Migrate from NetSuite to Acumatica

NetSuite Customer records map directly to Acumatica Customers. NetSuite's subsidiary and territory assignments translate to Acumatica Customer Class and Branch assignments. Primary contact details (name, email, phone) transfer directly; multi-address records are preserved as separate Customer Locations in Acumatica. Addressee and print-on-check information also transfer, and customer-specific pricing maps to Acumatica's customer price classes.

NetSuite Vendor records map to Acumatica Vendors. Tax ID fields and 1099 flags translate to Acumatica tax settings on the vendor record. Multi-address vendor records become separate Vendor Locations in Acumatica. 1099 flags map to Acumatica tax settings on the vendor record. Payment hold status and default payment account assignments also transfer to maintain vendor payment preferences in the target system.

NetSuite Employee records map to Acumatica Employees. E-mail address is the matching key for owner resolution. Inactive employees in NetSuite can be mapped as inactive in Acumatica or excluded based on your migration scope. Department and location assignments transfer as Employee Department and Branch references, preserving the organizational reporting structure across the migration.

NetSuite Inventory Part items map to Acumatica Stock Items. The item number, description, base price, and units of measure transfer directly. NetSuite's units types map to Acumatica's Unit of Measure setup on the Stock Item. Item class assignments translate to Acumatica Item Class, and any custom fields prefixed custitem become user-defined fields on the Stock Item DAC.

NetSuite Non-Inventory Part items map to Acumatica Non-Stock Items. These are used for services or materials not tracked in inventory. The item number and description transfer; pricing fields map where applicable. Non-stock items typically represent service items, expense items, or job materials that are expensed or invoiced without inventory tracking requirements.

NetSuite Kit items with component lists map to Acumatica Stock Items with an attached bill of materials (BOM). The kit header becomes the parent stock item, and each component is created as a BOM line. This requires BOM setup in Acumatica before the migration run.

NetSuite Chart of Accounts records map directly to Acumatica Accounts. Account number, name, type (Bank, Expense, Income, Asset, Liability), and inactive flag transfer. NetSuite's accounts are scoped to a single book; multi-book configurations require separate account mapping per book. Account currency settings and intercompany account flags also transfer to preserve the full financial structure.

NetSuite Customer Payments map to Acumatica Payments applied to AR Invoices. The payment amount, date, reference number, and applied invoice details transfer. Undeposited funds require mapping to an Acumatica Cash account. Payment method (check, credit card, EFT) maps to Acumatica Payment Method, and the deposit ticket reference transfers as a document reference on the payment record.

NetSuite Vendor Bills map to Acumatica AP Bills. Header fields (vendor, date, reference, amount) and line items (account, amount, description) transfer. Line-level tax codes are mapped to Acumatica tax zone configurations. 1099 flags and amounts also transfer to preserve vendor tax reporting requirements in the target system.

NetSuite Sales Orders map to Acumatica Sales Orders. Customer, date, line items, quantities, and prices transfer directly. Order status (Pending Fulfillment, Cancelled) maps to Acumatica's order status field. FulfillmentWarehouse assignments and shipment priority flags also transfer to preserve the full sales order fulfillment context in Acumatica.

NetSuite AR Invoices map to Acumatica AR Invoices. Line items, amounts, descriptions, and tax amounts transfer. NetSuite's billing schedule attachments are preserved as document attachments in Acumatica. Invoice-level discounts and payment terms also map to ensure the complete billing lifecycle transfers correctly to the target system.

NetSuite Custom Record Types map to Acumatica custom tables created via the Customization Project editor. Each custom field on the NetSuite record becomes a user-defined field (UDF) on the Acumatica custom table. Parent-child relationships between custom records may require junction tables in Acumatica.

NetSuite Saved Searches are definition exports only — the query logic does not execute in Acumatica. We export the Saved Search definition as a reference document. Acumatica Generic Inquiries must be rebuilt manually or with consultant assistance. This is disclosed upfront as a rebuild item.

NetSuite SuiteProjects Pro project records map to Acumatica Projects. Project ID, name, status, customer association, budget, and task hierarchy transfer. Time entries and resource assignments migrate as Project Tasks and labor allocations. Project-specific custom fields become UDFs on the Acumatica Project entity.