ERP data migration without losing ten years of job history
A guided wizard that imports customers, products, suppliers, and open jobs from spreadsheets or your old ERP. Upload CSVs, map columns, preview, and commit. Fix bad rows in place without round-tripping to Excel. Route mismatches get flagged and corrected. Open jobs import with their current status, so day one on MirrorWorks is not a clean slate you do not have. No consultants, no six-month projects.
1
Guided wizard
Step by step, not consultant by the day.
Upload CSVs, map columns, preview, and commit. Built for shop owners, not IT teams. No other ERP has this.
2
Multi-file upload
Bring the whole dataset at once.
Customers, products, BOMs, and suppliers in parallel. Validation flags conflicts before anything hits the database.
3
Multi-select and bulk edit
Fix rows in the import, not after.
Select bad rows, correct them in place, re-validate, commit. No round trips to Excel.
4
Route fixing
Clean up the operations you inherited.
Old routings rarely match new machine definitions. Bridge flags mismatches and suggests the correct route.
5
Open job import
Start mid-production, not from scratch.
Import jobs that are already on the floor with their current status, so the first day on MirrorWorks isn’t a clean slate you don’t have.
6
Rollback and re-run
Mistakes aren’t terminal.
Undo an import, fix the source, run it again. Standard in dev tools, missing from every other ERP.
DatamigrationisthenumberonereasonERPprojectsfail.
Most shops hear "six months and $40k of consulting" and walk away. The ones that push through arrive on day one with half their data missing and the other half wrong.
Bridge turns migration into something a shop owner can do on a weekend. Export your customer list from Xero, your product data from the old ERP, and your open jobs from a spreadsheet. Drop them in, map the columns, fix the obvious errors, and commit. Most implementations finish in under a week, not six months. This is how MirrorWorks goes from "interesting" to "we’re on it by the end of the month", because the hardest step just isn’t hard anymore. Included in every tier, from Pilot onwards.
Floor-first
UX designed backwards from the shop floor.
So what does switching actually cost?
Bridge is included in every tier and the import takes about a week, so migration is not the number that decides this. The number that decides it is what you already pay. Put your own figures in below. They stay in your browser.
Typical published pricing. Picking a system resets the cost lines to its defaults; your seats and renewal date stay put. Edit everything to match your bills.
How this works: your current costs run until your renewal and rise 5% a year. MirrorWorks runs from the month after, at its published month-to-month price. Switching skips your next upgrade project, because you are leaving. Bridge imports your data free.
