MSAMM
Back to course

Implementing Cloud Financials: From Empty Pod to Go-Live · Module 14 · Data Migration and Integration

What breaks

Lesson 140 of 153 · 1 min

Six failures, and one of them has no later fix. Import ran, nothing imported. Data stuck in the interface with errors. Look in the interface table. Subledger does not agree to the general ledger after migration. A control account mismatch. Fix it before go-live, or live with it forever. Migration worked in test and failed in production. Different data volume, or configuration differences between environments. Prevention: the full-volume dry run. Assets are depreciating from the wrong date. Date placed in service loaded incorrectly, and painful to correct at scale. Template rejected every row. Wrong template version for the release. Bank feed stopped and nobody noticed for three weeks. No monitoring — an operational failure, not a technical one. Everything on this list costs time except the second. A control account difference you carry through go-live is a number in the accounts that nobody can explain for as long as the

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Implementing Cloud Financials: From Empty Pod to Go-Live, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 14 · Data Migration and Integration

  1. 1Migration strategy: what to bringFree preview
  2. 2The import architecture
  3. 3File-based import end to end
  4. 4The finance import objects
  5. 5Opening balances
  6. 6Configuration migration between environments
  7. 7Integration patterns and third parties
  8. 8What breaks
  9. 9Lab: migrate opening balances