Legacy ERP without a big-bang switch
Rouslan Trouchkovskii connects ERP, shop and fulfillment with stable interfaces. Orders, stock and master data each get a mapping document before code.
Event-driven or batch paths are chosen per data type. Stock may lag minutes; orders must not duplicate when a webhook retries.
Legacy formats are transformed at the boundary, not inside the storefront. The shop speaks the API the team can test without the ERP GUI.
Phases end with reconciliation reports both sides sign. A difference without a named cause blocks the next phase.
What matters
- Mapping before the first interface goes live
- Separate rules for orders, stock and master data
- Transform at the boundary, not in the UI
- Reconciliation gates the next phase
Frequently asked questions
Which ERP systems are supported?
Any system that exposes documented interfaces or files the mapping can target. The first step names formats, owners and test data.
Can the old ERP stay during migration?
Yes, when phases define which system owns which entity until cut-over. Dual writes without a reconciliation rule are not used.
More in the house: Rouslan Trouchkovskii, Interfaces, Headless commerce in stages, Contact.
All posts