Master data · Data Import Available
Load data into M3 safely, row by row
Upload an Excel file. Every row is validated and compared with what is in M3, the records it will change are backed up, and only then is anything written.
8 rows refused: the warehouse does not exist. Nothing is written for these rows.
Example file and figures.
Why it matters
Today
- 1Load data with scripts or tools without a safety net
- 2Check the result afterwards, row by row
- 3Hope there is a way back if something goes wrong
Every mass update feels like a risk.
With Data Import
- 1Every row checked and compared before writing
- 2Rows M3 would refuse are never written
- 3A backup saved before anything changes
Mass updates you can trust.
How it works
From an Excel file into M3, safely
- 1 / 3
Check and compare
Every row is validated and compared with M3: changed, unchanged or new. Up to 100,000 rows per import.
Data ImportAvailableitem-warehouse.xlsx2,400 rows checked against M3A-2210100Allocation method 1 → 2changedA-2211100No differencesunchangedA-3001200New item/warehousenewA-3002900Warehouse 900 does not existrefused1,920 changed431 unchanged41 new8 refused8 rows refused: the warehouse does not exist. Nothing is written for these rows.
✓ Backup saved before writing: item-warehouse-backup.xlsxImport 1,961 rowsExample file and figures.
- 2 / 3
See what can't be loaded
Rows M3 would refuse are flagged with the reason, and nothing is written for them.
Data ImportAvailableitem-warehouse.xlsx2,400 rows checked against M3A-2210100Allocation method 1 → 2changedA-2211100No differencesunchangedA-3001200New item/warehousenewA-3002900Warehouse 900 does not existrefused1,920 changed431 unchanged41 new8 refused8 rows refused: the warehouse does not exist. Nothing is written for these rows.
✓ Backup saved before writing: item-warehouse-backup.xlsxImport 1,961 rowsExample file and figures.
- 3 / 3
Back up, then write
The records the import will change are saved to a backup file first. Re-importing it puts them back.
Data ImportAvailableitem-warehouse.xlsx2,400 rows checked against M3A-2210100Allocation method 1 → 2changedA-2211100No differencesunchangedA-3001200New item/warehousenewA-3002900Warehouse 900 does not existrefused1,920 changed431 unchanged41 new8 refused8 rows refused: the warehouse does not exist. Nothing is written for these rows.
✓ Backup saved before writing: item-warehouse-backup.xlsxImport 1,961 rowsExample file and figures.
8 rows refused: the warehouse does not exist. Nothing is written for these rows.
Example file and figures.
What it brings you
Mass updates without the risk
- 1“You don’t need a consultant for that anymore”Key users load and correct master data themselves, with the checks and the backup built in.
- 2No surprises in productionYou see exactly what an import will change before it changes anything.
- 3Always a way backThe backup is saved before writing, every time.
- 4Clean loadsRows M3 would refuse are never half-written.
Next in your journey
See Data Import on your own M3
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