Platform › Operations
Legacy Migration
Bringing a company across from the system it is leaving — masters and open transactions through the application, closed history archived rather than re-posted.
In Platform → Operations · 9 screens
| Screen | Kind | What it is | Columns | Fields | Actions |
|---|---|---|---|---|---|
| Migration Cockpit | Workspace | The cutover as a numbered plan, one step at a time: where in the old system each extract comes from — with the program or query to produce it — then upload, read the rejections, and load, post, archive or post the balances. | 0 | 0 | 0 |
| Source Systems | List | The systems TRANXACT knows how to be migrated from, and how data gets out of each. | 7 | 10 | 0 |
| Migration Objects | List | What comes across from each system, what it is called over there, and which of the three kinds of data it is. | 8 | 12 | 0 |
| Field Maps | List | How a field becomes a field. The transform is where a SAP date, a German decimal or an X-means-blocked flag is dealt with. | 6 | 7 | 0 |
| Migration Batches | Read-only list | Every consignment of rows, with what became of each. | 11 | 0 | 0 |
| Migration Runs | Read-only list | Validate, load, archive and balance runs. A run cannot be deleted — it accounts for records that now exist. | 8 | 0 | 0 |
| Migration Resets | Read-only list | Every time a company’s cutover was started again, and what it took with it. Kept because the load runs a reset deletes were what accounted for records that now exist — so this is the only trace a wipe leaves. | 9 | 0 | 0 |
| Archived History | Read-only list | Closed documents from the old system, kept whole and addressable by their old number. Records, not transactions: nothing here has been posted. | 8 | 0 | 0 |
| Opening Balances | Read-only list | The one thing the old ledger puts into this one, as a single conversion entry on the cutover date. | 6 | 0 | 0 |