Migrate from NetSuite to Dolibarr ERP

NetSuite Accounts map to Dolibarr accounting accounts using account type codes (0=Bank, 1=AR, 2=Inventory, 5=Fixed Assets, 10=AP, 21=Income, 23=COGS, 24=Expense). We preserve account numbers and names, and configure Dolibarr's accounting controller type (terme, tier, produit, TVA) per account. For multi-subsidiary NetSuite environments, each subsidiary's chart of accounts maps to a separate Dolibarr accounting entity or installation with distinct account prefix ranges to prevent cross-entity posting collisions.

NetSuite Customer records map to Dolibarr Third Parties with the contact type set to Customer. Address records (billaddr, shipaddr) migrate to Dolibarr address records with type tags. NetSuite's custentity_* custom fields on Customer records map to Dolibarr extrafields on the llx_societe table. We preserve customer-specific pricing tiers as Dolibarr price levels attached to the Third Party record.

NetSuite Vendor records map to Dolibarr Third Parties with the contact type set to Supplier. Tax registration fields (VAT number, employer identification) migrate to Dolibarr's third-party fiscal ID fields. NetSuite vendor-specific payment terms attached to the vendor record become Dolibarr payment term conditions on the Third Party.

NetSuite Items (inventory assembly, non-inventory, service, description-only types) map to Dolibarr Product records. Inventory assembly items with BOM relationships map to Dolibarr multi-level BOMs within the product sheet. NetSuite lot/serial tracking migrates to Dolibarr lot/serial numbers attached to stock movements. NetSuite pricing matrices (volume pricing, currency pricing) map to Dolibarr price lists attached to Product records.

Open NetSuite Sales Orders migrate to Dolibarr Customer Orders. The order status (Pending Fulfillment, Pending Billing, Closed) maps to Dolibarr status codes (Draft, Validated, Shipped, Billed, Canceled). Line items migrate with quantities, unit prices, VAT rates, and discount percentages. Fulfilled lines without invoicing map to Dolibarr shipping records linked to the order.

NetSuite Invoice records map to Dolibarr Customer Invoices. For open invoices, we migrate the full invoice detail including line items, tax lines, payment terms, and due dates. For paid historical invoices, we migrate summary records with payment status closed and original posting date. NetSuite invoice numbers become Dolibarr ref_customer for cross-reference. Custom fields on invoices (custbody_*) migrate to Dolibarr extrafields on the llx_facture table.

NetSuite Vendor Bills map to Dolibarr Supplier Invoices. Open bills migrate with full line detail, expense categories, and due dates. Historical paid bills migrate as closed records with payment reference. NetSuite's terms (Net 30, Net 60) map to Dolibarr payment term conditions attached to the supplier third party. Discount fields (custbody_discount_percent) migrate to Dolibarr discount lines on the supplier invoice.

NetSuite open AR (outstanding receivables) migrates as open Dolibarr Customer Invoices with status set to Unpaid. Aging buckets, due dates, and payment terms are preserved. NetSuite payment holds and credit holds on customer accounts migrate to Dolibarr bloquecredit and bloqueed fields on the Third Party record. We do not recreate closed AR as historical transactions; open AR is the carryforward scope.

NetSuite open AP (outstanding payables) migrates as open Dolibarr Supplier Invoices with status set to Unpaid. Due dates, aging buckets, and vendor payment terms are preserved. NetSuite vendor holds map to Dolibarr Third Party status flags. Open AP is carried forward as open balances rather than recreated as historical rows, matching how NetSuite structures the AP aging report.

NetSuite Journal Entries migrate to Dolibarr accounting entries with original posting dates and exchange rates preserved. Intercompany elimination entries (NetSuite subsidiary-to-subsidiary postings) are flagged for the customer's administrator to handle in Dolibarr because Dolibarr has no native intercompany elimination engine. Some organizations elect to carry forward open period balances only as fresh journal entries rather than replaying historical rows; we present both options during discovery and capture the choice in the migration contract before sequencing data.

NetSuite Projects (including PSA billing records, milestones, and resource allocations) map to Dolibarr Projects. Project status migrates (in progress, completed, on hold). Time entries attached to NetSuite Projects migrate to Dolibarr Project time tracking entries. Milestones migrate as Dolibarr Project task milestones. Project financials (billable hours, expenses) migrate to Dolibarr Project invoicing lines. Non-billable project costs and internal allocations are noted as requiring manual review post-migration.

NetSuite Employee records map to Dolibarr User records if the HR module is enabled, or to Dolibarr Third Parties with a note if HR is not in scope. Compensation history, PTO balances, and benefits enrollment (effective-dated rows) require careful sequencing because NetSuite stores them as separate sublist rows that Dolibarr HR flattens into a single employee record. We migrate current employment status, department, and job title; historical compensation rows are migrated as notes on the Employee unless the customer specifies carryforward only.

NetSuite Custom Records (custrecord_* script IDs) have no direct Dolibarr equivalent. We assess each custom record type during discovery: records with a 1:1 relationship to a standard object (e.g., custom compliance data attached to a customer) migrate as extrafields on the corresponding Dolibarr table (llx_societe). Records that function as independent objects with their own sublists and relationships require a separate Dolibarr module or external table that we document in the schema design phase.

NetSuite tax codes (nexus, rates, filing jurisdictions) map to Dolibarr's TVA (VAT) and local tax configuration. Nexus assignments require manual review because Dolibarr manages tax applicability at the third-party or product level rather than as a separate nexus registry. We preserve the full NetSuite tax code registry as a reference document for the customer's administrator to reconfigure in Dolibarr's tax management module.

NetSuite's subsidiary model has no native Dolibarr equivalent. Each NetSuite subsidiary must map to either a separate Dolibarr installation (for full legal entity isolation with independent databases) or a distinct Dolibarr accounting entity with separate account prefix ranges and dedicated chart of accounts. Intercompany transactions between subsidiaries require manual reconfiguration in Dolibarr because there is no automatic elimination engine. We build the subsidiary-to-company map during discovery, validate account prefix assignments, and document which subsidiaries will require separate installations versus shared-instance configuration.

NetSuite File Cabinet documents attached to records migrate as Dolibarr attachments linked to the corresponding record (Invoice, Order, Third Party, Product). File metadata (name, size, upload date) migrates; large file transfers are chunked and retried under rate limit constraints. Dolibarr's /documents/ directory structure replicates the NetSuite file cabinet hierarchy where accessible via REST.