Migrate from Adm Cloud to Dolibarr ERP

Adm Cloud Customer records map to Dolibarr Third Party with typentcode=TE_CUSTOMER. We preserve billing address, credit limit (encoded as concordance in llx_societe.cond_reglement), and payment terms (cond_reglement_id). The customer-supplier split in Adm Cloud produces separate Third Party records per entity if both roles exist. DoliCloud database access or CSV export from Adm Cloud provides the source record set.

Adm Cloud Vendor records map to Dolibarr Third Party with typentcode=TE_SUPPLIER. Payment terms and bank details migrate to llx_societe_rib. Any vendor marked inactive in Adm Cloud is flagged for exclusion unless the customer requests full historical preservation.

Adm Cloud Item master records map to Dolibarr llx_product. Adm Cloud variant structures (size, color, material from Packs vs Enterprise custom pricing tiers) normalize to a flat SKU model with Dolibarr variants handled via the product sub-product mechanism if the variant module is active. Product type (product vs service) maps from Adm Cloud item type classification. Price levels and cost layers map to llx_product_price entries created during import.

Adm Cloud account tree (account code, name, type, parent hierarchy) maps to Dolibarr llx_accounting_account. We preserve the full numeric account code and label. Tax codes attached to accounts in Adm Cloud (SAT/CFDI codes for Mexico) require explicit mapping to Dolibarr's tax system via llx_c_tax_range or a third-party SAT module if the customer requires CFDI-compliant invoicing post-migration.

Outstanding Adm Cloud AR invoices (customer invoices with open status) map to llx_facture with faclient=1 and fk_statut representing the invoice status. AP invoices map to llx_facture_fourn. Currency, exchange rate, and aging data transfer to the corresponding Dolibarr fields. Payment terms (cond_reglement_id) resolve from the Third Party mapping. Credit memos map as negative invoice amounts with type=3 (Amortissement). Chunks by date range to avoid import timeouts.

Historical Adm Cloud journals are high-volume, date-sensitive records. We sequence journal entry import after the chart of accounts is confirmed in Dolibarr. Entries split by fiscal period to avoid batch timeouts. Adm Cloud recurring journal templates do not migrate as automation; they are documented as a manual reconfiguration item in Dolibarr's Cron/scheduled task system. MXN/USD/COP exchange rates on each journal line require explicit mapping to Dolibarr's multicurrency accounting fields.

Adm Cloud User records (including role, department, and module permissions) map to llx_user. Role names differ significantly between Adm Cloud Packs and Enterprise; we map to the nearest Dolibarr equivalent (Admin, Restricted to third party, or read-only) and flag any Adm Cloud custom permission sets that have no Dolibarr counterpart for admin review. Login credentials do not transfer; new Dolibarr passwords are provisioned post-migration.

Adm Cloud custom fields added to standard objects require discovery during pre-migration scoping. We create matching Dolibarr extrafields on the equivalent llx_extrafields tables before record import begins. Adm Cloud Enterprise custom objects without a standard Dolibarr equivalent are stored as JSON in a dedicated Dolibarr extrafield column or mapped to a custom Dolibarr module if the customer has PHP development capacity.

Adm Cloud LATAM tax codes (SAT codes for Mexico, CFDI invoicing regimes) require explicit mapping to Dolibarr's tax configuration system. The full Adm Cloud tax code table is extracted during discovery and matched to llx_c_tva rate entries. Any SAT/CFDI-specific codes without a native Dolibarr equivalent require a third-party Dolistore module or custom configuration; this is flagged as an explicit sign-off item before import.

Adm Cloud Asset master records (acquisition cost, useful life, depreciation method) map to Dolibarr's Asset module if active. Depreciation methods (linear, declining) map to the nearest Dolibarr equivalent. Residual value discrepancies are flagged in the pre-migration report. Fixed asset migration requires the Asset module to be enabled in Dolibarr before import.

Adm Cloud bank account records and current balances transfer to llx_bank and llx_bank_account. Reconciliation history maps to Dolibarr's bank reconciliation feature. If Adm Cloud contains multiple currency bank accounts (MXN/USD/COP), each becomes a separate llx_bank_account entry with the currency code set appropriately.

Binary attachments (PDFs, images) stored in Adm Cloud's document module require separate file export and re-association by record ID in Dolibarr. Dolibarr stores uploaded files in the documents/ directory with a naming convention tied to the object type and ID. We preserve the link between document and parent object (Invoice, Third Party, Product) by matching filename patterns after export. PDF invoices from Adm Cloud are re-uploaded as Dolibarr documents attached to the equivalent invoice record.