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.
12 steps · 10 questions · 10 screens on this shelf
The screens on this shelf
Workspace
Migration Cockpit
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.
Open
Workspace
Migration Readiness
Go-live readiness per business area — ERP, CRM, supply chain, manufacturing, HR, healthcare, student and staffing: records, data quality, exceptions, reconciliation and a status for everything each area has to bring across.
Open
Records
Source Systems
The systems TRANXACT knows how to be migrated from, and how data gets out of each.
Open
Records
Migration Objects
What comes across from each system, what it is called over there, and which of the three kinds of data it is.
Open
Records
Field Maps
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.
Open
View
Migration Batches
Every consignment of rows, with what became of each.
Open
View
Migration Runs
Validate, load, archive and balance runs. A run cannot be deleted — it accounts for records that now exist.
Open
View
Migration Resets
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.
Open
View
Archived History
Closed documents from the old system, kept whole and addressable by their old number. Records, not transactions: nothing here has been posted.
Open
View
Opening Balances
The one thing the old ledger puts into this one, as a single conversion entry on the cutover date.
Open
Progress is kept in this browser only — it is not sent anywhere and nobody else can see it.