Vered
Implementation

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.

The whole implementation, in one screen: the onboarding pipeline, a self-serve import (upload, validate, preview, import), and a go-live gate where every item is computed from your actual data — fix the source, it turns green. No nine-month engagement.Recorded live, demo data
01/The pipeline

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.

  1. 01

    Map

    Your spreadsheet columns mapped to the data model, with templates generated for what is missing.

    src/lib/onboarding/columnMapper.ts; templateGenerator.ts
  2. 02

    Import

    The import engine loads it, validating as it goes.

    src/lib/onboarding/importEngine.ts
  3. 03

    Tie 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.ts
  4. 04

    Go live

    A deliberate switch, thrown when the tie-out says so.

    src/lib/onboarding/go-live.ts; /admin/settings/go-live
Migrate your data yourself: map columns, import, tie out the result, then go livethe whole pipeline, as one capability
02/After go-live

Connected, not captive

Integrate over webhooks and a documented API rather than a bespoke connector projectwebhooks + documented integrations
Export your dataleaving must be possible for staying to mean anything
Run multiple facilities with their own work centres and transfers between themmulti-facility from day one
Add your own fields without a developeryour fields, without a change order

Bring one spreadsheet and see how far it gets.

How Vered is packaged