The migration is a screen,
not an engagement.
ERP implementations fail in the services layer: month nine of a consulting engagement, and the tie-out still does not tie. Vered ships the migration as product, so you run it — and re-run it — yourself.
Keep exceptions visible. Keep the work moving.
Supported templates, providers and configured feeds only. Connection availability and health vary by setup; a catalog listing alone does not establish a working sync.
Map. Import. Tie out. Go live.
Four stages, each a real surface in the product. The stage names below are the actual module names in the codebase.
Map
Your spreadsheet columns mapped to the data model, with templates generated for what is missing.
src/lib/onboarding/columnMapper.ts; templateGenerator.tsImport
The import engine loads it, validating as it goes.
src/lib/onboarding/importEngine.tsTie out
The loaded result is tied out against what you had — the step that usually costs a consulting phase is a screen you can re-run.
src/lib/onboarding/tie-out.tsGo live
A deliberate switch, thrown when the tie-out says so.
src/lib/onboarding/go-live.ts; /admin/settings/go-live