Load and reconcile a migration package across its owning applications

Purpose

Implementation staff coordinate a migration without taking ownership of another application’s records. The run gives them one place to follow the package and assess its results.

How It Works

Staff upload a manifest and dataset files, then register the package in the workspace being prepared for use. Registration checks the declarations against completed uploads and establishes a dependency order before any dataset job starts. A measured digest is preferred, but a declared digest can also satisfy the current check. Staff start the run using their own authority. Platform loads its datasets locally; other configured applications receive requests carrying the staff member’s token. Reading the running run refreshes dataset progress and submits newly eligible work, so polling also drives the load. Staff can pause further submissions or cancel the run, although a failed downstream cancellation can leave a child job active. Records already committed remain in the workspace. The summary adds the reported counts and presents readiness separately from completion. Submission errors, incomplete progress responses and excess counts remain limits that staff must consider when reviewing a load. The product should give staff a dedicated screen for this work and make unresolved cancellation visible.

Relationships

• Uploads provide the manifest and datasets used during registration.
• Record imports perform each dataset’s changes in the owning application.
• Reading records by producer key supports reconciliation against the extract.
• Workspace reset provides a clean starting point after a failed load; activation controls customer access.