How long does an Infor LX to Epicor ERP migration take?

Most migrations land between six and ten weeks for environments with up to 50,000 parts, 20,000 open order history records, and a single-site configuration. Migrations with multi-site Infor LX setups, BOM structures exceeding 20 levels, more than 5,000 open work orders, or IDM document libraries over 10,000 items move to twelve to twenty weeks because of the additional extraction passes, BOM transformation, document chunk sequencing, and cross-reference table maintenance required. Epicor ERP configuration time (fiscal calendar, multi-currency, tax, UOMClass) runs in parallel with discovery and adds two to three weeks of upstream work before data extraction begins.

Do Infor ION integrations and custom macros migrate to Epicor?

No. Infor ION is a middleware layer specific to Infor OS and does not have a direct Epicor equivalent. We do not migrate ION configurations, BOD mappings, or ION Desk workflows as these are tightly coupled to Infor's data model and event architecture. We document the ION integrations in a written inventory that lists each integration's source and destination, its trigger, and the recommended Epicor API or Data Connection replacement. Similarly, Infor LX macros, form customisations, and user exits do not migrate. We deliver a written inventory of these customisations for the customer's Epicor admin or implementation partner to address.

What does an Infor LX to Epicor ERP migration typically cost?

Migrations under 50,000 items, 20,000 order history records, and single-site configuration land between $18,000 and $28,000 and complete in six to ten weeks. Migrations with multi-site configurations, complex BOM structures, large work order histories, or extensive IDM document libraries move to $35,000-$65,000 and twelve to twenty weeks. Epicor ERP subscription costs ($125 per user per month for Epicor Kinetic; higher for Enterprise editions) and IBM i infrastructure decommission savings affect the total cost of ownership calculation but sit outside the migration fee.

Can we migrate historical work order and transaction data?

We migrate current on-hand inventory balances as Epicor PartBin entries and recent transaction history for the prior twelve months. Full multi-year transaction history is typically archived rather than loaded into Epicor because it is voluminous and rarely referenced operationally. We extract work order headers, component allocations, and scheduled dates for open and recently closed work orders for manufacturing continuity. Older closed work orders migrate as historical records for reporting continuity if the customer requires it, but this is scoped separately. BOM revision history is not fully migratable and requires Epicor's revision control to be rebuilt from source documentation.

How do you handle the Infor LX maintenance-mode export requirement?

We schedule database exports during a planned maintenance window agreed upon with the customer's IT team. During this window, all Infor LX user sessions are suspended, the production environment enters maintenance mode, and we extract the target tables in a sequenced pass to minimise downtime. For environments requiring continuous operations, we negotiate a phased extraction approach with a cutover delta sync step. IDM document exports are handled separately with sequential 5,000-item chunks and cross-reference tracking. The customer is responsible for communicating the maintenance window to their user base.

What happens to Infor LX custom fields in CMS470 after migration?

Infor LX custom fields defined in CMS470 on Items, Suppliers, Purchase Orders, and related objects map to Epicor ERP User-Defined Fields on the corresponding business objects. We create matching UD columns (Character01-30, Number01-20, Date01-10) on the target Epicor tables during migration and migrate the field values. The customer configures field labels, help text, and any validation rules in Epicor post-import. Custom fields on other objects (Customers, Sales Orders) are handled on a case-by-case basis depending on Epicor edition and table availability.

Do you migrate Infor LX workflows, approval chains, and printing scripts?

No. Infor LX workflows, approval chains, macro-based automation, and printing scripts are platform-specific and do not have a direct Epicor equivalent. We deliver a written inventory of every active workflow, approval chain, and report customisation requiring rebuild, with a description of the current logic and a recommended Epicor equivalent (Approval Workflow, Report Designer, BAQ). The customer's Epicor admin or implementation partner rebuilds these post-migration. This inventory is delivered as part of the migration handoff package on completion day.

What data quality issues are most common when migrating from Infor LX to Epicor ERP?

The most common issues are inconsistent item codes (duplicate or inactive items with the same code), mismatched GL account structures (Infor's segment configuration differs from Epicor's COA design), incomplete address data on vendor and customer masters, orphaned purchase order lines with missing distribution accounts, and BOM component references to inactive parts. We run a pre-migration data quality assessment during discovery and flag these issues with remediation recommendations before extraction begins. We do not alter source data without explicit customer approval; the remediation work is performed by the customer's Infor LX admin or a designated data steward.

Infor LX to Epicor Prophet 21 Migration — Field-Level Mapping & Rollback

Object mapping

How Infor LX objects map to Epicor Prophet 21

Each row shows how a Infor LX object lands in Epicor Prophet 21, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Infor LX

GL Accounts

maps to

Epicor Prophet 21

Chart of Accounts

1:1

Mapping required

Infor LX GL Account codes and descriptions map to Epicor ERP Chart of Accounts entries with Account Type (Header, Detail, Statistical), Currency associations, and Segment structures. We extract account codes, descriptions, account groups, and fiscal year assignments directly from the IBM i database and map them to Epicor's COA segment structure. Multi-ledger configurations in Infor require mapping to Epicor's Ledger and Legal Entity hierarchy. Account balance carry-forward requires Epicor's GL Balance import with period-end dating.

Infor LX

Customers

maps to

Epicor Prophet 21

Customer Master

1:1

Fully supported

Infor LX Customer master records (credit limits, payment terms, address data, multi-currency AR settings) map to Epicor ERP Customer records. Customer-to-account assignments and open-receivable balances are preserved. We extract via direct database query and map Infor's Customer Number to Epicor's CustID with a cross-reference table for downstream transactional lookups. Multi-currency AR is configured in Epicor's AR Parameters with currency-specific Customer defaults.

Infor LX

Vendors

maps to

Epicor Prophet 21

Supplier Master

1:1

Fully supported

Infor LX Vendor master records (tax registration, Pay-to addresses, multi-currency AP settings) map to Epicor ERP Supplier records. We extract vendor codes and pay-to locations from the IBM i database and map to Epicor's SupplierID with a cross-reference table. Open-payable balances migrate with invoice date and period assignment. Tax registration IDs map to Epicor's Tax ID fields on the Supplier record.

Infor LX

Items

maps to

Epicor Prophet 21

Part Master

1:1

Fully supported

Infor LX Item master records (stocking parameters, unit-of-measure conversions, Phantom Item flags, CMS470 custom fields) map to Epicor ERP Part records. We extract the item code, description, type (Stock, Non-Stock, Service, Phantom), stocking UOM, and any user-defined alphanumeric or numeric custom fields. Unit-of-measure conversions map to Epicor's UOMClass and UOMConv tables. Phantom Items migrate as Part Type = Phantom and drive BOM explosion in Epicor's MRP.

Infor LX

Bill of Materials

maps to

Epicor Prophet 21

Job/Quote BOM

1:1

Fully supported

Infor LX BOM structures (multi-level, engineering, and production BOMs) map to Epicor Job BOM or Quote BOM depending on order context. We extract BOM headers, component lines, quantities, and scrap percentages from the IBM i database. BOM revision control in Infor (with effective date and替代 bom) maps to Epicor's Rev approval workflow. Multi-level BOM explosion is preserved with parent-component relationships intact. Operation steps from Infor Routing map to Epicor Job Operations with work centre assignments.

Infor LX

Purchase Orders

maps to

Epicor Prophet 21

PO Header and PO Lines

1:1

Mapping required

Infor LX PO headers and lines (approval workflows, distribution accounts, foreign-currency amounts, three-way match settings) map to Epicor ERP PO records. PO status (open, closed, cancelled) migrates with line-level quantity received and invoiced. We map Infor's PO number to Epicor's PONum with a cross-reference table. Three-way match logic in Infor does not replicate in Epicor automatically; it requires Epicor Purchasing configuration post-import. Distribution account assignments map to Epicor's PO line GL Account fields.

Infor LX

Sales Orders

maps to

Epicor Prophet 21

OrderHed and OrderDtl

1:1

Mapping required

Infor LX SO records (pricing structures, warehouse assignments, commitments against inventory, line-level quantities) map to Epicor ERP Sales Order records. We extract header-level terms, line-level quantities, and pricing but note that Infor-specific discounting rules, promotional pricing, and volume break schedules do not automatically transfer and require Epicor price list configuration post-import. Open SOs migrate with OrderHed.OrderNum and OrderDtl.OrderLine mapping; historical SOs migrate as closed records for reporting continuity.

Infor LX

Work Orders

maps to

Epicor Prophet 21

Job Entry

1:1

Mapping required

Infor LX Work Orders (production operations tied to BOMs and routing steps, scheduled dates, component allocations, demand-source pegging) map to Epicor ERP Job records. We preserve work order numbers, scheduled start and due dates, and component allocations. Operation-level dependencies and scheduling constraints are mapped to Epicor Job Operations with sequence and job operation detail, though Epicor's scheduling engine recalculates timing on first save. Multi-plant Infor LX configurations require Epicor Plant assignment during migration.

Infor LX

Inventory Transactions

maps to

Epicor Prophet 21

PartTran (Inventory Transactions)

1:1

Mapping required

Infor LX physical inventory adjustments and stock movements (transaction history against warehouse locations and items) map to Epicor PartTran records. We extract current on-hand balances as Epicor PartBin entries and migrate recent transaction history for the current and prior fiscal year. Full multi-year transaction history is voluminous and typically archived rather than loaded; we recommend migrating twelve months of transactional detail and archiving older periods. Warehouse locations in Infor map to Epicor Warehse and Bin records with a location cross-reference table.

Infor LX

Period Tables

maps to

Epicor Prophet 21

Fiscal Year and Period Configuration

1:1

Fully supported

Infor LX Period tables (user-defined financial reporting intervals with start and end dates, organised by year and calendar name) map to Epicor ERP Fiscal Year and Fiscal Period configuration. We export the period table structure and current year's open/closed status. Infor's period-based financial calendars map to Epicor's GL Calendar with Fiscal Year, Fiscal Period, and Adjustment Period definitions. Open/close status per period is set in Epicor GL Calendar maintenance post-import.

Infor LX

Custom Fields (CMS470)

maps to

Epicor Prophet 21

UD Fields on Part/Supplier/PO

lossy

Fully supported

Infor LX custom fields defined in CMS470 on Items, Suppliers, and Purchase Agreement headers and lines (alphanumeric, numeric, and date types) map to Epicor ERP User-Defined Fields on the corresponding business objects. We extract field definitions and values together and create matching Epicor UD columns (Character01-30, Number01-20, Date01-10) on the target tables during migration. The customer's admin configures field labels and help text post-import. CMS470 custom fields on other objects (Customers, SOs) are handled on a case-by-case basis depending on Epicor edition and table structure.

Infor LX

IDM Documents

maps to

Epicor Prophet 21

Document Management (DMS)

lossy

Fully supported

Infor Document Management exports (up to 5,000 documents per run; history and old versions excluded) map to Epicor ERP Document Management or an attached external DMS. We split large document libraries into sequential IDM export chunks, track the ID remapping table (source document ID to destination document ID), and re-link documents to their associated transactional records (POs, SOs, work orders, parts) after import. Non-ASCII characters in document metadata are handled during the XSLT transformation step. Custom metadata keys from Infor map to Epicor Document Type and UD fields where applicable.

Infor LX	Epicor Prophet 21	Compatibility
GL Accounts	Chart of Accounts1:1	Mapping required
Customers	Customer Master1:1	Fully supported
Vendors	Supplier Master1:1	Fully supported
Items	Part Master1:1	Fully supported
Bill of Materials	Job/Quote BOM1:1	Fully supported
Purchase Orders	PO Header and PO Lines1:1	Mapping required
Sales Orders	OrderHed and OrderDtl1:1	Mapping required
Work Orders	Job Entry1:1	Mapping required
Inventory Transactions	PartTran (Inventory Transactions)1:1	Mapping required
Period Tables	Fiscal Year and Period Configuration1:1	Fully supported
Custom Fields (CMS470)	UD Fields on Part/Supplier/POlossy	Fully supported
IDM Documents	Document Management (DMS)lossy	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Infor LX gotchas

High

Maintenance mode required for database exports

Medium

IDM document export caps at 5,000 items per run

Medium

ION API execution timeouts are strict

Low

Document IDs and properties are reassigned on import

Epicor Prophet 21 gotchas

High

Third-party bolt-on integrations complicate migration scope

High

Dirty data without standardized processes compounds migration risk

Medium

SDK customizations and BPMs may not survive platform upgrades

Medium

Report-based export only for non-technical users

Low

Per-user pricing model requires accurate user count before migration planning

Infor LX gotchas		Epicor Prophet 21 gotchas
Severity	Issue	Severity	Issue
High	Maintenance mode required for database exports	High	Third-party bolt-on integrations complicate migration scope
Medium	IDM document export caps at 5,000 items per run	High	Dirty data without standardized processes compounds migration risk
Medium	ION API execution timeouts are strict	Medium	SDK customizations and BPMs may not survive platform upgrades
Low	Document IDs and properties are reassigned on import	Medium	Report-based export only for non-technical users
		Low	Per-user pricing model requires accurate user count before migration planning

Pair-specific challenges

Maintenance-mode database export suspends all Infor LX user sessions

The primary data extraction path for Infor LX uses the built-in Database > Export Database Data tool, which requires the IBM i environment to be in maintenance mode during extraction. This suspends all user sessions and blocks production processing. We schedule database exports during a planned maintenance window, extract the target tables (GL accounts, customers, vendors, items, orders) in a sequenced pass to minimise downtime, and handle referential integrity across multiple export passes. If the customer requires continuous operations, we negotiate a phased extraction approach with a delta re-sync step before cutover.
IDM document export cap and ID reassignment require cross-reference work

The Infor Document Management Export/Import tool caps at 5,000 documents per exporter run when in use. History and old versions are excluded, so only the latest version of each document transfers. New document IDs are generated on the Epicor import side, and original IDs are not preserved. We split large document libraries into numbered IDM chunks, run sequential export sessions, and maintain a cross-reference table mapping source document IDs to destination document IDs. We re-link documents to their associated transactional records (POs, SOs, work orders, parts) after the import completes using the cross-reference table.
ION API 25-second timeout constrains any real-time integration extraction

Customer-built ION services on Infor LX enforce a 25-second timeout on REST API handlers. We do not use ION as the primary migration extraction path because large record sets (inventory, order history) exceed this window. Instead, we use direct database extraction for master-file objects. If the customer's migration scope requires extracting data via ION (for real-time or event-driven integration), we pre-chunk transaction sets, use ION storage handlers for bulk retrieval rather than synchronous REST calls, and handle partial-result recovery for any timed-out requests.
BOM and routing complexity does not fully auto-translate to Epicor job operations

Infor LX BOM structures and routing steps with operation-level dependencies, scheduling constraints, and demand-source pegging do not have a direct one-to-one Epicor equivalent. We extract BOM headers, component lines, quantities, and scrap percentages, and map them to Epicor Job BOM. Infor Routing operations map to Epicor Job Operations with work centre assignments, but Epicor's scheduling engine recalculates timing on first save, which may alter the planned start and end times from the source. Configuration of Epicor work centres, labour rates, and operation sequences is a post-import admin step.

Migration approach

Six steps for a successful Infor LX to Epicor Prophet 21 data migration

Discovery and Infor LX environment assessment

We audit the source Infor LX environment across IBM i version, installed modules (MMS, OFM, PM, etc.), active custom fields in CMS470, document library size, open order and work order counts, and ION integration footprint. We extract a sample of 100-200 records per master-file object to validate database accessibility and assess data quality. We identify any IDM export runs required for document objects and flag the maintenance window requirement for the database export. The discovery output is a written migration scope document and a data quality report with any records that require pre-migration cleansing.
Epicor ERP target environment provisioning

We provision the target Epicor ERP environment (cloud tenant or on-premise deployment per the customer's choice), configure the Chart of Accounts structure, set up Ledger and Legal Entity hierarchy, configure multi-currency and tax settings matching the source AP/AR configuration, and define the Part master UOMClass and Part Type settings. We create UD field columns on target tables matching the CMS470 custom field definitions. This step runs in parallel with discovery and typically takes two to three weeks to complete the initial configuration.
Schema mapping and BOM/routing transformation design

We design the field-level mapping for each master-file object (GL Account to COA entry, Customer to Customer, Vendor to Supplier, Item to Part, PO to PO, SO to Order, Work Order to Job, BOM to Job BOM, Routing to Job Operations). We design the BOM explosion strategy for multi-level Infor BOMs into Epicor Job BOM hierarchies, flag any Phantom Items, and map Infor work centres to Epicor Resource Groups. We build the transformation logic in our migration engine and validate it against a 500-record sample before full extraction begins.
Sandbox migration and reconciliation

We run a full migration into the Epicor test environment using production-like data volume extracted from the Infor LX production system during a scheduled maintenance window. The customer's finance and operations leads reconcile record counts, spot-check 30-50 records per object type against the Infor LX source, and validate BOM explosion results. Any mapping corrections are documented and applied to the migration engine before the production migration begins. Epicor workflow and report configuration is reviewed at this stage.
Production migration in dependency order

We execute production migration in record-dependency order: Chart of Accounts and Fiscal Calendar first, then Customer and Vendor masters, then Part master and BOM structures, then open Purchase Orders, then open Sales Orders, then Work Orders, then current on-hand inventory balances, then recent transaction history (prior twelve months), then IDM documents in sequenced chunks. Each phase emits a row-count reconciliation report before the next phase begins. IDM document re-linking runs after all transactional records are in place to satisfy parent-record lookups.
Cutover, validation, and integration handoff

We freeze Infor LX writes during the cutover window, run a final delta migration of any records modified during the migration window, validate Epicor record counts against Infor LX totals, and hand off to the customer's admin team. We deliver a written inventory of ION integrations, custom reports, and workflow configurations requiring rebuild in Epicor. We support a one-week hypercare window where we resolve any data quality issues raised by the customer's team. Post-migration admin configuration, workflow rebuild, and end-user training are outside standard migration scope and are handled as separate engagements.

Platform deep dives

Context on both ends of the pair

Infor LX

Source

Strengths

Deep manufacturing capabilities with strong MRP/MPS and shop-floor functionality, popular with large discrete and process manufacturers
Stability and longevity on the IBM i (AS/400) platform — Infor LX 8.4 still runs on this trusted, scalable hardware
Effective integration of planning, manufacturing, and distribution within a single ERP
Available in both Infor Cloud and on-premises deployment, allowing flexibility for customers with data residency or hardware preferences
Large enterprise segment focus — about 45% of PeerSpot researchers come from large enterprise, validating the platform for that scale

Weaknesses

Support is widely reported as lacking, with vendor attention focused on newer products over LX
APIs are underdeveloped relative to the IBM i foundation, complicating integration with modern cloud applications
User interface is dated and needs significant enhancement to match contemporary ERP UX expectations
Finance and administration features fall short for some country localizations (e.g., Italian accounting)
Customer base skews toward established enterprises rather than growing/cloud-first companies, limiting peer-community modernization patterns

Epicor Prophet 21

Destination

Strengths

Purpose-built for wholesale distribution with industry-specific replenishment, kitting, and counter-sale workflows out of the box.
Multi-warehouse management with bin locations, cross-docking, and real-time inventory visibility across all warehouse locations.
Automated replenishment engine with demand-based and min-max planning reduces stockouts and overstock carrying costs.
AI-infused reporting via Epicor Prism provides Gen AI-driven insights into ERP data without requiring a BI team.
Strong customer retention at 90% and a 50-year track record in the distribution vertical provides long-term vendor stability.

Weaknesses

High total cost of ownership — per-user pricing of $150-200/month plus $10K-$500K implementation creates significant budget commitment for small and mid-market distributors.
Customization via SDK requires technical expertise and introduces upgrade risk when custom code conflicts with new P21 releases.
Report generation performance is a known pain point — multiple users report system freezes during large or complex report exports.
Third-party bolt-on reliance for functionality that competitors include natively increases integration complexity and total solution cost.
Limited public API documentation — developers building custom integrations report difficulty finding P21 API authentication methods and endpoint specifications.

	Infor LX Source	Epicor Prophet 21 Destination
Strengths	Deep manufacturing capabilities with strong MRP/MPS and shop-floor functionality, popular with large discrete and process manufacturers Stability and longevity on the IBM i (AS/400) platform — Infor LX 8.4 still runs on this trusted, scalable hardware Effective integration of planning, manufacturing, and distribution within a single ERP Available in both Infor Cloud and on-premises deployment, allowing flexibility for customers with data residency or hardware preferences Large enterprise segment focus — about 45% of PeerSpot researchers come from large enterprise, validating the platform for that scale	Purpose-built for wholesale distribution with industry-specific replenishment, kitting, and counter-sale workflows out of the box. Multi-warehouse management with bin locations, cross-docking, and real-time inventory visibility across all warehouse locations. Automated replenishment engine with demand-based and min-max planning reduces stockouts and overstock carrying costs. AI-infused reporting via Epicor Prism provides Gen AI-driven insights into ERP data without requiring a BI team. Strong customer retention at 90% and a 50-year track record in the distribution vertical provides long-term vendor stability.
Weaknesses	Support is widely reported as lacking, with vendor attention focused on newer products over LX APIs are underdeveloped relative to the IBM i foundation, complicating integration with modern cloud applications User interface is dated and needs significant enhancement to match contemporary ERP UX expectations Finance and administration features fall short for some country localizations (e.g., Italian accounting) Customer base skews toward established enterprises rather than growing/cloud-first companies, limiting peer-community modernization patterns	High total cost of ownership — per-user pricing of $150-200/month plus $10K-$500K implementation creates significant budget commitment for small and mid-market distributors. Customization via SDK requires technical expertise and introduces upgrade risk when custom code conflicts with new P21 releases. Report generation performance is a known pain point — multiple users report system freezes during large or complex report exports. Third-party bolt-on reliance for functionality that competitors include natively increases integration complexity and total solution cost. Limited public API documentation — developers building custom integrations report difficulty finding P21 API authentication methods and endpoint specifications.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Infor LX to Epicor Prophet 21

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Infor LX

Epicor Prophet 21

How Infor LX objects map to Epicor Prophet 21

What specifically takes care here

Six steps for a successful Infor LX to Epicor Prophet 21 data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Infor LX to Epicor Prophet 21 migration cost

What are you migrating?

Frequently asked questions about Infor LX to Epicor Prophet 21 data migrations

Can't find your answer?

Related migrations to explore

Move from Infor LX.
Land in Epicor Prophet 21, intact.

Migrate from Infor LX to Epicor Prophet 21

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Infor LX

Epicor Prophet 21

How Infor LX objects map to Epicor Prophet 21

What specifically takes care here

Six steps for a successful Infor LX to Epicor Prophet 21 data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Infor LX to Epicor Prophet 21 migration cost

Frequently asked questions about Infor LX to Epicor Prophet 21 data migrations

Can't find your answer?

How long does an Infor LX to Epicor ERP migration take?

Do Infor ION integrations and custom macros migrate to Epicor?

What does an Infor LX to Epicor ERP migration typically cost?

Can we migrate historical work order and transaction data?

How do you handle the Infor LX maintenance-mode export requirement?

What happens to Infor LX custom fields in CMS470 after migration?

Do you migrate Infor LX workflows, approval chains, and printing scripts?

What data quality issues are most common when migrating from Infor LX to Epicor ERP?

Related migrations to explore

Move from Infor LX. Land in Epicor Prophet 21, intact.

Move from Infor LX.
Land in Epicor Prophet 21, intact.