Moving from Epicor to Business Central: a migration built around production
An Epicor to Business Central migration is mostly a manufacturing data project. Parts, methods, open jobs, inventory and costs must land in items, production BOMs, routings and production orders. The plant must keep running while that happens. So we plan the move around your production calendar. We test it with real jobs in a sandbox and cut over when the floor is quiet.
Last updated
What an Epicor to Business Central migration involves
Epicor sells several ERP products. Kinetic is for manufacturers, and Prophet 21 is for distributors. Each stores data in its own way. So our first task is to find out which product and modules you run. We also learn which screens people use daily and which customizations changed standard behavior.
From that we write a scope document. It lists the processes that move to Business Central and the ones that retire. It also lists gaps that need an add-on or an extension. Manufacturing in Business Central requires the Premium license. So production users are counted apart from finance and sales users at this stage.
Tell us your Epicor setup →
- ✓Epicor product and modules
- ✓Processes moving across
- ✓Processes being retired
- ✓Gaps and proposed answers
- ✓Premium and Essentials users
Epicor parts and methods become items, BOMs and routings
Epicor keeps materials and operations in one method. Business Central splits them. A production BOM holds the components. A routing holds the operations, work centers and machine centers. We split each method into those two records and link them to the item. Revision levels carry across as BOM and routing versions.
We map units and costing methods at the same time. Resource groups become work centers with their own calendars. First, we load a sample of finished goods. Then we recalculate standard cost in Business Central and compare it with Epicor. A cost gap at this point usually reveals a mapping error.
Map your part master →- ✓Parts to items
- ✓Materials to production BOMs
- ✓Operations to routings
- ✓Resource groups to work centers
- ✓Revisions to versions
Open jobs, inventory and work in progress after an Epicor migration
Jobs that are half finished on cutover day are the hardest part. You can finish or close as many as you can in Epicor before the switch. Alternatively, you can re-create the rest as released production orders in Business Central. Consumed material and finished operations go in as opening values.
Usually we combine both. A push finishes short jobs, and a controlled load handles long ones. Inventory comes from a count or a trusted Epicor report. Item journals post it by location, bin and lot or serial number. So quantity and value agree with the ledger from day one.
Go over open jobs →- ✓Raw material by location
- ✓Finished goods on hand
- ✓Lot and serial numbers
- ✓Work in progress value
- ✓Open purchase receipts
Testing the Epicor to Business Central migration with planners
Planners and supervisors judge a new system by one thing. Is tomorrow's schedule right? In the sandbox, we run planning worksheets against migrated demand. We release orders and post consumption and output. Then we compare the suggestions with what Epicor would have proposed. We explain each difference in plain terms for the Epicor to Business Central migration team.
We test labor and output reporting the same way, on the devices people use. For example, operators may scan or clock onto jobs today. If so, we show how production journals, shop floor pages or a data collection add-on will replace that. A few operators try it first on real jobs.
Book a shop floor walkthrough →- ✓Plan from real demand
- ✓Release and pick components
- ✓Post output and scrap
- ✓Send work to a subcontractor
- ✓Finish and cost an order
Mistakes to avoid in an Epicor to Business Central migration
Custom rules and screen changes in Epicor often hide decisions that nobody wrote down. One example is who may release a job. Another is when a price can be overridden. We treat these as requirements. Then we rebuild the important ones with approval workflows, Power Automate or AL extensions. We never assume standard Business Central behaves the same.
Costing is the other risk. Suppose Epicor values parts one way and Business Central uses another. Then margins shift on paper, although nothing changed in the plant. So we agree the costing method for each item group with your finance lead. We also show the effect on sample orders before go-live.
Ask what Premium covers →- ✓Costing method by item group
- ✓Who releases production orders
- ✓Scrap and rework handling
- ✓Labor reporting approach
- ✓Quality inspection points
Epicor to Business Central migration FAQ
Can Business Central replace Epicor for a manufacturer?
For many small and mid-sized discrete manufacturers, yes. The Premium license includes production BOMs, routings, capacity planning, subcontracting and production orders. Highly engineered work may need a configurator or scheduling add-on. We find that out during fit-gap work.
Does Microsoft provide a migration tool for Epicor?
No. The built-in cloud migration tool is for Microsoft's own earlier products. For an Epicor to Business Central migration, we extract the data with queries or exports. Then we transform it to the Business Central structure. Finally, we load it with configuration packages, journals and the standard APIs.
How do you handle jobs that are open at cutover?
Short jobs are finished in Epicor where possible. We re-create longer ones as production orders in Business Central. Their progress goes in as opening figures. We agree the list job by job with your production manager, so nothing is counted twice. Then we test a few jobs end to end in the sandbox.
Will our Epicor reports still be available?
The reports themselves do not move. First, we list the ones people really use. Then we rebuild them with Business Central report layouts, analysis mode on list pages or Power BI. Many turn out to be covered by standard Epicor to Business Central migration reports once the data is in place. So the rebuild list is often short.
What about quality and engineering change processes?
Business Central handles BOM and routing versions with start dates. It also tracks lots and serial numbers. However, formal engineering change control and detailed inspection plans often suit an add-on better. We suggest one only after we see how your team works today. We do not push a product.
Book a discovery call
Let's talk through your move to Business Central.
A focused call with a senior consultant. We learn how your business runs today, give you an honest view on whether Business Central fits, and outline scope and next steps before you commit to anything.
What happens after you send the form