Migrate from AI Works to Dolibarr ERP

AI Works User records split into Dolibarr's separate User (authentication) and Contact/ThirdParty (business record) objects. We extract email, name, and role from AI Works and create the User record first so that OwnerId lookups are satisfied during Contact import. Any AI Works user who also appears as a business contact (e.g., a supplier contact) is created as both a User and a ThirdParty with a link via the User rights table llx_user_grant.

AI Works Account records map to Dolibarr ThirdParty (llx_societe). The AI Works account name becomes thirdparty name, the domain becomes email and URL fields, and address data maps to Dolibarr's address fields (address, zip, town, country). Customer or supplier classification from AI Works sets Dolibarr's client and fournisseor flags. ThirdParty is imported before any related Contact or Invoice to satisfy foreign-key constraints in Dolibarr's import engine.

AI Works Contact records map to Dolibarr Contact (llx_socpeople). The foreign key fk_soc points to the parent ThirdParty llx_societe row ID, which we resolve after the ThirdParty import phase. Email, phone, job title, and address fields migrate directly. If AI Works stores multiple contacts per account with a primary flag, we set the primary_contact flag on the first imported contact per ThirdParty.

AI Works Invoice records map to Dolibarr Facture. The AI Works invoice status (Draft, Sent, Paid, Cancelled) maps to Dolibarr fk_statut values (0, 1, 2, 3). Invoice line items map to llx_facturedet with fk_facture as the parent reference resolved at migration time. Payment terms, due dates, and tax rates migrate as Facture header fields and llx_facturedet tax configuration. We verify that the Facture module is activated in Dolibarr before this phase runs.

AI Works Purchase Order records map to Dolibarr CommandeFournisseur (llx_commande_fournisseur). Supplier reference from AI Works resolves to the parent ThirdParty fk_soc. Order status maps to fk_statut, and line items import to llx_commande_fournisseurdet. The Purchases module must be active in Dolibarr before import; if it is not, Dolibarr silently skips the records. We validate module activation state before this phase begins.

AI Works Product records map to Dolibarr Product (llx_product). SKU, description, unit, and price data migrate to llx_product fields. For products with variants, we evaluate whether AI Works variant data maps to Dolibarr's multi-price feature or requires separate Product records per variant. Product type (service vs stock) sets Dolibarr's fk_product_type field. Pricebook entries from AI Works map to llx_product_price.

AI Works custom fields require pre-creation in Dolibarr's ExtraFields system before migration. We evaluate each AI Works custom field type against Dolibarr's supported types (varchar, int, text, date, datetime, select, checkbox) and create the corresponding llx_extrafields record before data import. Dolibarr's ExtraFields are tied to specific table names (e.g., llx_societe_extrafields for ThirdParty) and must be created in advance via the ExtraFields module or direct database insert.

AI Works approval chains attached to invoices and purchase orders have no direct Dolibarr equivalent as migrated records. We document every AI Works approval chain (trigger condition, approver role, escalation path) and deliver a written inventory with Dolibarr's Workflow module recommendations (llx_workflow) so the customer's admin can rebuild approval logic post-migration. The migration itself carries no approval configuration.

AI Works account balances and ledger entries require mapping to Dolibarr's Accounting module (Bookkeeping module activation required). We evaluate whether AI Works stores accrual-basis or cash-basis entries and configure Dolibarr's accounting period and chart of accounts before balance migration. Dolibarr's accounting module is not active by default and must be explicitly enabled; if it is absent, we migrate only the invoice record without accounting double-entry.

AI Works creation date, modification date, and any audit timestamps on every record type migrate to Dolibarr's date fields (date_creation, date_modification, tms). These fields are set during the INSERT statement and preserved to maintain the original audit trail in the migrated records. Timestamps on attachments migrate via Dolibarr's ECM (Electronic Content Management) table llx_ecm_files.

AI Works file attachments (invoices PDFs, order documents, contact photos) migrate to Dolibarr's document storage directory and the llx_ecm_files table. We preserve the original filename and Dolibarr's directory structure (by entity and year) so that documents appear in the correct context within Dolibarr's document browser. Large binary files are chunked and transferred via the source platform's file export API or FTP.

AI Works multi-currency invoice lines require evaluation against Dolibarr's multi-currency capability. Dolibarr's multi-currency module is a third-party or paid feature; if the source uses multiple currencies, we verify the module is active and migrate currency code, exchange rate, and base-currency amount. If Dolibarr lacks multi-currency support, we convert amounts to the base currency at the invoice date's exchange rate and document the conversion rate used.