Epicor Prophet 21

NS90: Migrate:

Epicor Prophet 21 to NetSuite

Epicor Prophet 21 to NetSuite, with your pricing, rebates and branch inventory intact.

NS90: Migrate extracts Prophet 21 read-only from on-premises SQL Server or Epicor Cloud, rebuilds vendors and suppliers, ship-tos, pricing libraries, contracts and rebates in NetSuite, and loads the history you choose with period-by-period trial-balance proof.

Plan my Prophet 21 migration

See Support Data

Source

Epicor Prophet 21 (on-premises, self-hosted or Epicor Cloud)

EXTRACTION

Read-only SQL Server on-prem. Read-only database and Data Services (OData) API in Epicor Cloud

Manufacturing data

Items by location and bin, supplier cross-references, price libraries, job/contract pricing and vendor rebates, mapped to NetSuite items, pricing and custom records

DATA DOMAINS

25 supported, including pricing and rebates

DELIVERED

45-day proof of concept, 90-day go-live

Depth

Options 1 to 4, balances to full history

WHY NOW

May 2028

Epicor’s announced final on-premises Prophet 21 feature release

Epicor has scheduled the last on-premises Prophet 21 feature release, 2028.1, for May 2028, with Active Support through June 30, 2029 and Sustaining Support from July 1, 2029. After that, new Prophet 21 functionality ships only in Epicor Cloud, and self-hosted systems count as on-premises. On-prem Prophet 21 customers now choose between moving to Epicor Cloud and choosing a new platform. NS90 makes NetSuite a data-safe option.

Source: Epicor announcement, January 2026

// Supported Data Domains

25 Epicor Prophet 21 data domains, mapped to NetSuite

Each domain maps to a NetSuite target, with the Prophet 21 source table or record shown so your team can check coverage against its own data. Domains scoped per project are distribution structures we design with you.

Master data

Transaction

Balances & files

Master data

Customers, vendors, items and the records every transaction depends on.

Customer

customer · customer_class

Vendor & supplier

Vendor (pay-to) and supplier (buy-from) records → one NetSuite vendor

Item

inv_mast → inventory, non-inventory or kit item

Supplier cross-reference

supplier_x_item → vendor part numbers and costs

Pricing (scoped per project)

price_library · price_book · price_page → price levels, quantity and customer pricing

Vendor rebates (scoped per project)

Rebate programs and open accruals → custom records and GL accruals

Ship-to

ship_to → customer addresses or child customers

Contact

contact

Item by location

inv_loc → item location settings and reorder points

Unit of measure

unit_of_measure → NetSuite unit types

Job / contract pricing (scoped per project)

Contracts with dates, multipliers and max quantities

Transaction

Sales, purchasing, banking and inventory transactions, with the reference numbers your team knows.

Sales order

oe_hdr · oe_line

Invoice

invoice_hdr · invoice_line

Customer payment

cash_receipts_hdr

Item receipt

PO receipts → item receipts

Vendor credit

AP debit vouchers

Journal entry

GL journal detail

Inventory history (scoped per project)

inv_tran → NSAW, or NetSuite adjustments

Pick ticket / shipment

oe_pick_ticket → item fulfillment

Credit memo

invoice_hdr credit documents

Purchase order

po_hdr · po_line

Vendor bill

AP vouchers

Vendor payment

AP payments and checks

Inventory on hand

inv_loc · inv_bin with lots and serials → opening inventory tied to GL

Balances & files

Period balances for reconciliation, and the documents attached to your records.

Trial balance

GL by period

Choose your depth

Bring as much Epicor Prophet 21 history as your business needs

Trial balances are part of every option. Pick how much transaction detail lives in NetSuite and how much stays reportable in NetSuite Analytics Warehouse.

Option 1

Balances

Trial balances only

Monthly trial balances by account and segment loaded to NetSuite. Fastest path to a clean opening position.

Available

Option 2

Balances + drill-down

Trial balances in NetSuite, detail in NSAW

Trial balances in NetSuite with transaction-level drill-down to legacy detail in NetSuite Analytics Warehouse.

Available

Option 3

Open items + history

Masters and open transactions in NetSuite, history in NSAW

Customers, vendors, items and open AR/AP/orders in NetSuite. Every closed transaction stays reportable in NSAW.

Available

Option 4

Full history

Open and closed transactions in NetSuite

The years you choose of closed and open transactions in NetSuite, with automated trial-balance true-up by period.

Available

What to plan for on Prophet 21

The Prophet 21 details that make or break a migration

These are the Prophet 21 structures that most often complicate a move to NetSuite. Each is built into how we scope and map a Prophet 21 migration, so you don’t discover it at UAT.

SQL on-prem, OData in Epicor Cloud

On-premises and self-hosted Prophet 21 runs on Microsoft SQL Server, so we extract with a read-only SQL user. Epicor Cloud includes a read-only database, and the Data Services (OData) API covers the rest. We never need write access.

Tables, views and joins

Prophet 21 stores documents as header and detail tables, such as oe_hdr and oe_line, and ships many built-in reporting views. We pick tables or views per domain and validate every header-to-line join before load.

Vendor and supplier are two records

Prophet 21 separates the vendor you pay from the supplier you buy from, and one vendor can have several suppliers. NetSuite has one vendor record, so we consolidate them, keep supplier IDs as cross-references and map remit-to and order-from addresses.

Shared addresses, split cleanly

Prophet 21 can link customer, supplier and vendor records to shared addresses. We give each NetSuite entity its own address book entries, so a later edit changes only the record it should.

Bill-tos and ship-tos

Distributors often carry hundreds of ship-tos per account. Ship-tos load as NetSuite customer addresses or child customers, depending on how you bill, price and report.

Pricing in layers

Prophet 21 pages sit in books, books sit in libraries, and a book can belong to several libraries, with options such as lowest price across libraries. We resolve the effective price per customer and item, rebuild it with NetSuite pricing, and test it against real Prophet 21 quotes.

Contracts outrank libraries

Job and contract pricing can take priority over libraries, with expiry dates, maximum quantities and prices set as a multiplier of supplier list. Active contracts load with their dates, and formula prices stay formulas instead of frozen numbers.

Rebates are margin, not metadata

Prophet 21 tracks vendor rebates with vendor-level rebate and allowance accounts and methods such as a multiplier of supplier cost. We carry open accruals so they tie to the GL, keep program terms as custom records, and keep claim history reportable in NSAW.

Items live at the location

Stock, reorder points and bins sit on the item-location record, not the item. Items load once, then location settings, then opening inventory by location, bin and lot at a cost that reconciles to the Prophet 21 inventory accounts.

Deleted is not always gone

Prophet 21 can flag records as deleted without removing them. Every extract filters on the delete flag, and record counts are checked against Prophet 21 reports.

UDFs and DynaChange

User-defined fields live in separate tables and map to NetSuite custom fields. DynaChange business rules are logic, not data, so we inventory them and rebuild the ones you still need as NetSuite workflows or scripts.

Integrations to rebuild

EDI documents such as 850, 810 and 856, eCommerce, carrier and price-file feeds all point at Prophet 21. We list each one at assessment, so cutover does not strand a trading partner.

Years of duplicates

Acquisitions and long Prophet 21 tenure leave duplicate items and customers. We dedupe in NSAW before load and keep legacy Prophet 21 IDs as cross-references for search and reporting.

Some Prophet 21 depth stays behind by design

Counter-sale workflows, service and maintenance, and cylinder or asset tracking may have no direct NetSuite target. We scope them explicitly and keep their history reportable in NSAW.

How NS90: Migrate works

From Epicor Prophet 21 to a reconciled NetSuite in six steps

Every step runs on NS90 Migrate, MHI’s cloud-native migration engine on NSIP and NSAW. It handles extraction, landing, harmonization, parallel loading and trial-balance validation as repeatable jobs, so each rehearsal and the final delta pull run the same way.