M3CloudSlam
← Insights

Migration·12 October 2026·3 min read

Master data migration from M3 on-premise to M3 Cloud: a checklist

A move to M3 Cloud is the one moment you have to touch all of your master data. Copying it as-is brings fifteen years of workarounds into a fresh environment. Treat the migration as the chance to arrive clean.

Before you extract anything

  • Decide which master data objects move, and in which order: dependencies first, for example warehouses before item/warehouse records.
  • Decide which records move at all. Items not sold for years and blocked customers may not need to come along.
  • Agree who owns each object, and who signs off that it is ready.

Extract complete tables

Work from complete extracts, with the key fields always included, so every row stays identifiable. Splitting exports to get around record limits is a common source of missing or duplicated rows.

Check against rules, before the data moves

DimensionExample check
CompletenessEvery stocked item has a receiving location
ValidityThe warehouse on every item/warehouse record exists
ConsistencyEvery warehouse an item is sold from has an item/warehouse record
UniquenessNo two customers share the same VAT number
PlausibilityLead times fall within a sensible range

Fix what you find at the source, in the on-premise environment, so the corrections are part of what moves.

Load with a safety net

  1. 1Validate every row before writing, and compare it with what is already in the target: new, changed or unchanged.
  2. 2Never write rows the target would refuse; report them with the reason instead.
  3. 3Save the records an import will change before it changes them, so there is always a way back.
  4. 4Load in the order of the dependencies you agreed at the start.
Run the same rules on both sides

Checking the data with the same rules in the old and the new environment shows directly whether something was lost or changed on the way.

After the load

  • Run the quality rules on the cloud environment and compare the results with the on-premise baseline.
  • Put the fields that steer M3 under governance from day one, so the clean state stays clean.
  • Check key transactions on real records before users do.
How M3CloudSlam helpsM3 Cloud migration →M3CloudSlam knows M3 on-premise and M3 Cloud, and connects to both: the bridge for your migration.

Be among the first to ask your M3 anything

We are onboarding a small group of founding customers. You get the newest features first, a direct line to the team, and founding pricing.

Become a founding customer
  • Preview features firstPredictor, Debugger, Release Toggle Impact and Value Provenance
  • Shape the roadmapYour M3 questions decide what we build next
  • Founding pricing, locked inYour rate stays as the product grows