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 · 9 screens on this shelf
The screens on this shelf
- Migration Cockpit The cutover as a numbered plan, one step at a time: where in the old system each extract comes from — with the
- Source Systems The systems TRANXACT knows how to be migrated from, and how data gets out of each.
- Migration Objects What comes across from each system, what it is called over there, and which of the three kinds of data it is.
- 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
- Migration Batches Every consignment of rows, with what became of each.
- Migration Runs Validate, load, archive and balance runs. A run cannot be deleted — it accounts for records that now exist.
- Migration Resets Every time a company’s cutover was started again, and what it took with it. Kept because the load runs a reset
- Archived History Closed documents from the old system, kept whole and addressable by their old number. Records, not transaction
- Opening Balances The one thing the old ledger puts into this one, as a single conversion entry on the cutover date.
Progress is kept in this browser only — it is not sent anywhere and nobody else can see it.