R12 TO FUSION MIGRATION CHECKLIST

Executive summary

A pragmatic, risk-focused checklist to align executives, project leads and IT for an R12 to Fusion migration. Use this as the project initiation handout to confirm scope, governance and the first 90 days of activities.

1. Executive and governance readiness

• Confirm executive sponsor — Name, authority, escalation path.
• Steering committee — Members, meeting cadence, decision gates.
• Project owner and PM — Single accountable owner with contact details.
• Funding approval — Budget envelope and contingency reserve confirmed.
• Success criteria — Two or three measurable outcomes (example KPIs: month-end close days, invoice days outstanding, reconciliation exceptions).

2. Scope and landscape assessment

• Define scope — Modules, legal entities, ledgers, countries, integrations, deprecated features.
• Inventory customisations — List and classify as Retain; Refactor; Replace; Retire.
• Interfaces and integrations — Catalogue APIs, flat files, middleware, third-party systems and owners.
• Data footprint — Master data, open transactions, historical balances to migrate, archival rules.
• Compliance and localisation — Country tax rules, statutory reports, regulatory dependencies.

3. Migration strategy and cutover plan

• Migration approach — Phased waves or big-bang; rationale and target wave plan.
• Cutover windows and blackout periods — Business blackout dates, critical transactions schedule.
• Rollback criteria — Clear go/no-go checkpoints and rollback triggers.
• Cutover sequencing — Order of data loads, interfaces stop/start, reconciliation checkpoints.
• Parallel run plan — Duration, reconciliation checks, sign-off criteria for switching over.

4. Data and conversion controls

• Source–to–target mapping — Chart of accounts, tax codes, units of measure, item masters.
• Data cleansing tasks — Duplicate masters, inactive records, erroneous balances, stale accounts.
• Conversion scripts and validation — Test conversions, sample reconciliations, automated validation scripts.
• Archive strategy — What stays in R12 read–only; how to access historical transactions.
• Reconciliation checkpoints — Trial balance, AR/AR receipts, AP accruals, inventory valuation, fixed assets.

5. Build, test and validation

• Core configuration baseline — Ledgers, legal entities, security roles, chart of accounts ready in test.
• Test plans — Unit, integration, performance, UAT, regression with owners and entry/exit criteria.
• Test data management — Masking rules, representative volumes, refresh cadence for environments.
• Dress rehearsals — Minimum two full dress rehearsals including data load, interfaces and reconciliation.
• Acceptance sign–offs — Business and technical sign–off checklist for each environment.

6. Change, training and runbooks

• Role–based training — Who, when, curriculum and acceptance criteria; include super–users and trainers.
• Runbooks and SOPs — Day–one runbooks for finance and supply chain, access and stepwise procedures.
• Cutover heatmap — Owner list for each cutover item, estimated duration and dependency.
• Stakeholder communications — Frequency, channels, go–live readiness dashboard and change channels.

7. Support and post go–live stabilisation

• Hypercare model — Duration, dedicated war–room, escalation matrix, RACI for hot fixes.
• Support tiers and SLAs — Incident response and resolution SLAs for hypercare and steady state.
• Continuous improvement backlog — Capture defects and enhancement requests with prioritisation method.
• Knowledge transfer — Handover sessions, runbook ownership transfer and training completion records.
• KPIs to monitor — Month–end close days; invoice days; reconciliation exceptions; average ticket response time.

8. Risk controls and compliance

• Top 10 risks — List with owner, mitigation and trigger action.
• Data privacy and masking — Ensure compliance during test and conversion activities.
• Audit trail and controls — Reconciliation audit logs, change control approvals for config and code.
• Vendor and third–party readiness — Confirm SLA and contingency from integrators, banks and payroll.

Delivery checklist for first 90 days

• 1. Executive sponsor introduced and charter signed.
• 2. Full customisation inventory completed and priority decision made.
• 3. Integration owners assigned and interface freeze date agreed.
• 4. First data conversion validated with sample reconciliations.
• 5. Core security roles and COA deployed to test.
• 6. UAT schedule published and first round of business test scripts executed.
• 7. Two dress rehearsals scheduled and resources confirmed.
• 8. Hypercare resources and runbook library prepared.

One–page action items to present to the client now

• Immediate decisions required — Migration approach (phased or big–bang); Data archival threshold (how many years to migrate); Cutover month preference.
• Immediate deliverables due in 7 days — Steering committee roster; Customisation inventory template; List of integration owners and contact details.