Skip to content
Get a quote

Migrate to Epicor Prophet 21

Epicor ERP — Kinetic, Prophet 21, BisTrack, iScala — is a vertical-specific manufacturing and distribution suite whose migrations live or die on DMT templates, GL opening balances, and the Progress-or-SQL schema underneath.

Short answer

FlitStack AI migrates financial, supply chain, and operational data into Epicor Prophet 21 from 200+ ERPs, including Odoo ERP, Edicom EDI, Business Central, NetSuite. Every field is mapped to Epicor Prophet 21's objects, history and associations come across, the Epicor Prophet 21 setup is configured alongside, and the whole migration stays reversible in one click.

By

From Any source
DestinationEpicor Prophet 21
Odoo ERPEdicom EDIBusiness CentralNetSuite
200+ sources mapped into Epicor Prophet 21

Systems we move into Epicor Prophet 21

The ERPs teams most often move from. Each page shows what moves, the field mapping and what to watch for.

What Epicor Prophet 21 supports, and where its import tools stop

  • Industry-specific design for wholesale distributors, not a general-purpose ERP repurposed for distribution — distributors choose P21 because it matches their replenishment, kitting, and counter-sale workflows out of the box.
  • Strong inventory control with automated replenishment, lot and serial tracking, and multi-warehouse management appeals to distributors with complex stock requirements and tight margin pressure.
  • Responsive customer support cited across G2 and Gartner reviews, with Epicor's 90% retention rate reflecting long-term customer satisfaction in a market where switching costs are high.
  • Cloud deployment on Microsoft Azure provides the flexibility to scale user counts and warehouse locations without on-premise infrastructure investment.
REST onlyOAuth 2.0 (B2Sell wrapper); direct SQL Server access for native queries
Rate limitsNot publicly documented by Epicor; third-party connector rate limits vary by integration layer
ObjectSupportNote
CustomersfullCustomer records in P21 include ship-to addresses, contact details, credit limits, and pricing tiers. Standard export via SQL views or REST API endpoints. We map each Customer record to the target system's counterpart, preserving any custom fields attached to the customer record.
VendorsfullVendor master data includes address, payment terms, and buyer assignment. Exportable via SQL Server views or direct table query. We preserve the vendor-to-item linkage so replenishment relationships survive the migration.
ItemsmappedItem master in P21 contains part numbers, UoM, warehouse assignments, replenishment methods, and lot/serial controls. Complex item structures (kits, sales kits, job assemblies) require field-level mapping to the destination item schema. We handle the UoM conversion and BOM flattening during migration.
Sales OrdersfullOpen and historical sales orders export via SQL queries against the OrderHead and OrderDtl tables. Line item pricing, discounts, and warehouse fulfillment data are included. We preserve order-to-customer linkage and open order status at cutover.
Purchase OrdersfullPO master and line data extract from the POHeader and POLine tables. Vendor pricing, lead times, and receipt schedules are included. We maintain the PO-to-vendor relationship and flag any partially received POs for manual reconciliation.
QuotesmappedQuote headers and lines export from the QuoteHed and QuoteDtl tables. Expiration dates, pricing, and customer linkage are preserved. We flag quotes with expired statuses so the target system receives only active or recently expired records.
Chart of AccountsmappedP21 GL accounts export from the GLAccount table. Account segment structure varies by company configuration, so we preserve the full account code string and map it to the destination's chart structure. Sub-account and cost center segments require explicit mapping.
Open AP/ARmappedOpen payables and receivables require careful sequencing: we extract invoice headers and line distributions, then map them to the destination AP/AR modules. Partially paid invoices are flagged with remaining balance and payment schedules for reconciliation.
WarehousesfullWarehouse master records include bin locations, picking priorities, and cross-dock configurations. Multi-warehouse setups extract cleanly via SQL. We map each warehouse and its bin structure to the destination, flagging any non-standard bin configurations.
Lot/Serial NumbersmappedLot and serial number tracking links to item and transaction history in P21. We preserve the lot number, expiration date, and cost layer (FIFO/lot-specific) during migration. Full traceability chains require exporting LotCtrl and SNTran tables together.
Employees/UsersmappedUser accounts and employee records have role-based permissions in P21. We extract user records, role assignments, and territory coverage. Owner/User assignment links to orders and quotes require field-level mapping in the destination system.
Custom FieldsnoneP21 supports user-defined fields (UDFs) added via the SDK or data directive framework. These are stored in extension tables or custom columns that vary by company. We do not migrate custom fields by default; we document their existence and advise the customer to re-create them post-migration or engage P21 consulting resources to map them.

The Epicor Prophet 21 migration guide

Why teams migrate to Epicor ERP

The four shapes an Epicor migration takes, and what makes the platform harder — or easier — than the ERP category average.

Epicor Software Corporation was founded in 1972 and is headquartered in Austin, Texas; the modern company is the result of a 2011 merger of Epicor and Activant Solutions, followed by a series of vertical acquisitions1. The flagship product is Kinetic (cloud manufacturing ERP, formerly Epicor 10), with Prophet 21 for wholesale distribution, BisTrack for building-materials, Eclipse for electrical/plumbing distribution, and iScala for international/multi-entity finance.

The typical Epicor customer is a $50M–$1B mid-market manufacturer or distributor with 50 to 5,000 users, real shop-floor or warehouse complexity, and a need for a vertical-tailored ERP without a Tier-1 implementation budget. Compared with Oracle NetSuite, Epicor positions on industry depth — discrete manufacturing, finite scheduling, MES — at a lower license point3. Compared with Dynamics 365 Business Central or SAP S/4HANA, it positions on Prophet 21's distribution heritage and on customisation latitude through BPMs and UD fields.

The shapes of migration that actually land on Epicor tend to fall into four patterns. First, legacy Epicor consolidation — Vantage, Vista, Epicor 9, on-prem Epicor 10 customers moving to Kinetic in the cloud as Epicor phases out on-premises support. Second, NetSuite-or-SAP exits, driven by sticker shock on multi-entity manufacturers — one Reddit thread documents a $700K NetSuite quote against an Epicor Kinetic evaluation for a 2-country, FDA-regulated manufacturer3.

Third, QuickBooks-or-spreadsheet outgrowing at the $20M–$100M revenue threshold where MRP, BOM and multi-warehouse inventory finally need real ERP. Fourth, competitor-ERP replacement — ECi M1, Infor SyteLine, Sage 100, IFS — usually triggered by an acquisition or an end-of-life announcement. Each shape has a different difficulty profile: a Vantage-to-Kinetic move is mostly a database upgrade with custom-code rewrites, while a NetSuite-to-Prophet 21 swing is a full re-implementation of the chart of accounts and inventory model.

What makes migrating to Epicor harder than the category average is the vertical product matrix. Kinetic, Prophet 21, BisTrack and Eclipse share branding but not data models — choose the wrong destination edition and the mapping spreadsheet is wasted. The underlying database is SQL Server on modern Kinetic and Prophet 21 SaaS, but legacy on-prem Prophet 21 and Vantage installs still run Progress OpenEdge, and Archon and Encompass migrations regularly find both engines in a single tenant.

What makes it easier than the average is the Data Management Tool (DMT) — Epicor's first-party bulk-import utility that ships with 60+ prebuilt templates and routes every row through the same Business Object layer the UI uses4. BPMs fire, validation runs, integrity is enforced — at the cost of throughput. Customisations preserve a decade of on-prem work but none of it auto-converts; it is rebuilt against Kinetic frameworks.

DMT is the import path that Epicor itself uses — and the price you pay is that every row pays for every BPM you wrote.

The Epicor ERP data model you need to map into

Business Objects, tables, UD fields, and the key columns you'll wire on every import — the destination schema decoded.

Epicor's data model is built around a relational schema of more than 1,300 services and roughly 20,000 operations, each backed by a Business Object (BO) that owns a primary table and its child tables. Kinetic groups BOs into modules — Erp, Ice, Mfg — and every import path, whether DMT or the UI, calls the BO update operations rather than writing to the database directly. That means upserts always run through validation, BPMs and security.

Before mapping a source field, you need to know which BO owns the destination table, what columns it requires, and which combination of keys uniquely identifies a row. The table below summarises the BOs you will touch in any Kinetic or Prophet 21 migration.

ObjectWhat it storesRequiredTier
Customer (Customer table)Bill-to and ship-to customers with terms and tax profilesCustID, Name, CustomerTypeAll editions
Vendor (Vendor table)Suppliers with payment terms, 1099 and bank routingVendorID, Name, CurrencyAll editions
Part (Part / PartPlant / PartWhse)Part master, plant-level planning, warehouse-level stockPartNum, IUM (inventory UoM), ClassID, TypeAll editions; multi-plant on most
GLAccount (Segments + ChartID)Chart of accounts with up to 20 segments per ChartIDAccount, Description, ChartID, ActiveAll editions; Kinetic supports multi-book
BOM (ECOMtl / ECORev / ECOOpr)Engineering BOM revisions, materials, operationsPartNum, RevisionNum, ApprovedDateManufacturing editions
ARInvHed / ARInvDtlAR invoice headers and lines (open + history)Company, InvoiceNum, CustNum, InvoiceDateFinancials module
APInvHed / APInvDtlAP invoice headers and linesCompany, VendorNum, InvoiceNum, InvoiceDateFinancials module
OrderHed / OrderDtl / OrderRelSales orders, lines and release schedulesCompany, OrderNum, CustNum, OrderDateAll editions
PartTran (inventory transactions)Every stock movement — receipts, issues, adjustmentsTranType, PartNum, Plant, TranQty, TranDateAll editions
UD Tables (UD01–UD100, UD-CodeType)User-defined tables and fields on standard tablesKey1–Key5 columns; UD fields defined per parent BOAll editions

Every BO row carries a Company column. Epicor's multi-company architecture means a single tenant can host multiple companies with separate ChartIDs, currencies and operational books — and DMT imports must specify the target Company on every row, or the load lands in whichever company the DMT user's default is set to.

Upsert keys vary by BO. Customer keys on CustID (or the system-assigned CustNum integer); Part keys on PartNum; GLAccount keys on the composite of ChartID + Account; OrderHed keys on Company + OrderNum. DMT templates declare the key columns explicitly — the Add mode rejects duplicates, Update requires the row to exist, and Add-or-Update attempts both4. Keys are fixed by the BO and cannot be reassigned at runtime.

Custom fields are added as UD fields on standard tables via the Data Dictionary, or as separate UD Tables for entirely new entities. UD field types include character, decimal, integer, date, datetime, boolean and combo-box (bound to UserCodes — Epicor's picklist mechanism). There is no hard cap on UD fields per table, but practical limits emerge from form-customisation and BAQ join complexity.

Field typeLimitNotes
Character UD fieldLength set at field creationLength cannot be changed after creation without DD rebuild
Decimal / Integer UD fieldPrecision set at creationUsed for prices, quantities, custom counters
Date / Datetime UD fieldSQL DateTime rangeUse for legacy created/modified preservation
Boolean (Logical) UD fieldTrue/FalseRenders as checkbox on customised forms
Combo-box (UserCode-bound)UserCode list per CodeTypeEquivalent to picklist; maintain in User Codes Maintenance
BAQ-bound UD fieldRead-only at the UI layerPulls from a Business Activity Query at runtime
UD Tables (UD01–UD100)100 generic tables with Key1–Key5Parent/child wiring via Key columns; no native cascade delete55
Calculated fields (BPM-managed)Server-side via BPMNo native formula type; rebuild logic in a BPM data directive

Relationships in Epicor are foreign keys in the underlying SQL Server (or Progress OpenEdge on legacy on-prem). Parent/child wiring on UD tables uses the Key1–Key5 columns mapped to the parent's natural key55. There is no native cascade-delete on UD tables — deletion is enforced by BPMs or by the parent BO. Standard tables ship integrity rules: deleting an OrderHed cascades to OrderDtl and OrderRel via the BO, not via SQL.

Customisations beyond UD fields live in BPMs (Business Process Methods) — server-side C# code attached to BO operations as pre-, post- or in-transaction directives — and in Personalizations (per-user form layouts) and Customizations (shared form code). None of these is data; all of them affect how data writes behave during import, which is why a DMT load against a heavily-BPMed tenant runs slower than the raw row count would suggest.

Pre-migration prep — the work before you touch Epicor

What must be true on the source, in the destination, and across the team before the first DMT row is committed.

The single best predictor of a clean Epicor migration is whether the chart of accounts, part master and customer/vendor master have been cleansed before DMT is opened. Data Ladder, Panorama and Epicor's own Implementation Guide all converge on the same point — cleansing after import is more expensive than cleansing before, because every dirty row that lands triggers BPM execution, validation logging and downstream report distortion.

Cleanse the part master, the chart of accounts and the customer master before DMT — every dirty row that lands costs you twice.

Treat the source export as raw material that needs to be shaped to Epicor's expected formats — Part numbers padded to the new schema's length, GL account segments concatenated to ChartID + Account, UoM codes converted to Epicor UoM Class members, currencies expressed in Epicor's Currency Master codes, dates rewritten as MM/DD/YYYY for DMT (which uses regional settings).

Source-side prep

  • Cleanse and dedup customer, vendor and part masters in the source before extract — Data Ladder and similar tooling are designed for ERP-bound dedup and catch case-only and whitespace duplicates that survive a naive SQL export.
  • Lock the chart of accounts for the cutover fiscal period — adding a segment after the GL has been loaded into Epicor means rebuilding ChartID and re-keying every prior journal.
  • Reconcile open AR and AP to the penny in the source before extract — Epicor's reconciliation reports (AR Aging, AP Aging, GL Trial Balance) will surface every variance after load, but fixing it in the source is faster than journal-entry corrections in the target.
  • Decide what is historical versus what is open — most teams import open transactions only (open AR, open AP, open POs, open sales orders, on-hand inventory) and archive history to a read-only warehouse or UD tables8687.
  • Stamp a stable external ID on every record before extract — the source primary key carried into a Character30 UD field gives you a reconciliation anchor that survives Epicor reassignment of CustNum, VendorNum and OrderNum.

Destination-side prep

  • Stand up a Pilot environment — Kinetic SaaS customers get a Pilot tenant alongside Production; on-prem customers clone the production database to a Test server and update SysAgent paths so background jobs fire against the test environment36.
  • Provision users and security groups first, including License Configuration, before loading data — owner and audit columns fall back to the DMT user if the referenced employee or user is missing.
  • Build the Chart of Accounts and segment structure in Epicor before loading any GL or sub-ledger data — Epicor supports up to 20 segments per ChartID with controlled-value lists per segment119.
  • Create UD fields, UD tables and UserCodes before importing rows that depend on them — DMT silently ignores values for UD fields that have not been added to the Data Dictionary.
  • Configure UoM Classes and conversion factors before loading the Part Master — every Part has an Inventory UoM (IUM), Purchasing UoM (PUM) and Sales UoM (SUM), and conversions are owned by the UoM Class, not the Part117.
  • Define Plants, Warehouses, Bins, and Site relationships before any inventory transactions land — PartTran rows reject if the referenced Plant or Warehouse does not exist.

People prep

Cutover only works if Finance, Operations and IT cooperate. Lock down a source-system freeze window — typically 48 to 96 hours over a weekend bracketing month-end — and communicate it to every group that touches the ERP. Train Finance on Journal Entry, GL Account Maintenance and Period Close, and train Operations on Part Entry, Job Entry and Sales Order Entry before go-live.

A clean Vantage-to-Kinetic upgrade runs 6–9 months elapsed; a NetSuite-to-Prophet 21 swing runs 9–15 months; a Vantage-to-Kinetic with 20+ customisations runs 12–18 months and $200K–$500K in conversion alone.

Import mechanisms: DMT and supporting tools

The canonical Epicor load path is DMT, supplemented by third-party staging tools. Picking the wrong combination is how mid-migrations stall at scale.

Epicor's canonical load path is the Data Management Tool (DMT). Third-party tools like Archon, Encompass and MindHARBOR sit alongside DMT and add staging, transformation and Progress-OpenEdge extraction layers.

DMT — Data Management Tool

DMT is a Windows desktop client that ships with more than 60 prebuilt CSV and Excel import templates — Customer, Part, BOM, GL Account, AR Invoice, AP Invoice, Sales Order, Inventory Transaction, UD Table and more4. The launch path is Start → Epicor → DMT; the template builder is Template Builder within the same client. Templates accept .csv and .xlsx; columns mirror BO operation parameters one-to-one, with the key columns marked as required.

DMT runs in Add, Update or Add-or-Update mode per template invocation. Each row makes one BO call, so a 100,000-row Customer import is 100,000 sequential operations — throughput is in the 5–30 rows per second range depending on BPMs and network latency. A separate DMT Historical Data license unlocks higher-volume loads on tables like PartTran86.

DMT also supports BAQ Exports from the command line — DMT.exe -User=… -Export -BAQ=MyBAQ -Target=… produces a DMT-importable CSV from any Business Activity Query, which is the canonical pattern for extracting from a source Epicor environment.

Third-party staging tools

Archon Data Store extracts from SQL Server and Progress OpenEdge with full schema preservation, normalises across Vantage / Vista / E9 / E10, and re-links file-share attachments. MindHARBOR focuses on Prophet 21 SaaS transitions and ships a checklist covering custom SQL, integrations, reporting and scheduled automation — categories DMT does not cover. Encompass and Six S Partners run the official Epicor Data Extraction Tool for Avanté, DataFlo, Enterprise, Scala, iScala and Manage 2000113.

Mapping your data into Epicor

The longest section — because for an ERP the mapping spreadsheet is the migration. Chart of accounts, BOMs, inventory, multi-currency, fiscal cutover.

Mapping is where every Epicor migration earns its scars. The schema decisions you make in your mapping spreadsheet determine whether the Trial Balance ties out on day two, whether MRP produces sensible suggestions on day five, and whether Finance trusts the data through the first month-end close.

Work in dependency order: Currencies and UoM Classes first, then Chart of Accounts, then Customers and Vendors, then Parts and BOMs, then open AR/AP, then open Sales Orders / POs / Jobs, then GL opening balances, then on-hand inventory via PartTran. Each layer depends on the prior layer's foreign keys resolving.

Chart of accounts and GL opening balances

Epicor's Chart of Accounts is segmented under a ChartID with up to 20 segments — typical structures are Natural Account + Department + Division + Project119. Each segment has a Maintenance program with controlled values, and the composite GLAccount row is the cross-product the system allows for posting. Build the ChartID and segment values before loading any GL data; loading then becomes a DMT GLAccount Import keyed on ChartID + Account.

GL opening balances are not a single import — they are a Period 1 cutover Journal Entry posted on the conversion date. The standard pattern: freeze the source on the last business day of the prior period, close the period in the source, export the closing Trial Balance, build a Journal Entry in Epicor that mirrors the TB exactly, post it as Beginning Balance type, and reconcile the Epicor TB against the source TB to the penny115.

Use the AR Subledger, AP Subledger and Inventory Valuation reports as the authoritative reconciliation source, not the GL trial balance alone — subledger-to-GL mismatches are the most common cutover defect.

Common source → Epicor GL / Finance mapping
SourceDestinationNote
account_codeGLAccount.Account (composite)Concatenate source segments to match Epicor ChartID structure
account_descriptionGLAccount.AccountDescLength capped per Data Dictionary
currency_codeCurrency.CurrencyCodeConfigure in Currency Master with ISO 4217 code116
fiscal_periodFiscalCalendar.FiscalPeriodBuild the fiscal calendar before any posting; supports 4-4-5 and 13-period
opening balanceJournal Entry, BegBal typePost one JE per Book; reconcile to source TB to the penny
AR open invoiceARInvHed / ARInvDtl via DMTImport as open-balance only; do not re-create historical posted invoices
AP open invoiceAPInvHed / APInvDtl via DMTMatch VendorNum and PurPoint; PO-link only if the PO also migrated

Customers, vendors, parts

Common source → Epicor Customer / Vendor / Part mapping
SourceDestinationNote
customer_id / account_numberCustomer.CustID (key)Pad to Epicor field length; CustNum is system-assigned
ship_to_addressShipTo tableOne ShipTo row per address; primary flag controls default
credit_limitCustomer.CreditLimitCurrency-scoped; populate Customer.CurrencyCode first
part_number / skuPart.PartNum (key)Inventory UoM (IUM) must match a UoM Class member
part_uomPart.IUM / PartUOM child rowsConversion factors live on the UoM Class, not the Part117
part_class / categoryPart.ClassIDPre-create ClassID values; drives GL account posting rules
vendor_idVendor.VendorID (key)Multi-currency vendors need a Currency code and tax profile
tax_id / EINVendor.TaxID / Customer.TaxIDRequired for 1099 reporting (US) and VAT/GST (international)

Inventory, BOMs and units of measure

Inventory in Epicor is the union of PartWhse (warehouse-level on-hand and bin), PartBin (bin-level detail) and PartTran (every movement). On-hand at cutover loads via an Inventory Quantity Adjustment PartTran with TranType=ADJ-QTY, or via the Cycle Count Entry process for tighter controls. Lot-tracked and serial-tracked parts require LotNum and SerialNum columns; activate tracking on the Part record before loading transactions.

Units of measure are owned by UoM Class — for example a Length UoM Class contains member UoMs (inch, foot, metre) with conversion factors between them. A Part picks an Inventory UoM (IUM), Purchasing UoM (PUM) and Sales UoM (SUM) from one or more classes, and the system auto-converts on transactions117. For metals, textiles and high-value inventory, the Advanced UoM module supports dual-unit transactions122.

BOMs (Bills of Material) load against the ECO (Engineering Change Order) group of tables — ECORev (revision header), ECOMtl (material lines), ECOOpr (operations). DMT ships a multi-level BOM template that walks parent-child relationships; rev approval is a separate operation and is required before MRP will consider the BOM54. Resource Groups, Operations and Operation Resources must exist before the BOM lines reference them.

Multi-currency and historical exchange rates

Epicor stores every monetary value in both document currency and base currency (Base, Rpt1, Rpt2, Rpt3 columns). The Daily Exchange Rate table holds rates by date; loading historical AR/AP at original rates requires rate rows to exist on the document date or the load reverts to the current rate. Build the daily rate table from source history before loading open AR/AP, and post FX revaluation at cutover as a Journal Entry per Book116.

Fiscal calendar and period close

The Fiscal Calendar in Epicor supports calendar-year, 4-4-5, 4-5-4 and 13-period structures, with up to 12 or 13 periods plus an adjustment period. Build the calendar for the current fiscal year and the prior year before posting any historical data; period close in Epicor closes all sub-ledgers and locks posting, and you cannot post to a closed period without re-opening it. For the cutover period, leave it open until the Trial Balance ties out and Finance signs off.

Files, attachments and audit trail

Attachments in Epicor link to records via the XFileRef table — every Customer, Vendor, Part and OrderHed can carry attachments referenced by file path or document-management handle. Kinetic SaaS routes attachments through Epicor ECM (formerly DocStar); on-prem installs point at a file share.

The practical cap on a single attachment is around 175 MB in Kinetic cloud — anything larger errors out after a long spin105. Bulk attachment migration runs through the ECM Batch Import tab, fed by a CSV of file paths and target XFileRef keys97.

Audit trail in Epicor is opt-in. Change Log is enabled per table via a Data Directive and captures column-level changes with username and timestamp into the ChgLog table98. The standard CreatedBy, CreatedOn, ChangedBy and ChangedOn columns are system-managed — DMT stamps them with the current user and current time.

To preserve the legacy audit trail, populate two UD fields per object — Legacy Created By (Character30) and Legacy Created Date (Datetime) — from the source export, and instruct Finance to rely on those columns for historical reports.

Customisations themselves migrate via Solution Workbench exports — package BPMs, Customizations, BAQs, Dashboards, Reports and UD definitions into a Solution file, then import on the target tenant. On a cloud move from on-prem Epicor 10 to Kinetic SaaS, expect to rebuild rather than migrate code-heavy BPMs that called external assemblies or directly hit the database — Kinetic cloud's runtime restrictions block both.

The pitfalls that derail Epicor migrations

Specific failure modes — ranked by impact, each tied to the exact Epicor mechanism that breaks.

Validation and cutover

What to verify after the load, in what order — and how to fail safely when something is wrong.

Validation is the bridge between DMT finishing and users being allowed in. Epicor's own upgrade tooling ships Reconciliation Reporting with 13 prebuilt reports — AP Aging, AR Aging, GL Opening Balance, GL Debit/Credit, Trial Balance, Check Register, AP Received Not Invoiced, Open POs, Material Transactions, Quote Detail, Sales Order Backlog and Scheduled Shipments — that compare source against destination and flag variance rows. Use these as the spine of your reconciliation plan, supplemented by BAQs against the source extract.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5% variance gets investigated before users get login access.

  • GL Trial Balance by company, by book, by period — must tie to the source TB to the penny on the cutover date.
  • AR Aging total by Customer and bucket — sum of open ARInvHed rows by 0-30/31-60/61-90/90+ ageing buckets.
  • AP Aging total by Vendor and bucket — open APInvHed minus paid amount on each row.
  • Inventory Valuation by Part, Warehouse and costing method — PartWhse on-hand × cost should match source closing valuation.
  • Open Sales Order backlog — count and dollar amount on OrderHed where order not fully shipped.
  • Open PO backlog — count and dollar amount on POHeader where PO not fully received.
  • Active BOM count by Part — number of approved revisions with at least one material line.
  • User and security assignment — every active user has the same Security Group set as the source role.

On top of reconciliation, run a manual spot-check protocol: pick 30 random records across BOs and verify each field against the source UI. Pick five high-value Customers and trace the full association graph — addresses, contacts, open orders, open invoices. Pick five Parts and trace the BOM, on-hand by warehouse, cost roll-up. If a discrepancy shows up in three or more of the 30, halt the load and re-import via DMT Update mode keyed on the natural key.

Rollback in Epicor is not a button. There is no native bulk-undo for a DMT load, no equivalent to a CRM's import-batch delete. The practical fallbacks are three: (1) keep a clean SQL Server backup taken seconds before the load, and restore in place if catastrophe strikes; (2) stamp every imported row with an Import Batch ID UD field so a follow-on DMT Delete template can remove them; (3) on Kinetic SaaS, dry-run every load in Pilot before Production.

Cutover sequencing: (1) source goes read-only and the team is notified; (2) a final delta export captures everything changed during the test-load window; (3) the delta is loaded via DMT Update templates in dependency order; (4) the GL beginning-balance JE is posted to the cutover period; (5) Reconciliation Reporting runs and Finance signs off on TB, AR/AP Aging and Inventory Valuation; (6) users get access plus 72-hour hyper-care; (7) source decommission is scheduled 90 to 180 days out.

Migration partners and tools

Epicor channel partners, ETL vendors, specialist migration shops — what each is good for and how to choose.

Epicor runs a tiered Channel Partner and ISV programme — partners are certified by vertical (manufacturing, distribution, building materials, automotive aftermarket) and by product (Kinetic, Prophet 21, BisTrack, Eclipse, iScala). The right partner for any migration is the one with named projects in your vertical and your source system, not the largest partner overall135138.

Epicor itself runs Professional Services for cloud migrations and ships Analyzer, Packager/Transfer, Data Upgrade and Reconciliation Reporting as part of the Cirrus upgrade programme113. For specialist data work outside core configuration — UD fields, integrations, archived attachments — channel firms like Encompass Solutions, Six S Partners, MindHARBOR (Prophet 21), EC Solutions, Estes Group, LST Consultancy and DCKAP are commonly named113. Archon Data Store specialises in legacy Epicor extraction including Vantage, Vista, E9 and Progress OpenEdge.

On the ETL and iPaaS side, Fivetran, Airbyte, Workato, MuleSoft, Boomi and Stitch all have Epicor connectors of varying maturity. Their role in a migration is rarely the migration itself — it is the staging layer into a warehouse, the transformation layer that resolves UoM and ChartID conversions, and the ongoing-sync layer afterwards. For warehouse-first teams, Airbyte or Fivetran into Snowflake then DMT-from-warehouse is a common pattern.

Managed-migration cost ranges vary widely with edition and scope. A Vantage-to-Kinetic upgrade with light customisation lands in the £45,000–£100,000 / $50,000–$120,000 range; a NetSuite-to-Kinetic move with multi-entity finance, BOMs and 18 months of history starts around $250,000 — one documented oil-and-gas case ran 900 hours and $350,000 for 1.1M historical records. A heavy on-prem Epicor 10 to Kinetic move with 20+ customisations crosses $500,000 once conversion ($200K–$500K) and integration rebuilding ($50K–$200K) are added.

For teams that want to outsource the migration end-to-end, FlitStack specialises in ERP data migrations including Epicor and handles the field mapping, GL opening-balance posting, UoM and BOM conversion, open-AR/AP load, and reconciliation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on record count and source platform, with separate line items for historical-data depth and integration rebuilds so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want an Epicor Channel Partner, Epicor Professional Services, an iPaaS-first approach, or a specialist migration vendor. [Explore FlitStack →](/contact)

Epicor Prophet 21 migration checklist

An 8-phase task list for moving master, transactional, and historical data into Epicor ERP using the Data Management Tool, BAQs, and Solution Workbench without breaking the GL or subledger reconciliation. Typical timeline: 12–32 weeks.

0. Decide & Plan11 tasks
  • Confirm the Epicor product, vertical, and deployment model under contract. Document whether the target is Kinetic (public cloud SaaS), Epicor 10 / Epicor for Manufacturing on-premise, Prophet 21 (distribution vertical), BisTrack (building products), or iScala (international). Each vertical ships a different Business Object catalog and a different DMT template set.If skipped: Building a mapping spreadsheet against the wrong vertical surfaces missing tables and templates only after staging begins.
  • Confirm the exact Epicor release line under contract. Capture the major.minor.patch (for example Kinetic 2025.2 or Epicor 10.2.700). Customizations and DMT template versions are pinned to the release.If skipped: A DMT template built for one release silently rejects columns added in another, producing partial loads that pass row counts but fail field-level validation.
  • Define migration scope by module and business object. Document every in-scope object explicitly: Customer, Vendor, Part, BOM, Routing, GLAccount, GLJrnHed, APInvHed, ARInvHed, OrderHed/OrderDtl, POHeader/PODetail, Project, Job, FAAsset, EmpBasic, and any UD tables. Mark each as full-history, open-only, or out-of-scope.If skipped: Undocumented scope around open jobs and historical AP/AR is the single biggest cause of cutover slippage.
  • Decide how many fiscal years of transactional history migrate. Pick a cutoff in writing. Reddit and Epicor User Forum threads document 20-year historical loads that bloated LaborDtl past 2.3M rows and pushed BAQs to time out. Common cuts: open documents plus 1–3 closed fiscal years; anything older stays in an external archive or UD-table read-only store.If skipped: Importing decades of closed-period documents inflates the database, slows BAQs, and forces 2 TB+ backup windows that nobody costed in the implementation plan.
  • Decide the cutover date relative to the fiscal calendar. Anchor go-live to a period boundary — typically Period 1 of a new fiscal year. The opening-balance Journal Entry is simpler when it lands on a clean period and the fiscal calendar in Company Configuration has no partial periods.If skipped: A mid-period cutover forces partial-period journals and double-counts revenue and expense across the legacy and Epicor ledgers.
  • Decide the multi-company architecture. Pick the company structure in Epicor: single company, multi-company with consolidations, or multi-site within a single company. The choice fixes GLAccount segment design, intercompany trading, and how DMT keys parent/child records.If skipped: Switching from single to multi-company after master data loads requires rekeying Company on every downstream record.
  • Identify GDPR, SOC2, HIPAA, and retention constraints. Capture residency rules that govern which Epicor cloud region hosts the tenant (US, EU, APAC) and how long backups are retained. For EU subsidiaries on a US-hosted tenant, document the cross-border transfer mechanism before any personal data leaves the source.
  • Assign a single accountable owner for the migration. Name one DRI plus named leads for finance, distribution, manufacturing, projects, IT, and end-user enablement. Every cross-team decision routes through the DRI.
  • Document explicit success criteria for go-live. Write down what must be true to declare cutover complete — trial balance ties to source within a defined tolerance, AR and AP aging match by customer and vendor, inventory quantity-on-hand reconciles by part and warehouse, open sales and purchase orders all loaded, BOMs and routings approved.
  • List out-of-scope items in writing. Examples: historical email threads, legacy custom SSRS reports, terminated employee records past retention, closed jobs older than the cutoff, change-log entries pre-cutover. Circulate the list to all stakeholders.If skipped: Items not explicitly out-of-scope reappear as last-minute demands during sandbox testing.
  • Set and communicate the source-system freeze window. Pick the date and time after which no new transactions post in the legacy system. Broadcast it to every team that writes to the legacy.If skipped: Late writes to the source after final export create a delta no one reconciles until users notice missing transactions post-cutover.
1. Pre-Migration Prep20 tasks
  • Run dedup analysis on source customer and vendor masters. Match on tax ID, legal name + country, and primary contact email. Resolve flagged duplicates in the source before export — merging in Epicor after the fact requires reversing AR and AP history.If skipped: Duplicate customers loaded into CustGroup or Customer tables fragment AR aging and break credit-limit logic.
  • Standardize part-number formatting in the source. Force a single case (commonly upper), strip leading or trailing whitespace, and replace separators that conflict with Epicor's PartNum constraints. Part-number normalization done in the source is one-pass; done in Epicor after load it cascades across PartBin, Job, Quote, and Order tables.If skipped: Mixed-case part numbers create phantom duplicates in inventory and break BOM resolution.
  • Normalize phone, country code, and address formatting. Pick one phone format (E.164 recommended), one country-code standard (ISO 3166-1 alpha-2), and one address-line convention. Apply across Customer, Vendor, Contact, and EmpBasic source records.
  • Identify and resolve records with missing required fields. Epicor business objects enforce non-null on a defined set of fields per release. Run a profile pass against the source for blank Company, CurrencyCode, SalesTerritory, ClassID (parts), and similar mandatories.If skipped: DMT silently skips rows missing required fields and reports them only in the job log, so partial loads can pass row-count checks but fail business validation.
  • Resolve picklist value mismatches against Epicor user codes. Source values for terms, ship-via, FOB, currency, country, sales tax, and similar must map to entries you will load into UserCodes. Build the mapping now, not at transform time.
  • Re-encode all source extracts to UTF-8 without BOM. Latin-1 and Windows-1252 source files corrupt diacritics in customer and vendor names on import. Force every extracted file to UTF-8 before any transformation.If skipped: Mojibake in customer and contact names is hard to spot until a user reports an email going to the wrong person.
  • Export current record counts per object as a baseline. Persist a dated baseline CSV with one row per source object and its row count. Use this for Phase 6 reconciliation deltas.
  • Provision production and sandbox/pilot environments. Confirm pilot is a clean clone of the intended production configuration. Lock the version of pilot to the version production will go live on; do not let Epicor's cloud auto-upgrade pilot mid-project.If skipped: A pilot one minor release ahead of production silently diverges DMT templates and Business Object signatures.
  • Configure Company Configuration before any data lands. Set base currency, fiscal calendar, period structure, tax liabilities, default plant, and country-of-incorporation. These drive validation on every downstream import.If skipped: Changing base currency after master data loads requires a full reload — Epicor stores monetary values pre-converted on each row.
  • Build the chart of accounts and segment structure first. Define the GL Control segment plus department, division, project, or other COA segments via Chart of Accounts Maintenance. The segment structure is foundational and rebuilding it after journal data lands is extremely costly.If skipped: Changing segment count or width post-load forces a database-level rewrite of every posted GL row.
  • Define the fiscal calendar and open the relevant periods. Set fiscal-year start, period count, and period close cadence in Company Configuration. Open the periods you intend to post into; closed periods reject DMT loads.
  • Load currencies and set up daily exchange-rate import. Create every currency the business transacts in, then configure the exchange-rate maintenance pattern (manual entry or BAQ-driven) before any multi-currency document is loaded.If skipped: Loading foreign-currency invoices without an exchange rate for the document date posts them at zero rate and corrupts the GL.
  • Create all UD fields and UD tables before any DMT load. Use User Defined Column Maintenance and Solution Workbench to add UD columns to every business object that needs them. DMT will only populate columns that exist when the template is generated.If skipped: DMT silently drops data in columns that do not exist in the destination, so missing UD fields cause invisible loss.
  • Create UserCodes for every source picklist mapped in 1a. Load reason codes, terms, ship-via, FOB, sales territory, and similar via UserCodes Maintenance or the DMT UserCode template before any document import references them.
  • Provision named users with appropriate security groups. Create every user in the User Account Security screen — or via the DMT UserFile template — with the correct security groups, company access, and site access before cutover.
  • Stage Solution Workbench solutions for BPMs, BAQs, dashboards, and customizations. Build BPMs that enforce business rules and personalizations as Solutions in pilot. Export the solutions so they ship to production as a single artifact at cutover.
  • Pause all outbound integrations on the destination. Disable scheduled Service Connect workflows, EDI triggers, BPM email notifications, and any external integration that fires on master-data or document creation during load.If skipped: Integration noise during DMT loads sends spurious notifications to customers and vendors and pollutes downstream systems with not-yet-real data.
  • Communicate the freeze window to every source-system user. Calendar invite, internal wiki page, and stand-up announcement. Confirm acknowledgment from each functional lead.
  • Schedule role-based training on Kinetic before cutover. Per the 2026.1 release notes the Classic smart client is being retired; train only on the browser-based Kinetic UI. Segment training by role: finance, sales, purchasing, inventory, production.If skipped: Training users on the Classic shell creates double change-management debt when the shell is removed in a later release.
  • Designate first responders for the first 72 hours post-cutover. Name one person per functional area who triages user issues and routes data discrepancies to the migration DRI.
2. Source Export12 tasks
  • Export GL chart of accounts with full segment values. One row per account; include every segment (control, department, division, project, etc.). Preserve account type and posting flag.
  • Export the GL trial balance as of cutover for every period in scope. One file per period. Debits and credits per account-segment combination. This is the source of truth for the opening-balance journal in Phase 3.If skipped: Without a frozen trial balance snapshot you cannot prove the destination ties to the source in Phase 6.
  • Export customer and vendor masters with all standard and UD fields. Include billing and shipping addresses, terms, credit limit, tax ID, default currency, and any extension fields. Export contacts separately keyed to the parent record.
  • Export the Part master with UoM Class, default plant, and class. Capture PartNum, base UoM, UoM Class, costing method, product group, class, and the inventory and revenue GL controls.If skipped: Missing UoM Class on the Part master breaks every transaction that converts between purchase, stock, and sales UoMs.
  • Export BOMs and routings, parent-then-child. Multi-level BOMs export as a flat list of parent PartNum + child PartNum + quantity + UoM rows; routings as Operation + Resource Group + standard times. Maintain the sequence numbers exactly.
  • Export inventory on-hand, on-order, allocated, by Part, Plant, Warehouse, and Bin. One row per Part-Plant-Warehouse-Bin-LotNum-SerialNum combination. Lot and serial-controlled parts need every dimension.If skipped: Aggregating quantities above the bin or lot level loses the granularity Epicor needs to reconcile cycle counts.
  • Export open AP and AR invoices with aging buckets and remaining balance. Header plus line for each open document. Capture original date, due date, terms, currency, original amount, and current open amount.
  • Export open sales orders, purchase orders, jobs, and projects. Header and line for each. Open quantity and dollar amounts only; shipped or received quantities are out of scope unless explicitly in.
  • Export payment, cash-receipt, and bank-account configuration. Bank accounts, AR payment terms, payment methods. These configure cash-application behavior on day one.
  • Export attachments and document metadata from the source DMS. For each attachment, capture the binary file, the source record key (e.g. invoice number), the file name, MIME type, and original upload date. Note Epicor Kinetic Cloud attachments cap at approximately 175 MB per file per the user forum; flag any source file larger than the cap.If skipped: Files larger than the destination cap need a Phase 3 decision (split, store externally, or skip); discovering the cap at cutover breaks the attachment migration.
  • Capture configuration exports for every report, dashboard, and automation. SSRS reports, BAQs, dashboards, scheduled jobs, workflow rules, and external integrations are rebuilt manually in the destination. Screenshot or XML-export each one for the Phase 7 rebuild.
  • Timestamp every export file and persist the manifest. One CSV manifest row per exported file with filename, source-table name, row count, and ISO-8601 export timestamp. This is the audit record of what was in scope at cutover.
3. Transform & Map26 tasks
  • Build a master mapping spreadsheet keyed by Epicor business object. One tab per target object (Customer, Vendor, Part, BOM, Routing, GLAccount, OrderHed, OrderDtl, APInvHed, ARInvHed, etc.). For each source field, document the destination column, the transformation rule, nullability, and whether it is required by the DMT template.If skipped: Without a master mapping, multiple analysts make conflicting decisions about the same field and the contradictions surface only in sandbox.
  • Decide the upsert key per object. Typical keys: CustNum or CustID for Customer, VendorNum or VendorID for Vendor, PartNum for Part, plus Company on every row. Persist the key choice in the mapping sheet.
  • Decide handling for source fields with no destination equivalent. Per field, pick one: drop, concatenate into a Comment or Notes column, or create a UD field. Implement UD-field creation in Phase 1b before this transform completes.
  • Validate every transformed value against the destination type catalog. Epicor types include nvarchar with hard length limits, decimal(28,8) for monetary, datetime, and bit. Truncation or rounding rules must be explicit in the mapping sheet.If skipped: Implicit truncation on long Description fields silently loses information that auditors will eventually ask about.
  • Convert all dates to ISO-8601 with explicit timezone. Use yyyy-MM-ddTHH:mm:ssZ. DMT accepts shorter forms but ambiguity around DD/MM versus MM/DD parses silently wrong on locale-different rows.If skipped: Date-format drift on transactional dates pushes documents into the wrong fiscal period.
  • Normalize decimal separator and precision per Epicor type. Use dot decimals everywhere. Round monetary values to the precision the destination column accepts (commonly 4 or 8 places). Truncate, do not round, on quantity fields where the source carries spurious extra digits.
  • Truncate or split source fields that exceed Epicor column limits. For each source field longer than the destination, decide: truncate with logged loss, split into multiple fields, or overflow into a Comment Text record. Document the choice in the mapping sheet.
  • Re-encode every transformed file to UTF-8 without BOM. DMT accepts UTF-8 cleanly; a leading byte-order mark on column-1 of row-1 makes the first column look unrecognized.If skipped: A stray BOM is a one-character bug that fails the entire file with a misleading column-name error.
  • Escape commas, quotes, and newlines in free-text fields. DMT consumes CSV and XLSX. For CSV, quote every field containing a comma, double inner quotes, and replace embedded newlines with a literal escape if the destination type does not accept multi-line content.
  • Generate external-ID columns on every object for upsert idempotency. Carry the source primary key into a UD column (e.g. UD_LegacyID) on every object. This is the rerun-safe handle if a Phase 5 load step fails partway.If skipped: Without external IDs, re-running a failed load creates duplicates or silently overwrites unrelated rows.
  • Decide and implement strategy for original document dates. Source create-dates on AP, AR, and sales orders are valuable for aging. Decide per object: load the source date into the destination Date field (best for aging accuracy) or capture it in a UD_OriginalDate field while the create-stamp reflects load date.
  • Decide and implement record-ownership strategy. Either map source owner to the matching Epicor user by email, or assign every migrated row to a placeholder data-migration user and reassign in Phase 7.
  • Decide and implement the attachment strategy. Two paths: re-upload binaries into Epicor's attachment store (subject to the per-file size cap), or keep binaries on an external store and load only the URL into a UD field. Decide per attachment class.
  • Enable change-log data directives only after historical load completes. Change-log capture writes a row to the change-log tables on every update. Leaving directives enabled during DMT loads multiplies database growth by the number of migrated rows.If skipped: Loading 1M+ rows with change-log directives enabled balloons the change-log table and degrades load throughput.
  • Build the GLAccount file with full segment values per the destination COA. One row per account combination. Validate every segment value against the segment masters loaded in Phase 1b. Mark account type (Asset, Liability, Equity, Revenue, Expense) and posting flag.If skipped: Loading GL transactions before GLAccount completes pushes every line to a suspense account and reconciliation has to be re-done.
  • Prepare the GL opening-balance Journal Entry as a Period 1 BegBal journal. Build one Journal Entry whose lines mirror the Phase 2 trial balance snapshot. Post it to Period 1 of the cutover fiscal year. Exclude current-year P&L lines if you also intend to import current-year posted invoices, or you will double-count income.If skipped: Either an opening journal that includes YTD income or current-year invoices loaded on top of an opening journal that already contains them double-counts income.
  • Verify debits equal credits on the opening-balance journal before staging. A balanced journal is required to post. Run the sum check before saving the DMT input file.
  • Build the Part master file with UoM Class and default plant. One row per Part. Reference the UoM Class loaded in 1b; reference the Plant loaded in 1b. Set base UoM, costing method, product group, class, inventory GL control, and revenue GL control.
  • Build the UoM Class, UoM, and UoM Conversion files before the Part master loads. Epicor's Advanced UoM module supports dual UoMs and attribute-driven conversions. Decide per Part class whether Advanced UoM applies. Stage UoM Class first, UoM second, conversions third, and Part fourth.If skipped: Loading Parts before the UoM Class they reference fails the row; loading them after a partial UoM Class load corrupts the link with no hard error.
  • Build the BOM file parent-then-child, level by level. Multi-level BOMs cannot load bottom-up — DMT validates that the child PartNum exists when the parent row references it. Sort the file by BOM level ascending. Stage Routings in parallel keyed to the same Part.If skipped: An out-of-order BOM file rejects the child row before the parent and produces an incomplete bill of materials.
  • Build inventory-on-hand files at Part-Plant-Warehouse-Bin-LotNum-SerialNum granularity. Match the source export granularity from Phase 2. Lot-controlled parts need every LotNum row; serial-controlled parts need every SerialNum row. Quantities post via the Quantity Adjustment business object, not by writing PartBin directly.If skipped: Direct writes to PartBin bypass costing logic and break the inventory-to-GL tie at the next inventory revaluation.
  • Stage daily exchange rates for every active currency. Load enough history of daily rates to cover the dates on every multi-currency document being imported. The CurrencyExRate business object accepts DMT uploads.If skipped: Missing a rate for a document date causes the document to post at the wrong converted amount, silently corrupting the multi-currency GL.
  • Prepare open AP invoices for DMT into APInvHed and APInvDtl. Header plus lines per open invoice. Document date drives aging; due date drives the cash forecast. Validate that every Vendor and PurPoint exists from Phase 1b.
  • Prepare open AR invoices for DMT into ARInvHed and ARInvDtl. Header plus lines per open invoice. Validate that every Customer, ShipTo, and salesperson exists. Carry tax amounts in the source currency, not pre-converted.
  • Build the AR and AP open-payment files keyed to invoices. Partial payments need to attach to the invoice they applied against. Stage Cash Receipts and Payment Headers keyed by invoice GroupID.
  • Build fiscal-calendar and period-close configuration before the first transactional load. Confirm fiscal years and periods are open in Fiscal Calendar Maintenance for every period any document references. Closed periods reject DMT row-by-row.
4. Sandbox Test Migration11 tasks
  • Load a 1–5% representative sample of each object into pilot. Sample by date range (e.g. one month of orders), customer tier (top 10 plus bottom 10), and part class (one row per ProdGroup). Use DMT's standard templates.
  • Validate field-by-field on 10 random sandbox rows per object. Open the record in the Kinetic UI and compare every field against the source extract. Spot edge cases: long descriptions, special characters, NULL handling, multi-currency values.If skipped: Row-count checks pass while field-level corruption hides until a user opens the record in production.
  • Run a full-volume DMT load against pilot for the largest object. Per the DMT documentation, large jobs are limited by application-server throughput. Time the load and extrapolate to production volume.If skipped: Loading 500K rows in pilot at the wrong concurrency setting wedges the application server and stretches cutover past the planned window.
  • Test multi-level BOM and Routing import in dependency order. Confirm the BOM file sorted by level ascending loads cleanly. Confirm Routings load against the same Part and that resource groups resolve.If skipped: An out-of-order BOM load rejects child rows and leaves an incomplete bill of materials that production-control will catch only at the first job.
  • Test the opening-balance Journal Entry posts cleanly to Period 1. Stage the BegBal journal via DMT, post it, run a trial balance, and tie the trial balance back to the source.If skipped: An unbalanced or wrong-period opening journal taints every downstream financial report from go-live forward.
  • Test inventory quantity adjustments to PartBin. Load on-hand via QuantityAdjustment, then run a Stock Status Report. Confirm Part-Plant-Warehouse-Bin-Lot-Serial totals match source on-hand.
  • Test multi-currency invoice import for a non-base currency. Load one foreign-currency AP and one foreign-currency AR invoice. Confirm both the document amount and the converted amount post correctly using the staged daily rate.If skipped: A misconfigured exchange-rate type produces invoices that look right on the document and wrong on the GL.
  • Test attachment upload via DMT XFileAttch. Upload a representative sample of attachments, including the largest file in scope, to confirm none of them hit the per-file cap (approximately 175 MB on Kinetic Cloud).If skipped: Discovering the file-size cap mid-cutover forces an emergency external-storage plan.
  • Run a full-cycle business test in pilot: create order → ship → invoice → cash. Pull a real customer, create a sales order with migrated parts, ship from a migrated bin, invoice in a migrated period, apply cash. Confirm GL postings are correct.
  • Time the end-to-end sandbox load and extrapolate to production. Record wall-clock per object. Multiply by the production-to-pilot row ratio and compare to the cutover-window budget.If skipped: An end-to-end load that runs longer than the cutover window in pilot will not magically run faster in production.
  • Have finance, operations, and a power user sign off pilot results. Written sign-off naming the artifacts reviewed and the issues outstanding. Block Phase 5 on sign-off.
5. Production Cutover13 tasks
  • Confirm source freeze and verify no new writes in the last hour. Query the source for the latest update timestamp on every in-scope table. Confirm it is older than the freeze cutoff.If skipped: A single late source write produces a reconciliation delta nobody hunts down for weeks.
  • Take the final source export (delta from Phase 2 baseline). Re-export every in-scope object. Diff against the Phase 2 export and merge the delta into the transformed files.
  • Confirm BPMs, data directives, and integrations are paused on the destination. Disable in-transaction and post-processing data directives, BPM email actions, and Service Connect schedules. Re-enable only after Phase 5 completes.If skipped: A live BPM emailing every Customer record-creation event spams thousands of contacts during cutover.
  • Load masters first: UserCodes, Plants, Warehouses, Bins, COA segments. These are the foundation. Every subsequent load depends on these existing.
  • Load users, then Customer and Vendor masters. UserFile via DMT, then Customer via DMT, then Vendor. Each by its DMT template.
  • Load Part master, UoM Class, UoM, BOM, and Routing in dependency order. UoM Class → UoM → UoM Conversion → Part → BOM (level ascending) → Routing. Each step must complete before the next begins.If skipped: Skipping the level-ascending order on BOM leaves orphan child rows that production-control surfaces at first job creation.
  • Post the GL opening-balance Journal Entry to Period 1. Load via DMT, then post via the Journal Entry business object. Run a trial balance immediately and compare against the Phase 2 source snapshot.If skipped: Posting before debits=credits is checked corrupts every downstream financial report.
  • Load inventory on-hand via Quantity Adjustment. Run the QuantityAdjustment DMT template. Run a Stock Status Report and tie back to the source.
  • Load open AP invoices into APInvHed/APInvDtl, then open AR into ARInvHed/ARInvDtl. Header file before line file for each. Load partial payments after both invoice loads complete.
  • Load open sales orders, purchase orders, jobs, and projects. Header before lines on every object. Open quantities and balances only; do not load already-shipped or already-received history unless explicitly in scope.
  • Load attachments last, keyed to the records that own them. Attachments depend on the parent record existing. Run XFileAttch after parent loads succeed.
  • Capture import job IDs, row counts, and error logs for every step. Persist the DMT log file in a dated cutover-evidence folder. These are the audit record.If skipped: Without logs you cannot reproduce a failed load idempotently or prove a number to an auditor later.
  • Re-enable BPMs, data directives, change-log capture, and integrations. Only after every load step has signed-off row counts. Smoke-test each integration with a single record before unpausing the rest.
6. Validate16 tasks
  • Compare per-object row counts: source vs destination. Build a BAQ per object that returns the destination row count and place it next to the Phase 2 baseline. Investigate every non-zero delta.If skipped: A 1% row-count delta sounds small until it lands on AR invoices and the customer with the missing row notices first.
  • Run the Epicor Trial Balance and tie to the source trial balance. Per the 10.2.400 Reconciliation Reporting reference, run GL Trial Balance, GL Opening Balance, AP Aging, AR Aging, Open POs, and Material Transactions; tie each back to the source.If skipped: An unreconciled trial balance at go-live becomes a year-end audit finding.
  • Reconcile AP aging by vendor. Run AP Aging in Epicor and compare per-vendor balances to the source aging snapshot. Differences should be zero or explainable.
  • Reconcile AR aging by customer. Run AR Aging and tie per-customer balances to the source. Confirm bucket cutoffs match the source aging policy.
  • Reconcile inventory on-hand by Part, Plant, Warehouse, Bin. Run a Stock Status Report or BAQ that aggregates PartBin and compare to the Phase 2 source export.If skipped: Inventory rebuilds done after go-live break the GL-to-inventory tie because cost layers were never recreated.
  • Cross-check 25–50 random records per object field-by-field. Sample customers, vendors, parts, invoices, orders, BOMs, and attachments. Compare every populated field in source vs destination.
  • Verify parent-child relationships on a sample. Order header → order lines, invoice header → invoice lines, BOM parent → BOM children, Job → JobAsmbl → JobOper → JobMtl.
  • Verify ship-to and bill-to associations on customers. Each migrated customer should resolve to the right CustShipTo and CustBillTo. Spot-check 20 random customers.
  • Verify attachment-to-record links resolve and the file opens. Open the attached file from the parent record in the Kinetic UI for a random sample of 25 attachments. Confirm the right file opens.
  • Verify UD-field values arrived intact on every object that has UD fields. DMT silently drops data in non-existent columns; this is the last chance to catch a UD field that was renamed between mapping and load.
  • Confirm change-log data directives are now enabled in production. Per the audit-trail discussion in the Epicor User Forum, change-log capture is enabled per table via data directive on the columns you care about. Activate the agreed-upon set in production.
  • Run the GDPR data-subject lookup against a known person. If the destination tenant hosts EU personal data, confirm the data-subject access workflow returns all the fields it should. Validate the data-residency commitment matches the tenant region.If skipped: A GDPR mismatch found in audit costs more than the entire migration project.
  • Snapshot the Phase 5 evidence pack (DMT logs, row counts, sign-offs) to long-term storage. SOC2 and HIPAA evidence requirements typically demand the migration log be retained alongside the migrated data.
  • Have power users from each function run their day-1 workflow on real migrated data. Sales creates an order from a migrated customer. Purchasing creates a PO against a migrated vendor. Inventory issues material to a migrated job. Finance posts a payment against a migrated invoice.
  • Document data issues surfaced by UAT and decide fix-now vs fix-later. Triage every issue: blocking (fix before go-live), cosmetic (fix in Phase 7), or acceptable. Persist the triage decision.
  • Get written sign-off from the migration sponsor before opening production. Name the artifacts: trial-balance match, AR/AP aging match, inventory match, UAT triage decisions, evidence pack. No production login until sign-off.
7. Post-Migration Cleanup11 tasks
  • Announce go-live with login instructions and a where-to-get-help contact. Include the Kinetic URL or on-prem launch path, named first responders, and a known-issues list.
  • Run role-based training sessions on the Kinetic browser UI. Segment by function. Confirm every named user has logged in once within the first 5 business days.
  • Set the source system to read-only and announce the read-only date. Revoke write permissions in the source. Keep read access for the planned retention window.
  • Rebuild reports and dashboards in Epicor via BAQ + SSRS or Kinetic dashboards. Source reports do not transfer. Use the Phase 2 configuration captures to rebuild the equivalent in BAQs, BAQ Reports, and SSRS.If skipped: Missing reports at month-end forces finance back to spreadsheets and erodes confidence in the new system.
  • Promote BPMs, personalizations, and customizations from pilot via Solution Workbench. Export the pilot solution package and import into production. This is the upgrade-safe path documented in the Epicor User Forum.If skipped: Hand-recreating BPMs in production diverges them from pilot and breaks the next upgrade.
  • Re-establish integrations to external systems. EDI, banking, CRM, payroll, calendar sync, BI tools. Smoke-test each one before unpausing scheduled jobs.
  • Reassign ownership from the data-migration placeholder user to real users. If you used a placeholder owner in Phase 3, run a BAQ-driven update to set CreatedBy and ChangedBy to the real owners now.
  • Schedule the 30-day retrospective. Capture what went well, what didn't, and the residual issue list from Phase 6 UAT triage.
  • Decide and document the source-system decommission date. Typically 90 days after cutover. Confirm the retention obligation is independently satisfied by the archived exports.
  • Archive all source exports, mapping spreadsheets, DMT input files, and DMT logs. Long-term cold storage labeled by cutover date. This is the forensic record if a discrepancy surfaces months later.If skipped: Without archived exports, a year-end audit question about a migrated transaction has no source of truth to reference.
  • Close out the migration project formally with a final status report. Final task counts, residual issues with owners, lessons learned, and the link to the 30-day retrospective.

Questions, answered

Migrating to Epicor Prophet 21: questions

How long does migration to Epicor take?

A clean Vantage-to-Kinetic upgrade with light customisation runs 6 to 9 months. A NetSuite or Dynamics-to-Kinetic move with multi-entity finance, BOMs and 18 months of history runs 9 to 15 months. A heavy on-prem Epicor 10 with 20-plus customisations crosses 12 to 18 months of elapsed time.

Can I migrate from NetSuite to Epicor Kinetic?

Yes, and the Reddit r/Netsuite thread documents the inverse with cost numbers: 1.1 million records across Field Service, Sales Orders, POs, AP and AR can run 900 hours and $350K through a managed-services vendor. NetSuite SuiteScript and saved searches do not transfer — rebuild as BAQs and BPMs.

Can I migrate from QuickBooks or Sage to Epicor?

Yes — QuickBooks and Sage 50/100 are common Prophet 21 and Kinetic source systems. Standard objects map cleanly via DMT, but QuickBooks does not enforce ChartID segments or controlled UoM, so plan an extensive cleansing pass on customer master, vendor master, chart of accounts and item master before extract.

Does Epicor preserve original timestamps on import?

No. CreatedBy, CreatedOn, ChangedBy and ChangedOn columns are system-managed and stamped with the DMT user and current time on every imported row. To preserve the original audit trail, add Legacy Created By (Character30) and Legacy Created Date (Datetime) UD fields on each target table and populate them from the source export.

What is the canonical Epicor import path?

DMT — the Data Management Tool — is the canonical first-party path. It ships with 60-plus prebuilt CSV and Excel templates that call Business Objects row-by-row, and a separate Historical Data license unlocks higher-volume loads. Third-party tools like Archon stage the data before DMT for large or Progress-OpenEdge sources.

What happens to open AR and AP invoices during migration?

Import open AR and AP invoice headers and lines via DMT into ARInvHed/ARInvDtl and APInvHed/APInvDtl with the open balance as the line amount, not the original gross. Match VendorNum and CustNum to the master records loaded earlier. Reconcile the AR Aging and AP Aging reports to the source aging report to the penny.

Is there an undo or rollback for an Epicor DMT load?

No native bulk-undo. Three practical fallbacks: keep a SQL Server database backup taken seconds before the load; stamp every imported row with an Import Batch ID UD field so a DMT Delete template can remove them by batch; on Kinetic SaaS, dry-run every load in Pilot before Production for every template.

Get a quote

Moving to Epicor Prophet 21?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Epicor Prophet 21 setup with you, then send a quote.

Get a quote