Skip to content

Operational transition and source ownership

Operational cutover is the agreed point after which new operational work and changes are made in Toolora. The legacy system can remain a historical source. Fetching an export, publishing code or completing a technical import does not establish that business decision.

Toolora remains in pre-launch development. Shared-data cleanup, replacement imports and the operational transition are deferred until the rest of the platform is ready. This article describes decision boundaries and evidence; it is not a procedure authorizing cutover or a database reset.

Decision or evidence Required owner or result What it does not establish
System of action Explicit agreement about where each kind of new work is created/changed A read-only source link does not select the operational owner
Retained identity/configuration Deliberate preservation of users, roles, company/provider settings and reusable test access Cleanup must not silently remove required bindings or sessions
Source corpus and coverage Named source version, completeness and private preservation A recent folder timestamp is not complete business coverage
Imported reconstruction Identity, relation, value and exception reconciliation Counts or a succeeded job are insufficient
Native operational readiness Named business workflows and their remaining limitations A code deployment or unit pass is not independent acceptance
Provider continuity Exact accounting/payroll identity and recoverable outcome boundary Local state cannot certify remote bookkeeping or payroll
Final transition action Approved scope, timing, responsible people and recovery limits A planning document is not execution permission

Distinguish source history from current work

Section titled “Distinguish source history from current work”

A project can retain a source-offer link without making that offer its accepted billing authority. Imported invoice history can remain valid evidence while unresolved basis attribution blocks new invoicing. Those gaps must be reconciled or explicitly handled through an accepted procedure, not concealed by changing status labels.

A native quote, customer contact and project work site retain their own identities. Source reconstruction must not replace an existing person’s reviewed edit or rewrite an issued snapshot to resemble current company presentation. Import sources defines the identities that need to remain traceable.

The accepted direction defers a generalized source-neutral migration platform until an observed second-source/customer need justifies it. That is a bounded architectural decision, not permission to copy another integration or expand this documentation pass into a new collector.

A delta read can bring later source facts into an existing reconstruction, but the owning runbook still determines which operations are scheduled, manual, dry-run or explicitly applied. Payment refresh and invoice re-import have different purposes and ordering. A running sync job does not mean simultaneous edits in both systems are safely merged.

Before a real transition, the accepted scope must say which source changes still arrive, when final source capture occurs and which system owns later corrections. Reuse historical replay so an old fact does not create a new customer notification, duplicated project or payroll command.

Suppose a synthetic company has imported customer/project history and passed a local invoice-editor test. Its historical invoices still lack reconciled source/basis links, and the bureau has not accepted a payroll file. The technical import can be complete for its declared scope while the operational transition remains unapproved.

The next useful evidence is the specific reconciliation and receiving-system/business outcome, not another row-count report. If the agreed initial scope defers a variant, record the actual limitation and usable accepted handling rather than claiming universal readiness.

The financial lifecycle, historical transition and first-stage PAX issues retain their own open acceptance. Previous dated receipts establish their named scenario and version; old exception counts are not current inventory. Reports and payment reconciliation preserve source and amount coverage.

Vi Målar’s Fortnox binding is real bookkeeping. No transition rehearsal may bypass that provider restriction by changing a binding or using final attest/export/send as a test. Current runbooks, release checks and an explicit operational decision are required before actual shared changes.

This source review performs no cleanup, replacement import or cutover. Evidence interpretation explains the separation between implemented, merged, deployed and scenario-verified facts.