Week 5 of 8
Data migration you can sign
Infor’s implementation guide asks for three things on data: a full practice run of the migration sequence in the cutover plan, SIT on the migrated data, and formal business sign-off of the results before go-live. Most programs do the first, rush the second and skip the third.
If you are moving from on-premises, also check the overlap you can afford. Infor’s lifecycle policy allows Transitional Support for the old license of no more than 18 months, and only if it is written into your agreement.
This week: agree tolerances and script the checks
- List every migration object in load order with its load method and dependencies: sites and warehouses, items, customers, suppliers, BOMs, routings, stock, open orders, open AR and AP, balances.
- Agree count and value tolerances with finance and data owners before Mock 1, per object.
- Script the reconciliation you will repeat at 3 a.m.: stock quantity and value by warehouse, AR and AP open items, trial balance by account, items without a structure.
- Time every rehearsal step. Anything well over plan on the critical path gets an action before the next mock.
Number of the week
18 months
maximum Transitional Support for an on-premises license while you move to a new offering, if it is in your agreement.
Source: Infor Product Lifecycle PolicyUse this week
- Infor Data Migration Validation Tracker →
Objects in load order, count tolerances, reconciliation checks that pass or fail on your numbers, and rehearsal timings.
- Mock Cutover Rehearsal Tracker →
Goals and exit criteria for each rehearsal, with variance flags.
Next week: SIT, UAT and two layers of security. Getting a signature that holds.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.