Migrate from NetSuite to Infor CloudSuite Corporate

NetSuite Accounts (identified by account type codes: 0=Bank, 1=AR, 2=Inventory, 5=Fixed Assets, 10=AP, 21=Income, 23=COGS, 24=Expense) map to Infor CloudSuite GL Accounts. NetSuite's acctNumber and name fields map to AccountCode and Description. If NetSuite uses a multi-subsidiary chart with intercompany elimination accounts, each subsidiary's Eliminations account maps to an Infor Elimination Company account type within the consolidated structure. Account type codes must be reviewed against Infor's GL Account Type table during discovery.

NetSuite Customer records (entity type = Customer) map to Infor CloudSuite Customer Master. Address books, tax registration IDs, credit limits, payment terms, and currency assignments transfer to the Infor Customer record. Multi-address Customer records in NetSuite map to Infor Customer Address records with the primary address flagged. Customer-specific pricing tiers and discount schedules map to Infor price/discount groups. Custom fields (custentity_*) on Customer records require enumeration via SuiteQL discovery before field-level mapping.

NetSuite Vendor records (entity type = Vendor) map to Infor CloudSuite Supplier Master. Tax ID, W-9/W-8 status, payment terms, ACH/routing information, and default currency transfer to Infor Supplier. Vendor-specific landed cost assignments and 1099 settings map to Infor Supplier configuration fields. Multi-address Vendor records map to Infor Supplier Address records.

NetSuite Items map to Infor CloudSuite Item Master with item type differentiation: Inventory Assembly maps to Infor manufactured or stocked item; Non-Inventory maps to non-stocked item; Service maps to service item. BOM (Bill of Materials) relationships on Assembly items map to Infor BOM records with routing and work center assignments. Lot/serial tracking settings from NetSuite (tracking policy, shelf life, bin locations) map to Infor lot control configuration. Pricing matrices on Items transfer to Infor price lists with customer-specific overrides. Custom fields (custitem_*) require enumeration before field-level mapping.

NetSuite BOM records (on Assembly items) map to Infor CloudSuite BOM with component items, quantities per, and operation sequence. If NetSuite uses multiple BOM revisions (effective date-driven), each revision maps to an Infor BOM revision with effective date range. Work centers from NetSuite locations map to Infor work center codes. Routing operations from BOM (step sequence, work center, run time) map to Infor Routing records linked to the BOM.

NetSuite transactions carry line-level detail including tax lines, exchange rates, and fulfillment data. Historical transactions require a scope decision during scoping: (a) full history replay preserving posting dates and exchange rates, or (b) open-period carry-forward creating fresh journal entries at the destination. Closed transactions that are replayed require Infor's historical posting period to be open, which requires Infor administrator configuration before import. Open Sales Orders, Invoices, and Bills transfer as open items with aging preserved.

Outstanding receivables and payables migrate as open balances rather than as historical transactions. We extract open invoice amounts, due dates, aging buckets, payment terms, and currency from NetSuite. Each open AR record becomes an Infor open invoice attached to the Customer; each open AP record becomes an Infor open voucher attached to the Supplier. Payment terms and aging data transfer to the Infor AR/AP aging configuration. Partial payments are flagged and reconciled during the migration window.

This is the highest-risk object in the migration. NetSuite's subsidiary model allows multiple legal entities to exist in one database with intercompany eliminations. Infor CloudSuite requires each legal entity to map to a distinct Company (or Division within a Company) with its own GL, AP, and AR. We build the subsidiary-to-company map during discovery, validate that each NetSuite subsidiary maps to a distinct Infor company with the correct posting group assignments, and confirm intercompany accounts before any transaction data lands. Wrong subsidiary-to-company mapping causes posting rejections at import time.

NetSuite Custom Records (custrecord_* script IDs) have user-defined fields, lists, and sublists unique to each environment. Every NetSuite account has a different custom record schema that cannot be discovered via public documentation. We run a metadata discovery pass against the account's SuiteQL endpoint to enumerate all active custom record types and their fields before building the migration map. Infor CloudSuite stores custom attributes in Data Business Fabric or as custom tables with user-defined columns; we map NetSuite custom record fields to Infor custom table columns by data type (text, number, date, checkbox, list/select).

NetSuite attaches custom fields to nearly every standard object using custbody_*, custcol_*, custentity_*, and custitem_* prefixes. These are discovered per-entity via SuiteQL metadata queries during discovery. Custom fields on transaction lines (custcol_*) require special handling in REST/SOAP payloads because they must be attached to the line-level sublist rather than the parent record. We preserve the full custom field registry and map each to an Infor custom attribute or extended data field.

NetSuite Employee records (name, email, department, location, compensation history, PTO balances, benefits enrollment) map to Infor CloudSuite Employee Master. Effective-dated compensation rows require careful sequencing to preserve the compensation timeline. NetSuite's HR module is less mature than its financials module; organizations with deep HR complexity may use Infor Human Capital Management as a separate module within CloudSuite. We migrate Employee as a standard object and flag any HR module gaps for the customer to review.