The short answer
Production does not stop for a migration. A good plan separates what must move (open orders, open stock with its lots and expiry, master data) from what can be archived, rehearses the move several times, and cuts over in a quiet window.
What worries operations teams
Downtime
A line that waits for the system is a day of lost product.
Lost batch history
A recall next year may need a lot from last year.
Retraining
Operators and storekeepers who know the old screens by heart.
Hidden customisations
Years of local fixes that nobody documented.
A migration in five steps
- Inventory the old systemList the customisations, reports, integrations and interfaces. This is the fit-gap.
- Decide what movesOpen items and master data move. Closed history is archived and linked for recall look-ups.
- RehearseRun the migration several times in a sandbox and reconcile each rehearsal to the old ledger.
- Cut overFreeze in a quiet window, load the final balances, stock with lots and expiry, and open orders, and verify.
- StabiliseRun both ledgers' reports side by side for the first close, with support on the floor.
What changes by source system
| Quelle | What we plan for |
|---|---|
| SAP Business One | Item and batch masters, warehouse bins, open orders, and local add-ons that need a modern equivalent |
| Sage X3 | Formula and production data, lot and expiry records, and multi-site structures |
| Dynamics GP | Inventory, receivables and payables history, and Microsoft's lifecycle dates for the product, which you should check on Microsoft's site |
Where to go next
To see this against your own recipes, warehouses and routes, book a FoodBeverageFlow 365 consultation, or read the FoodBeverageFlow 365 product page.
Häufig gestellte Fragen
Can we migrate without stopping production?
Usually yes. We rehearse the migration several times, reconcile each rehearsal to the old ledger, and cut over at a quiet point in the production calendar, with a short, agreed freeze.
Do we bring historical batch and lot data across?
Open stock with its lots and expiry dates is migrated. Closed history is usually archived and linked for recall look-ups, with the scope agreed in the fit-gap so the new system stays fast.