Why an Epicor Kinetic migration is dominated by the customisation surface, the GL segment compression, the multi-book gap and the MOM split — and what that means for every design decision that follows.
Every ERP migration eventually collides with an uncomfortable truth: the two systems do not merely store data in different tables — they reason about the business in different ways.
Epicor Kinetic is the current name (post-2021 rebrand) of the platform previously sold as Epicor ERP 10. It is a manufacturing-centric ERP with deep strength in mid-market and upper-mid-market discrete, make-to-order, engineer-to-order, and mixed-mode manufacturing, plus industrial distribution — with recognised footprints in fabricated…
Epicor has publicly announced that the final on-premises feature release is Kinetic 2028.1 (tentatively January 2028), with Active Support through 2029-12-31 and Sustaining Support from 2030-01-01. After that date, innovation is cloud-only via the "Ascend with Epicor" migration programme.
The customisation surface is the dominant cost and effort driver because no artefact carries forward mechanically. Each Epicor customisation technology has a different D365 disposition:
An Epicor chart of accounts is defined at Company level as a segmented account string: a natural (main) account segment plus additional user-defined segments (division, department, project, and others), configurable up to a documented maximum of approximately twenty segments.
An Epicor Book is a set of accounting policies — for example GAAP, statutory, and managerial — attached to a Company. The same transaction can post differently per Book, allowing parallel views of the same operational events under different accounting standards.
An Epicor Method of Manufacturing (MOM) is a single revisioned template combining:
The ICE framework's carry-forward from ERP 10 to Kinetic creates a lineage problem for customers still mid-Kinetic-migration. The load-bearing distinction:
Outside the four centrepieces, Epicor's standard functional estate maps to D365 with reasonable structural alignment:
The rest of this learning path is organised into fourteen domains. Each covers a distinct design surface and the decisions it demands:
Epicor Kinetic is a capable, mature manufacturing ERP. The migration to D365 F&SCM is not driven by a functional capability indictment — it is driven by vendor timeline (the Kinetic 2028.1 on-premises sunset), Microsoft estate consolidation, and the opportunity to modernise extensibility.