NetSuite to Epicor Prophet 21 migration
We migrate Accounts, Customers, Vendors, Items, and transactional history from NetSuite into Epicor ERP with the subsidiary-to-company architecture resolved upfront, BOM and work order structures preserved for manufacturing environments, and every NetSuite custom field mapped to its Epicor UD-field equivalent before cutover.
FlitStack AI migrates companies, customers, vendors, part / partplants and eco and jobmtl / jobopers from NetSuite to Epicor Prophet 21, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 6-10 weeks.

What moves from NetSuite to Epicor Prophet 21?
Moving from NetSuite to Epicor ERP is a structural migration driven by industry fit and operational performance.
Read the full summary
NetSuite's unified database with subsidiary-aware intercompany eliminations maps to Epicor's multi-company structure, which requires each legal entity to be a separate Epicor company without built-in consolidation elimination entries. We resolve this architectural gap during discovery by designing the subsidiary-to-company map and determining whether intercompany transactions should become standard journal entries, internal sales orders, or a separate consolidation strategy. NetSuite's SuiteQL extraction layer, custom field registry (custbody_*, custrecord_*, custentity_*), and API concurrency ceiling of 15-55 simultaneous requests per tier shape our extraction approach; we chunk by date ranges and service tier capacity. Epicor ERP does not migrate Workflows, automations, SuiteFlow sequences, or SuiteScript customizations as code; we deliver a written inventory of every NetSuite automation requiring rebuild in Epicor Business Process Management (BPM) or Kinetic framework. For manufacturing customers, BOM and routing complexity is the primary timeline driver.
Account → Company
NetSuite Accounts (chart of accounts records identified by account type codes and optionally acctNumber) map to Epicor GL Account segments.
How it maps
NetSuite account types (0=Bank, 1=AR, 2=Inventory, 10=AP, 21=Income, 23=COGS, 24=Expense) map to Epicor COA segment values under the configured account structure. We preserve full account number, name, and type. Epicor's account segment structure requires mapping NetSuite's flat account list into Epicor's segmented account format (typically Company-Branch-Natural Account or equivalent per the customer's Epicor COA configuration). The mapping is defined during discovery against the customer's Epicor Chart of Accounts structure.
Customer → Customer
NetSuite Customers map directly to Epicor Customer records.
How it maps
The NetSuite entity ID becomes the Epicor CustID, and the customer name, address, contact information, credit terms, and tax registration migrate to Epicor Customer and CustShip records. NetSuite Customer fields like creditlimit, terms, and region map to Epicor Customer.CreditHold, Customer.TermsCode, and Customer.SalesRepID. Multi-address NetSuite customers map to multiple Epicor CustShip records linked to a single Customer.
Vendor → Vendor
NetSuite Vendors map to Epicor Vendor records.
How it maps
NetSuite entity ID becomes Epicor Vendor.VendorID, and standard fields (name, address, contact, payment terms, 1099 flag) migrate to equivalent Epicor Vendor fields. Tax ID from NetSuite maps to Vendor.TaxID for US 1099 reporting. Multi-address vendors map to multiple Epicor VendRemitTo or VendorPP records.
Subsidiary → Company
NetSuite's subsidiary model lets one database represent multiple legal entities with intercompany eliminations.
How it maps
This is the most structurally significant mapping decision in a NetSuite-to-Epicor migration. Epicor does not support a single-database multi-entity model with automatic intercompany eliminations. Each NetSuite subsidiary must map to a distinct Epicor Company, and intercompany transactions must be reclassified as standard journal entries, internal sales orders, or an external consolidation strategy. We build the subsidiary-to-company map during discovery, validate posting group assignments in Epicor before data lands, and present the intercompany treatment options (eliminate, keep as-is, consolidate manually) as a decision point documented in the migration contract.
Item (Inventory Assembly, Service, Non-Inventory) → Part / PartPlant
NetSuite Items (inventory assembly, non-inventory, service, description-only) map to Epicor Part records with PartPlant configuration for inventory-specific settings.
How it maps
The NetSuite item type maps to Epicor Part.TypeCode (MFG, PHant, PKG, etc.). Unit of measure from NetSuite maps to Epicor Part.IUM and Part.DUM. Pricing matrices migrate to Epicor Part.PriceList or OrderDtl base pricing. Build assemblies, BOM relationships, and landed cost fields require mapping to Epicor's engineering and costing modules during the BOM mapping phase.
BOM (Bill of Materials) and Work Order → ECO (Engineering Change Order) and JobMtl / JobOper
NetSuite Bill of Materials on assembly items map to Epicor Engineering BOM (EBOM) and ECO (Engineering Change Order) structures.
How it maps
NetSuite work orders map to Epicor Job records with JobMtl (materials) and JobOper (operations/routing) entries. This is the highest-complexity manufacturing mapping because NetSuite nests BOMs under assembly items while Epicor manages BOMs as separate Engineering records linked to Part numbers. Routing steps (NetSuite manufacturing routing) map to Epicor JobOper with work center references. We recommend scoping BOM and work order migration only for active or recent records; historical completed work orders typically convert to job cost history without full reconstruction.
- AccountCompany1:1
- CustomerCustomer1:1
- VendorVendor1:1
- SubsidiaryCompanysplit
- ItemPart1:1
- BOM and Work OrderECO and JobMtltransformed
+ 11 more in the mapping below
How NetSuite and Epicor Prophet 21 differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | NetSuite | Epicor Prophet 21 |
|---|---|---|
| Multi-entity model | Single database with subsidiary-aware intercompany eliminations | Separate Epicor companies, one per legal entity; no built-in consolidation elimination |
| Manufacturing depth | Inventory assembly, BOM, and work orders as standard modules | Kinetic, Prophet 21, and industry-specific MES; deeper job costing and scheduling |
| Customization approach | SuiteBuilder custom fields, custom records, SuiteFlow; no downtime for field adds | UD Codes, BPM, .NET/Angular extensions; field adds require development and testing downtime |
| Custom field registry | Prefix-based custom fields (custbody_*, custrecord_*, custentity_*) with script IDs | UD fields defined per-table; no universal naming pattern, require per-entity discovery |
| API and extraction | SuiteQL with 15-55 concurrent request ceiling per tier, date-bounded batches | REST and OData APIs; Kinetic offers GraphQL; Epicor Data Interface (EDI) for bulk |
| Lot and serial tracking | Lot/serial number assigned at transaction time; tracked in inventory records | PartTran-driven; lot/serial numbers managed through PartLot table and UD Codes |
| Reporting | Real-time dashboards and saved searches; hundreds of native reports | SSRS and Crystal Reports; prone to breaking; specialists required for custom reports |
What to watch for in a NetSuite to Epicor Prophet 21 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
NetSuite subsidiaries require a multi-company Epicor design before any data maps
NetSuite's single-database subsidiary model with built-in intercompany elimination has no direct Epicor equivalent.
How we handle it
Each NetSuite subsidiary must become a separate Epicor Company, and Epicor companies do not share a database or perform automatic elimination entries. Intercompany transactions from NetSuite (sales between subsidiaries, eliminations, intercompany journal entries) require a pre-migration decision: whether to create equivalent intercompany transactions in Epicor as internal orders and journals, carry eliminations forward manually, or consolidate separately after migration. We present this as a required discovery decision and document the chosen treatment in the migration contract. Skipping this step results in a consolidated trial balance that does not match the NetSuite source after migration.
NetSuite custom fields require per-account discovery before Epicor UD field design
NetSuite custom fields (custbody_*, custcol_*, custentity_*, custitem_*, custrecord_*) have no public schema documentation and vary per account.
How we handle it
We run a metadata discovery pass against the NetSuite SuiteQL endpoint to enumerate all active custom objects and fields before building any migration map. Each discovered custom field maps to an Epicor UD field on the equivalent table. Custom fields on transaction lines (custcol_*) must be added to Epicor's line tables (OrderDtl, POLine, InvoiceDtl) as UD columns, which requires Epicor administrator access and, in on-premise deployments, potentially a test cycle with downtime. We scope this as a prerequisite before any record migration begins.
BOM and work order complexity drives the majority of migration timeline variance
NetSuite inventory assemblies with nested BOMs (sub-assemblies, multi-level bills of materials) and active work orders are the highest-complexity migration objects.
How we handle it
Epicor manages BOMs as separate Engineering Change Order (ECO) records linked to Part numbers, not as nested sub-records under the assembly item as in NetSuite. Routing steps in NetSuite manufacturing routings map to Epicor JobOper entries with work center references that must be validated against the Epicor Resource Group configuration. We recommend migrating only active or recently completed work orders; deep historical work order reconstruction is rarely operationally necessary and dramatically increases migration scope. BOM migration for organizations with more than 200 assemblies and three or more BOM levels moves the timeline from six to ten weeks to fourteen to twenty-six weeks.
Lot/serial tracking and PartTran history require sequential migration after Part setup
NetSuite lot and serial numbers are stored in inventoryDetail subrecords on transactions and can be queried via SuiteQL joined to transaction lines.
How we handle it
Epicor tracks lot movements via PartTran, which is generated when a lot is received, transferred, issued, or shipped. Lot and serial numbers cannot be migrated independently; they must be migrated after Part and PartPlant are configured in Epicor. We extract NetSuite lot/serial assignments per transaction line, map them to Epicor PartLot records with expiry and bin assignments, and then create the corresponding PartTran entries to establish the on-hand balance trail. Migrations that skip this sequencing result in orphan PartLot records with no transaction history and incorrect on-hand quantities in Epicor.
Epicor's hybrid deployment model changes API and extraction approach per customer
Epicor offers on-premise, hosted, and cloud-based deployments.
How we handle it
Cloud-based Epicor Kinetic and Epicor ERP SaaS use REST/OData APIs accessible from our extraction environment without VPN requirements. On-premise deployments require VPN connectivity or a secure file transfer mechanism that must be scoped during discovery. Additionally, Epicor's cloud versions update more frequently than NetSuite's twice-yearly release cycle, which can change API behavior between discovery and migration execution. We pin API versions in our extraction scripts and validate endpoint compatibility before migration runs. On-premise customers with custom .NET extensions may have data stored outside the standard Epicor database, which requires additional extraction scope.
How the migration runs
Discovery and subsidiary-to-company design
We audit the NetSuite environment across service tier, subsidiary count and hierarchy, custom record types, custom fields, item types (inventory assembly depth, BOM levels), active work orders, and transaction volume by date range.
What this step covers
We pair this with an Epicor deployment assessment (cloud vs. on-premise, Kinetic vs. Prophet 21 vs. Epicor ERP, modules licensed). The discovery output is a written migration scope, a subsidiary-to-company map with intercompany treatment recommendation, a BOM migration scope decision (active-only vs. historical), and a custom field enumeration from the NetSuite SuiteQL endpoint. This phase typically runs two to four weeks.
Epicor schema preparation and UD field creation
We provision the Epicor migration target: configure COA segment structure, create Company records for each NetSuite subsidiary, define UD fields and tables for every discovered NetSuite custom field and custom record type, configure Part and PartPlant settings for inventory items, and set up the Epicor TaxConnect tax code registry.
What this step covers
Epicor UD field creation requires administrator access and, for on-premise deployments, may require a brief test cycle. Schema is validated in the Epicor environment before any record migration begins. This phase runs in parallel with NetSuite extraction script development and typically takes one to three weeks.
NetSuite extraction in date-bounded batches under API ceiling
We extract NetSuite data using the SuiteQL endpoint in date-bounded batches of up to 1,000 records per request, monitoring API concurrency headers and implementing exponential backoff to stay within the account's tier ceiling (15 concurrent for default, up to 55 with SuiteCloud Plus licenses).
What this step covers
We monitor the running six-month transaction-line average to avoid triggering a tier upgrade during extraction. Master data (Accounts, Customers, Vendors, Items) extracts first, followed by BOM and routing records, followed by transactional history in dependency order. Each batch emits a row-count reconciliation report.
BOM and work order sequencing for manufacturing environments
For organizations with NetSuite inventory assemblies, multi-level BOMs, and active work orders, we sequence BOM extraction and transformation as a dedicated phase.
What this step covers
NetSuite assembly items are decomposed into Epicor Engineering BOM records (EBOM and ECO), with sub-assembly relationships mapped to Epicor's Part-BOM linkage. Work orders map to Epicor Job records with JobMtl and JobOper entries derived from the NetSuite work order line data. Routing steps map to JobOper with work center lookups validated against the Epicor Resource Group configuration. We recommend migrating only open and recently completed (within 12 months) work orders to limit scope.
Production migration in dependency order with reconciliation gates
We run production migration in record-dependency order: Epicor Company configuration, Chart of Accounts, Customer and Vendor records, Employee records, Part and PartPlant (inventory), BOM and routing (manufacturing), open AR and AP balances, Sales Orders and Invoices, Purchase Orders and Bills, Journal Entries, Project and PSA records, Activity and engagement history (if applicable), Custom Record instances, and Custom Field values on standard records.
What this step covers
Each phase emits a row-count and balance reconciliation report before the next phase begins. Financial reconciliation validates that the Epicor trial balance matches the NetSuite source trial balance within agreed tolerances.
Cutover, validation, and automation rebuild handoff
We freeze NetSuite writes during cutover, run a final delta migration of any records modified during the migration window, then hand Epicor as the system of record.
What this step covers
We deliver a written inventory of every active NetSuite SuiteFlow workflow, saved search automation, and custom record workflow with its trigger, conditions, actions, and a recommended Epicor BPM equivalent. We do not rebuild NetSuite SuiteFlow or SuiteScript customizations as Epicor BPM workflows; that is a separate engagement scoped by an Epicor implementation partner. We support a one-week hypercare window for reconciliation issues raised by the customer's finance and operations team.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
NetSuite to Epicor ERP migrations price primarily on transaction volume, BOM and routing complexity, and custom field count. Epicor licensing and implementation fees sit outside the migration fee and vary by deployment model (cloud subscription vs. on-premise). Every quote is scoped with you; there is no self-serve pricing.
Get a quote for NetSuite to Epicor Prophet 21 →Why teams move from NetSuite to Epicor Prophet 21
- NetSuite's slow page load and transaction save times frustrate daily users. Reviewers on G2 and Reddit cite 30-60 second delays opening routine records, with follow-up actions equally sluggish. Epicor Kinetic is built for real-time manufacturing and distribution operations where sub-second response on the shop floor is operationally critical. Companies running high-volume transactional environments, shift-based operations, or multi-location warehouse teams move to Epicor specifically for responsiveness that NetSuite's shared-tenancy architecture cannot deliver consistently at scale.
- NetSuite is a generalist ERP built for broad cross-industry coverage. Epicor is purpose-built for manufacturing, distribution, and regulated industries, with native best practices for BOM, routing, job costing, and supply chain that NetSuite delivers through customization and add-ons. A distributor cited on Reddit evaluating NetSuite and Epicor Prophet 21 noted that Prophet 21 was more purpose-built for their industry, and several NetSuite-to-Epicor migration reviewers cite Epicor's functional depth in industry-specific workflows as the primary driver for switching.
- NetSuite's per-user licensing model with per-transaction-line tier ceilings, module lock-in, and renewal uplift pricing surprises organizations at contract renewal. NetSuite tiers cap monthly transaction lines (Standard: 200K, Premium: 2M, Enterprise: 10M) and trigger forced upgrades when ceilings are hit during a migration. Epicor's custom pricing model based on modules and company count gives organizations more predictable cost control without transaction-line billing events, and companies cite Epicor's 412% three-year ROI for distribution customers as evidence of better TCO at scale.
- NetSuite's SuiteBuilder and SuiteFlow customization model creates technical debt that accumulates over time. Administrators cite difficult upgrade paths when customizations conflict with NetSuite's twice-yearly releases, and support complexity grows with each customization layer. Epicor's BPM-driven workflow model and optional advanced modules owned and supported directly by Epicor reduce the burden of managing third-party add-ons and upgrade risk. Reddit reviewers switching from Epicor to NetSuite cite integration issues and support costs as pain points on the Epicor side; NetSuite-to-Epicor migrators are specifically those who have hit the customization ceiling in NetSuite.
- NetSuite's dated, non-intuitive interface increases onboarding time for new employees and creates a steep learning curve for administrators. G2 reviewers consistently cite NetSuite's UI as a friction point, particularly for organizations with high turnover or distributed teams that need rapid system adoption. Epicor Kinetic offers a modern cognitive ERP interface with role-based navigation and analytics designed for manufacturing and distribution workflows, which reduces the time to competency for shop-floor and warehouse staff.
Questions, answered
NetSuite to Epicor Prophet 21 migration questions
How long does a NetSuite to Epicor ERP migration take?
Most NetSuite-to-Epicor migrations land between six and ten weeks for organizations without manufacturing complexity (no multi-level BOMs, fewer than three NetSuite subsidiaries, under 200 users, and under 200,000 transaction records). Migrations with active work orders, multi-level BOMs, more than three NetSuite subsidiaries, or extensive custom record types move to fourteen to twenty-six weeks because of BOM sequencing, Epicor multi-company setup, and custom field schema creation. Data quality is the biggest variable; organizations that have maintained clean NetSuite data (no duplicate SKUs, consistent naming conventions, standardized units of measure) migrate significantly faster than those carrying years of accumulated data debt.
Do NetSuite SuiteFlow workflows and SuiteScript customizations migrate to Epicor BPM?
No. NetSuite SuiteFlow visual workflows and SuiteScript server-side customizations are architecturally different from Epicor Business Process Management (BPM) and have no direct equivalent. We do not migrate them as code. We deliver a written inventory of every active NetSuite SuiteFlow workflow and SuiteScript customization with its trigger, conditions, actions, and a recommended Epicor BPM equivalent (or Kinetic framework extension where applicable). The customer's Epicor implementation partner rebuilds these as part of the Epicor deployment. Custom NetSuite saved searches that serve as reporting shortcuts also do not migrate; we recommend Epicor Report Builder or SSRS as the replacement.
How do we handle NetSuite's subsidiary model in Epicor?
NetSuite's subsidiary model lets one database represent multiple legal entities with automatic intercompany eliminations. Epicor does not support this model; each NetSuite subsidiary must become a separate Epicor Company. We design the subsidiary-to-company map during discovery, and the customer chooses how to treat intercompany transactions: recreate them as internal sales orders and journals in Epicor, carry them forward as manual consolidation entries, or handle them post-migration in a separate consolidation tool. This is one of the most consequential design decisions in the migration and must be resolved before any data is mapped. We document the chosen treatment in the migration contract.
Do we lose historical transaction data moving from NetSuite to Epicor?
We migrate the full transactional history within the agreed scope: open AR and AP balances, current-year closed transactions, and optionally one to three years of historical transactions based on the customer's data retention decision. We do not recommend migrating the full multi-year transactional history from NetSuite unless the customer has a specific compliance or audit requirement; full historical loads increase migration cost, introduce data quality risk, and can degrade Epicor system performance. Historical data not migrated can be stored in a low-cost archive for compliance and retrieval purposes. The NetSuite trial balance and account reconciliation must match the Epicor trial balance after migration for the project to be considered complete.
Can Epicor handle NetSuite's lot/serial number tracking?
Yes, Epicor manages lot and serial numbers through the PartLot table, PartSerialNo records, and PartTran transaction entries. NetSuite lot/serial assignments at transaction time migrate to Epicor as PartLot records linked to the Part, with expiry dates and bin assignments preserved. Serial number traceability migrates as PartSerialNo records. Lot and serial movements (receipts, issues, transfers) migrate as Epicor PartTran entries that establish the on-hand trail. This migration runs after Part and PartPlant are configured in Epicor because PartLot references require a valid Part number to exist first.
What happens to NetSuite Custom Record types in Epicor?
NetSuite custom record types (custrecord_* script IDs) vary per account and must be discovered before mapping. Each custom record type migrates to an Epicor UD Table (user-defined table) with equivalent fields. The migration includes both the custom record type schema (field names, types, required flags) and all custom record instances (the actual data rows). Epicor UD Tables are accessed via Epicor's standard data access layer, and the UD fields are displayed in Epicor's Kinetic UI alongside standard fields. We recommend defining the Epicor UD Table structure before migration begins so that the migration can write directly to the target schema.
How does NetSuite's API concurrency ceiling affect our migration timeline?
NetSuite enforces a maximum of 15 concurrent API requests for default-tier accounts (up to 55 with SuiteCloud Plus licenses on Tier 5). We monitor concurrency headers and implement exponential backoff with a queue system during extraction. If we exceed concurrency, NetSuite returns 429 or 403 errors and the requests are retried. We chunk exports into date-bounded batches of up to 1,000 records per request. Large migrations (over 500,000 transaction lines) may be paced across several weeks to avoid exhausting the account's monthly transaction-line tier ceiling during extraction. We scope each migration within the account's tier ceiling and flag before committing to a timeline if a tier upgrade will be required to complete the migration.
Related migrations
Sources: official documentation
- Data Migration Tools (DMT) — Epicor
- Export and import a Multi-Level BOM — Epicor User Help Forum
- Importing History from Old ERP System — Epicor User Help Forum
- Importing History from Old ERP System (page 2) — Epicor User Help Forum
- Bulk upload attachments to ECM — Epicor User Help Forum
- Data Migration Tools (Extraction Tool + DMT) — Epicor
- Upgrades and Migrations — Epicor
Get a quote
Moving from NetSuite to Epicor Prophet 21?
Tell us roughly how many records and objects you have. We scope the mapping and the Epicor Prophet 21 setup with you, then send a quote.
Get a quote