D365ConsultantDivision of Sataware
D365ConsultantDivision of Sataware
Moving off Epicor

Epicor to Business Central migration, planned around the Epicor product you actually run.

An Epicor to Business Central migration depends first on which Epicor you own, because Epicor is a family of separate products rather than one system. Kinetic, formerly Epicor ERP 10 and Epicor 9, is a manufacturing ERP. Prophet 21 and Eclipse are distribution systems with their own databases and vocabulary. We start by naming the product and version. Then we map its data model and say where Business Central fits well and where it does not.

Kinetic, P21, Eclipse
three different starting points
Premium
Business Central licence for production orders
BAQs
a common route for extracting Kinetic data
Close-up of CNC milling cutters and tool holders

Which Epicor product are you leaving?

Manufacturing

Epicor Kinetic / ERP 10

Job-based manufacturing with parts, methods of manufacturing, operations, resource groups and multi-site inventory. The closest Business Central fit is the Premium licence with production BOMs, routings and production orders.

  • โœ“Job shops and make-to-order plants map well
  • โœ“Heavy scheduling or configurator use needs a closer look
  • โœ“Business Activity Queries feed the extraction
Distribution

Prophet 21

Wholesale distribution with detailed pricing, supplier rebates, multiple branches and counter sales. Business Central covers warehousing and purchasing well. The fit check spends its time on complex price and rebate logic.

  • โœ“Contract pricing reviewed rule by rule
  • โœ“Branch structure mapped to locations or companies
  • โœ“Supplier rebate tracking often needs an app or extension
Distribution

Eclipse

Built for electrical, plumbing and HVAC supply houses, with trade-specific quoting and pricing. Some companies in these trades do better staying on a trade-specific system. We tell you if yours is one of them.

  • โœ“Trade quoting and job pricing compared honestly
  • โœ“Branch transfers and counter sales mapped to locations
  • โœ“Vendor price file imports rebuilt

Epicor vocabulary and where it lands in Business Central

In Kinetic, a part is the item master, grouped by part class and product group. A method of manufacturing ties materials and operations to it. Business Central splits that into an item, a production BOM for the materials and a routing for the operations. Work centers and machine centers stand in for Epicor resource groups and resources. Epicor sites become locations, or separate companies when each site keeps its own books.

Kinetic's general ledger holds its chart of accounts in a GL book. It has a natural account segment plus further segments such as division or department. The natural account stays as the G/L account number. The other segments turn into dimensions. A second book usually points to a reporting need, such as another currency or a statutory view. An added reporting currency or a separate consolidation company covers that.

Prophet 21 and Eclipse speak distribution: branches, ship-tos, suppliers, product groups and price matrices. Customers and ship-to addresses map directly. We translate price matrices into Business Central sales price lists. A list can target one customer, a price group, a campaign or all customers. It can hold quantity breaks and date ranges. If you run BisTrack, iScala or an older Epicor product, the same method applies with its own mapping.

Epicor records mapped to Business Central

Epicor
Business Central
Watch for
Part (Kinetic), product (P21, Eclipse)
Item
Units of measure and conversions checked per item
Part class, product group
Item category and inventory posting group
Separate the reporting grouping from the accounting grouping
Method of manufacturing: materials
Production BOM
Phantom and pull-ahead parts need a design decision
Method of manufacturing: operations
Routing with work centers and machine centers
Setup and run times verified against the shop floor
Open job
Released production order
Created fresh at cutover with remaining quantities
Site or branch
Location or company
One legal entity or several decides the answer
Warehouse and bin
Location and bin
Directed put-away and pick only where volume needs it
COA segments and GL book
G/L account plus dimensions
Natural account stays, the other segments become dimensions
Price lists and price matrices
Sales price lists
Rebate and contract logic tested with real orders
Customer and ship-to
Customer and ship-to address
Tax area set per ship-to for US sales tax

What moves across, and in what form

  • โœ“Opening trial balance by natural account and dimension, posted as one journal at the cutover date
  • โœ“Open AR invoices, open AP invoices and unapplied cash as individual documents, so aging matches Epicor
  • โœ“On-hand inventory by location, bin, lot and serial number at the unit cost you agree to carry
  • โœ“Open sales orders, purchase orders and transfers with remaining quantities, not their shipped history
  • โœ“Short open jobs finished in Epicor first, longer ones recreated as production orders with work in process carried by journal
  • โœ“Posted history summarized by month for comparisons, with full detail exported to an archive you can query

Built again from scratch rather than carried across

BPM directives

Epicor BPM directives are code that fires on events. Each becomes standard setup, a workflow, a Power Automate flow or an AL extension. Some turn out to be no longer needed.

BAQ reports and dashboards

List views, analysis mode, financial reports and Power BI replace BAQs and the dashboards built on them.

Configurator rules

Product configurator logic does not transfer. Business Central needs an AppSource configurator or a custom extension. So in an Epicor to Business Central migration, we scope this up front rather than discover it late.

Printed documents

We redesign custom invoices, packing slips and job travelers as Business Central report layouts in Word or Excel. Your team can adjust them later.

A cutover that respects the shop floor

  1. 1

    Pick a point between jobs

    Choose a period end with the fewest jobs mid-operation. Finishing short jobs in Epicor beats migrating partial labor and material.

  2. 2

    Count the stock

    Run a physical or cycle count close to cutover. Then the quantities you load into Business Central are ones the warehouse trusts.

  3. 3

    Extract and reshape

    Pull data through BAQs, Epicor's export tools or direct SQL access where your hosting allows it. Next, map it into configuration packages.

  4. 4

    Rehearse with a real week

    Before the live cutover, push a full week of orders, receipts, output and shipments through a sandbox.

  5. 5

    Go live and prove it

    Load balances, open documents and stock, and tie each to the Epicor closing reports. Then release production orders to the floor.

Epicor migration questions answered

Can Business Central handle Epicor-level manufacturing?

For many small and mid-sized job shops and make-to-order plants, yes. Business Central Premium includes production BOMs, routings, capacity planning, production orders and output reporting. Companies that depend on advanced scheduling, complex configurators or large engineer-to-order projects should compare carefully. Some of them belong on Dynamics 365 Supply Chain Management or should stay where they are. The fit-gap tells you which side of that line you are on.

Is there a Microsoft tool that migrates Epicor data automatically?

No. Microsoft's cloud migration tools cover its own older ERPs, such as Dynamics GP and Dynamics NAV, not Epicor. We extract and clean Epicor data, then reshape it into configuration packages or load it through the Business Central APIs. That is why we script every step, so trial runs repeat cleanly with fresh data.

We run Prophet 21. Is Business Central the right move?

It can be, if your pricing and rebate rules fit Business Central price lists or a proven app. Distributors with simple branch warehousing and buying often gain from the tie to Microsoft 365 and Power BI. Some distributors live on complex contract pricing and rebate programs. They should test those rules first. We run that test with real orders in a sandbox during the fit-gap.

More Epicor to Business Central migration questions

What happens to our open jobs at cutover?

Finish what you can in Epicor and recreate the rest. Jobs close to completion are best completed and closed in Epicor before cutover. We recreate longer-running jobs in Business Central as released production orders with their remaining operations. The work in process value comes in by journal, so the balance sheet ties.

Do we keep Epicor running for history?

Usually only for a short read-only period, if at all. Summarized history covers comparative reports. A database export or archive holds the detail for audits. Your Epicor licence and hosting terms decide how long read-only access is practical. So check them before you set the cutover date.

Talk to us about your project.

Tell us what you run today and what has to change. A senior consultant replies with a written next step.

Get started

Start with a scoping conversation.

Thirty minutes with a senior consultant - not a sales call. We look at how you run today, tell you plainly whether Business Central is the right fit, and give you an honest sense of scope, cost and timeline before you commit to anything.

What happens next
1
We review your enquiry
A consultant reads it before the call - no discovery questionnaire to fill in.
2
30-minute scoping call
Your processes, your current systems, and the gaps that matter most.
3
Written summary & estimate
Indicative phases, licence counts and a cost range, in writing within three days.
Reply within one business day
NDA signed before discovery on request
No obligation, no cost for the scoping call
Microsoft-certified consultants only
Request your scoping call
Four fields. A consultant replies within one business day.
No cost
Your details stay with our consulting team - never shared, never added to a mailing list.