Migrate from Agility ERP to Dolibarr ERP

Agility ERP Customer records map to Dolibarr Third Party contacts where the IsCustomer flag is enabled. Address, contact name, email, and payment terms transfer as standard Dolibarr fields. We validate email format during import and flag duplicate third-party names across the full import set to prevent double-creation. Customer-specific custom fields stored in Agility ERP's extension table require individual mapping to Dolibarr's ExtraFields system, which we configure before migration.

Agility ERP Vendor records map to Dolibarr Third Party contacts with the IsSupplier flag enabled. Remit-to addresses, tax IDs, and payment terms transfer 1:1. We check for duplicate vendor names within the import set to prevent Dolibarr from creating duplicate third-party records. Vendor-specific custom fields follow the same ExtraFields mapping process as customer fields.

Agility ERP open sales orders map to Dolibarr Customer Order records with status preserved. The Agility ERP status vocabulary (Open, Released, Backordered, and any custom statuses) requires an explicit lookup table we build during the discovery phase; each Agility ERP status value maps to a corresponding Dolibarr order status or custom workflow state. Line items transfer with quantity ordered, quantity delivered, quantity remaining, unit price, and product reference. The customer order date and order number are retained for audit trail continuity.

Agility ERP open purchase orders map to Dolibarr Supplier Order records. The same status vocabulary mapping logic applies as for sales orders. Line-level purchase order data transfers with supplier reference fields retained. If Agility ERP purchase orders reference a vendor record, we resolve the vendor lookup to the corresponding Dolibarr Third Party before inserting the supplier order.

Agility ERP inventory items map to Dolibarr Product records when the Stock module is activated. Cost layer data (average cost, FIFO cost, or lot cost) from Agility ERP transfers to Dolibarr's PMP (Weighted Average Price) field. We flag any items where the destination costing method differs from the source method so the customer can decide whether to adjust the cost layer during import or accept Dolibarr's default. Stock on hand and reorder point values transfer as Product Stock records linked to the appropriate warehouse.

Agility ERP account codes, descriptions, and classification (asset, liability, expense, revenue) map to Dolibarr accounting accounts. We audit every account code against Dolibarr's character length limits during scoping; any code exceeding the threshold is renumbered and recorded in a mapping table delivered alongside the chart of accounts. Account codes that change require a historical journal remap before historical entries are loaded, which we flag during discovery.

Historical Agility ERP journal entries transfer as Dolibarr accounting entries. We flag entries that contain embedded account IDs from the legacy chart of accounts and remap them to the new Dolibarr GL structure before loading. Only the current and prior fiscal year are migrated by default; additional years are migrated only if the customer specifies a longer retention scope during discovery, as historical volume directly affects migration timeline and price.

Fixed asset records including depreciation schedules are not accessible via Agility ERP's standard export or API layer. We flag any customer with a non-zero fixed asset balance during scoping and coordinate a direct database extract from Agility ERP support before the migration window opens. This custom extraction adds lead time and may require a separate professional services engagement with Agility ERP. Once extracted, we map asset records, accumulated depreciation, and current book value to Dolibarr's Asset module, which must be activated before import.

Agility ERP stores custom fields in a non-standard extension table that requires field-by-field review during scoping. Each custom field is mapped to a corresponding Dolibarr ExtraFields entry on the appropriate object (ThirdParty, Product, Order, etc.). Field type translation is required: Agility ERP field types map to Dolibarr types (varchar to varchar, integer to integer, date to date). Custom field values transfer as part of the parent object import, not as a separate migration phase.

Agility ERP shipment and delivery records map to Dolibarr Shipment records when the Shipping module is activated. Shipment date, carrier, tracking number, and linked sales order reference transfer directly. We resolve the parent customer order reference to the newly created Dolibarr Customer Order during import so the shipment is linked to the correct order.

Agility ERP project records map to Dolibarr Project records when the Project module is activated. Project name, description, status, start and end dates, and assigned contact references transfer. If the Dolibarr Project module is not activated during scoping, we flag this as a module activation dependency before migration begins.

Agility ERP user accounts map to Dolibarr User records for admin and staff users (not third-party contacts). We match by email address and map the active/inactive status. User permissions do not migrate directly because Dolibarr's permission model is tied to module activation and Dolibarr's own permission groups; we deliver a permission matrix recommendation based on the user's Agility ERP role so the customer's admin can configure access in Dolibarr.