Migrate from Vault-ERP to Dolibarr ERP

Vault-ERP accounts map to Dolibarr's accounting chart. We extract the full account hierarchy via the NetSuite API and map it to Dolibarr's PCG-type classification. Multi-entity subsidiary structures in Vault-ERP may require separate Dolibarr instances or a third-party multi-company module; this is determined during scoping. Account numbers and names migrate directly; account type mapping (asset, liability, equity, revenue, expense) is configured in Dolibarr's accounting setup before import.

Vault-ERP Customer records map to Dolibarr Third-Party entities in Customer mode. We preserve contact details, addresses, payment terms, and credit limits. Vault-ERP custom classification fields on customers require per-instance mapping to Dolibarr extra fields. The customer is created before any related order or invoice records so that the foreign-key reference is satisfied at import time.

Vault-ERP Vendor records map to Dolibarr Third-Party entities in Supplier mode. Contact details, addresses, and payment terms migrate directly. Vault-ERP vendor-specific fields (tax ID, payment methods, default warehouses) map to corresponding Dolibarr supplier extra fields or native fields where names align.

Vault-ERP Item records map to Dolibarr Products (for inventory items) or Services (for non-inventory items). Item type (inventory vs non-inventory vs service), pricing, and BOM data transfer, but BOM structures may require manual reconfiguration in Dolibarr's BOM module post-migration if used. Vault-ERP custom item fields require per-instance mapping to Dolibarr extra fields.

Open payable records carry outstanding balances, payment terms, and linked vendor references. We map these to Dolibarr's outstanding supplier payment records, noting that currency and subsidiary metadata may require configuration in Dolibarr's banking module. Open AP is loaded after Third-Party records to satisfy the supplier reference.

Open receivable records carry outstanding balances, payment terms, and linked customer references. We map these to Dolibarr's outstanding customer payment records. Currency handling is preserved; multi-currency transactions require Dolibarr's multi-currency module to be active.

Vault-ERP Sales Orders map to Dolibarr Customer Orders. Order headers reference the Third-Party customer; order lines reference Products or Services. Vault-ERP's custom order form logic means order layouts vary; we extract the underlying transaction data and remap line items to Dolibarr order lines. Order status (draft, validated, shipped, invoiced) maps to Dolibarr's ORDER_STATUS values.

Vault-ERP Purchase Orders map to Dolibarr Supplier Orders. Line items reference Products, and the order references the Third-Party supplier. Vault-ERP PO custom fields require per-instance mapping to Dolibarr extra fields. Order status maps to Dolibarr's supplier order status values.

Vault-ERP Employee records map to Dolibarr Users with HR module activated (for system login) or Third-Party in Employee mode (for HR records without login). We migrate employee profiles, job titles, department assignments, hire dates, and salary information. Vault-ERP effective-dated HR changes (compensation changes, title transitions, department reassignments) migrate as a sequence of dated records rather than a single snapshot, preserving audit continuity. Custom employee fields require per-instance mapping.

Vault-ERP time tracking entries with billable and non-billable hours linked to projects or employees map to Dolibarr Project time entries. We extract raw hours and project associations and remap them to Dolibarr's timesheet structure. Vault-ERP's configurable time entry module means we apply per-instance field mapping during extraction.

Vault-ERP document references and metadata export alongside their associated records. We verify every migrated document by MD5 checksum comparison after transfer and flag any attachment where the source and destination hashes do not match. Dolibarr stores attachments in its documents directory with references linked to the parent entity (Third-Party, Product, Order, Project).

Vault-ERP tax codes reference jurisdiction-specific rates and rules. We extract the tax code definitions and their associated rates and map them to Dolibarr's tax dictionary configuration. Jurisdiction mapping is validated against Dolibarr's supported tax types (TVA, VAT equivalents, sales tax) during setup.