Epicor Kinetic

NS90: Migrate:

Epicor Kinetic to NetSuite

Epicor Kinetic to NetSuite, with four years of history reconciled to the penny.

NS90: Migrate extracts from Epicor Kinetic cloud through its REST API, checks API completeness against your general ledger, and loads the history you choose into NetSuite, including parts, revisions and bills of materials, with period-by-period trial-balance proof.

Plan my Epicor Kinetic migration

See Support Data

Source

Epicor Kinetic (cloud / SaaS and on-prem)

EXTRACTION

Kinetic REST API v2 (OData) with API key

Manufacturing data

Parts, revisions, bills of materials and on-hand inventory, mapped to NetSuite items, assemblies and BOM revisions. Routings scoped per project

DATA DOMAINS

21 supported

DELIVERED

Kickoff to go-live in about 4 months

Depth

Option 4, full history

WHY NOW

2028.1

Epicor's announced final on-premises Kinetic feature release

Epicor has scheduled the last on-premises feature release for early 2028, with active support through 2029. On-prem Kinetic 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

21 Epicor Kinetic data domains, mapped field by field to NetSuite

Domains with solid dots have a proven field-level mapping from Epicor Kinetic to NetSuite. Hollow markers are manufacturing domains we scope per project, built on BOM migrations from other source systems.

Master data

Transaction

Balances & files

Master data

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

Customer

CustomerSvc

Contact

Customer · Vendor contacts

Item / part

Part (manufactured, purchased, sales kit) → assembly, inventory or kit item

Bill of materials

Method materials → BOM and components by location

Vendor

VendorSvc

Employee

EmpBasicSvc

Part revision

Approved revision → BOM revision with effective dates

Routing (scoped per project)

Operations, resource groups → routing and work centers

Transaction

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

Sales order

SalesOrderSvc

Invoice

ARInvoiceSvc

Customer payment

CashRecSvc

Item receipt

ReceiptSvc

Vendor credit

APInvoiceSvc

Journal entry

GLJournalEntrySvc

Customer shipment

CustShipSvc

Credit memo

ARInvoiceSvc

Purchase order

POSvc

Vendor bill

APInvoiceSvc

Vendor payment

PaymentEntrySvc

Inventory on hand

Quantities by warehouse, bin and lot → 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 Kinetic 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.

Chosen on 1 Epicor Kinetic project

What we’ve learned on Epicor Kinetic projects

The Epicor Kinetic details that make or break a migration

These come from real NS90 Epicor Kinetic projects. Each is already built into our standard Epicor Kinetic mapping, so you don’t discover it at UAT.

API first, with no database access needed

Kinetic cloud gives no SQL access. We extract through REST API v2, with cached tokens and full pagination, and land the data in NetSuite Analytics Warehouse for transformation.

Test API completeness against the GL

Some documents, such as standalone cash receipts, come from a different service than you'd expect. We compare extracted totals to the trial balance early, so gaps surface in week one, not at UAT.

Rebuild relationships the API leaves out

Child records may lack foreign keys, and some fields, like due dates, aren't exposed. We reconstruct them from related services and business rules.

Lines NetSuite won't accept as-is

Epicor lets expense lines post to AR, AP and bank accounts, and vendor credits carry part lines. We remap them to valid NetSuite structures and keep quantity and part in custom fields.

Periods that line up

Epicor fiscal period naming can shift a year against NetSuite posting periods. We align calendars before the first trial balance load.

Transactions without an entity

Journal-style entries with no customer or vendor are assigned to controlled opening-balance entities, so balances still tie.

Workflow-safe loads

Approval workflows are paused for load windows and restored afterwards, so historical POs and bills don't get stuck in approval queues.

Automated true-up

200,000+ trial balance lines were reconciled by period, and fewer than 400 needed an automated true-up entry.

Paging every call

Kinetic APIs return results in pages. Every extraction handles pagination fully, so no records are cut off.

Payments need special handling

Some payment services return incomplete identifiers. We key payments on stable fields and validate totals against the GL.

Credit memos need a returns account

Epicor credit memos are mapped to a returns account so they post correctly in NetSuite.

One method, several NetSuite records

An Epicor part revision holds materials, operations and subassemblies together. NetSuite splits these into items, BOMs, dated BOM revisions and routings, so we rebuild the structure rather than copy it.

Stock or phantom, decided per component

Epicor settings decide whether a component is issued from stock or built as a subassembly. We turn that into one NetSuite choice per component: stock, phantom, purchase order or work order.

Revisions become dated

Approved Epicor revisions load as NetSuite BOM revisions with start and end dates. We load current revisions by default, and older ones only where you still build to them.

Load order matters

Components load first, then assemblies, BOMs, revisions and routings. Multi-level structures are validated level by level.

Routings need NetSuite set up first

NetSuite routings require standard- or average-cost assemblies, work-in-process work orders, and cost templates and work centers. We set these up before loading operations, or keep routings in NSAW for reference.

Plant-specific methods

When a part is built differently by site, each plant's method becomes a NetSuite BOM assigned to that location.

Units and costs first

Epicor unit conversions are harmonized before items load. Opening inventory loads by location, bin and lot at a cost that reconciles to the Epicor inventory accounts, with the cost method agreed per item.

Some Epicor depth stays behind by design

Formal engineering change history, quality data and finite scheduling have no NetSuite target. We archive them in NSAW so they remain reportable.

How NS90: Migrate works

From Epicor Kinetic 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.