Infor to NetSuite Data Migration
Migrating from Infor to NetSuite? Settle automates the mapping between Infor's industry-specific data model and NetSuite's cloud ERP — preserving item masters, customer records, manufacturing data, and financial history across Infor LN, M3, or CloudSuite.
Working with enterprise teams on active migration programs
Days
to production-ready mappings
Roughly half
the cost of consulting-led delivery
Every row
validated before go-live
Enterprise migrations routinely run months behind schedule. Yours doesn't have to.
This guide is for VPs of IT, data architects, and migration leads at companies moving data from Infor to Oracle NetSuite — whether you're scoping, planning, or mid-program.
Infor LN stores data in session-based tables — tcibd001 (Items), tccom100 (Business Partners), tipcf001 (BOM Lines), tisfc001 (Production Orders) — using a multi-company, multi-site architecture. Infor M3 uses a different schema with tables like MITMAS (Item Master), OCUSMA (Customer), and MPDMAT (BOM). NetSuite uses a unified cloud object model. Settle identifies which Infor product line you're migrating from and maps the correct source schema to NetSuite automatically.
Based on the founding team's enterprise migration experience
Last updated July 2026
How Settle automates your Infor to Oracle NetSuite migration
Settle detects which Infor product line your database runs — LN, M3, CloudSuite Industrial, or CloudSuite Distribution — and applies the correct source schema mapping. No manual table-by-table identification needed.
Infor's Business Partner model (where one entity can be customer, vendor, or both) is automatically split into NetSuite's separate Customer and Vendor record types with cross-references preserved.
Manufacturing data — BOMs, routings, and production orders — is restructured from Infor's production planning model to NetSuite's manufacturing module format with proper component quantities and operation sequences.
Multi-company configurations are mapped to NetSuite OneWorld subsidiaries with intercompany relationships, transfer pricing rules, and elimination entries documented for the finance team.
Get your Infor to Oracle NetSuite mapping analysis — see results in under an hour
Migration timeline: manual vs. Settle
Traditional approach
Timeline
8–18 months
Estimated cost
$600K–$1.5M
Team size
5–12 consultants
Typically requires
×Manual field mapping in spreadsheets
×Custom ABAP/SQL extraction scripts
×3–5 mock migration cycles
×Dedicated source system consultants
×Manual reconciliation testing
With Settle
Enterprise benchmarksTimeline
Days
Estimated cost
A fraction of consulting cost
Team size
2–4 internal resources
Included
✓Schema profiling & analysis
✓AI-generated field mappings
✓Transformation SQL
✓Validation & readiness reports
✓Production-ready load files
Common challenges migrating from Infor to Oracle NetSuite
Infor product line identification and schema mapping
Infor's portfolio includes LN, M3, CloudSuite Industrial (SyteLine), CloudSuite Distribution (formerly Distribution SX.e), VISUAL, and others — each with a completely different database schema. The item master is tcibd001 in LN, MITMAS in M3, and item in SyteLine. Settle identifies which Infor product your database runs and applies the correct schema mapping to NetSuite.
Explore related migrations →Multi-company and multi-site financial consolidation
Infor LN and M3 support complex multi-company and multi-site configurations with intercompany trading, transfer pricing, and consolidated financial reporting. NetSuite handles this through OneWorld subsidiaries and intercompany automation. The entity structure mapping — Infor companies to NetSuite subsidiaries, Infor sites to NetSuite locations — affects every transactional record in the migration.
Explore related migrations →Manufacturing data restructuring
Infor LN stores BOMs in tipcf001 (BOM lines) with routing operations in tirou001. Infor M3 uses MPDMAT (BOM material) and MPDOPE (BOM operation). Both have multi-level BOM structures with revision tracking. NetSuite uses BOM records with component lines and routing steps. The restructuring from Infor's production planning model to NetSuite's manufacturing module requires careful component-level mapping.
Explore related migrations →Business partner model to NetSuite customer/vendor split
Infor LN uses a unified Business Partner model (tccom100) where a single entity can be a customer, vendor, or both — with roles assigned to the same business partner record. NetSuite separates customers and vendors into distinct record types. Settle splits Infor business partners into the correct NetSuite record types while preserving cross-references for entities that are both customer and vendor.
Explore related migrations →Chart of accounts and dimension translation
Infor LN uses ledger accounts with dimensions. Infor M3 uses accounting strings with division, accounting identity, and cost center. NetSuite uses accounts with classes, departments, and locations as segments. The dimensional model translation affects all financial data and must be validated before any journal entries migrate.
Explore related migrations →Infor to Oracle NetSuite field mapping — what data moves
12 data objects typically migrated
| Source Object | → | Target Object |
|---|---|---|
| tcibd001 / MITMAS (Item Master) | → | Item |
| tccom100 / OCUSMA (Business Partner / Customer) | → | Customer |
| tccom100 / CIDVEN (Business Partner / Vendor) | → | Vendor |
| tipcf001 / MPDMAT (BOM) | → | BOM / BOM Revision |
| tirou001 / MPDOPE (Routing) | → | Routing |
| tisfc001 / MWOHED (Production Order) | → | Work Order |
| tdsls400 / OOLINE (Sales Order) | → | Sales Order |
| tdpur400 / MPLINE (Purchase Order) | → | Purchase Order |
| Inventory (whwmd210 / MITBAL) | → | Inventory Adjustment |
| G/L Entries (tfgld100 / FSLEDG) | → | Journal Entry |
| AR (tdsls410 / ARS100) | → | Invoice / Customer Payment |
| AP (tdpur410 / APS100) | → | Vendor Bill / Vendor Payment |
Typical enterprise migrations include 500K–10M+ records across these objects. Settle handles profiling and mapping at enterprise scale.
The cost of manual Infor to Oracle NetSuite migration
Infor to NetSuite migrations are driven by companies seeking a modern cloud ERP after years on Infor LN (formerly Baan), Infor M3 (formerly Movex/Lawson M3), Infor CloudSuite Industrial (SyteLine), or Infor VISUAL. The migration decision is often triggered by end-of-life announcements, rising maintenance costs, or PE firms consolidating portfolio companies onto a single platform. Infor's product line fragmentation — each acquired product has a different database schema — makes these migrations especially complex.
The core technical challenge is that Infor doesn't have one data model — it has many. Infor LN uses Dutch-origin table naming (tcibd, tccom, tisfc) with session-based architecture. Infor M3 uses a different schema entirely (MITMAS, OOLINE, MPDMAT). Infor CloudSuite Industrial (SyteLine) uses yet another SQL Server schema. Each requires a different mapping approach. On the NetSuite side, all of these must converge into a single object model — Items, Customers, Work Orders, BOM revisions.
Companies typically engage Infor-specialist consulting firms for 8–18 months. The data conversion effort — identifying which Infor product line is in use, mapping its specific schema to NetSuite, handling multi-company/multi-site data, and migrating financial history — is one of the most difficult workstreams because of Infor's schema fragmentation.
Consulting-led delivery for migrations in this class typically runs $600K–$1.5M. Settle prices it fixed and scoped — read the full cost breakdown.
Frequently asked questions
Related migration paths
Exceptions surface before the first load, not after the third.
Built by the team that ran Fortune 500 migrations by hand. Currently onboarding enterprise design partners on active migration programs.
Ready to migrate from Infor to Oracle NetSuite?
Tell us about your migration and we'll show you how Settle can help.
No commitment required. We'll review your migration scope and share a preliminary assessment within 48 hours.