Migrate from Adm Cloud to Odoo ERP

Adm Cloud Customer records map to Odoo Partner records with partner_type = 'contact'. The Adm Cloud billing address, credit limit, and payment terms map to Odoo's street/city fields, credit_limit on res.partner, and property_payment_term_id. We use the customer email or internal ID as the dedupe key during import. If Adm Cloud stores both a contact and an organization on the same Customer record, we split to a Contact child record attached to a Company Partner parent.

Adm Cloud Vendor records map to Odoo Partner records with partner_type = 'supplier'. The vendor account code, payment terms, and bank details transfer to Odoo's supplier fields. We flag any Vendors with an inactive status in Adm Cloud for exclusion from the import scope unless the customer requests they be migrated as inactive records in Odoo.

Adm Cloud Item master records map to Odoo Product records. We normalize Adm Cloud custom pricing tiers and cost layers into Odoo's product pricelist structure. Variants in Adm Cloud (color, size, dimension) map to Odoo Product Variants with attribute lines. SKU (hs_sku equivalent) maps to Odoo's default_code field. Products with serialized tracking in Adm Cloud map to Odoo's lot/serial number tracking via stock.lot.

Adm Cloud's account tree (account codes, names, types, parent-child hierarchy) maps directly to Odoo's account.account model. We preserve account codes as Odoo's code field and map Adm Cloud account types to Odoo's account.account type selections (asset, liability, equity, revenue, expense). Tax codes attached to accounts in Adm Cloud require explicit mapping to Odoo's account.tax records before the account import finalizes. Parent-child hierarchy is preserved via the parent_id foreign key.

LATAM tax codes from Adm Cloud (SAT codes for Mexico, CFDI invoicing codes) map to Odoo's account.tax records under the l10n_latam module localization. Each Adm Cloud tax code is assigned an Odoo tax_type, amount, and tax_group. Multi-component taxes (base + VAT + IEPS in Mexico) split into separate Odoo tax lines. We flag any Adm Cloud tax codes without an Odoo l10n_latam equivalent for customer sign-off before import.

Outstanding Adm Cloud AP and AR invoices map to Odoo account.move records with move_type = 'in_invoice' (AP) or 'out_invoice' (AR). Currency, exchange rate, due date, and aging data transfer to Odoo's currency_id, amount_total, invoice_date_due fields. Payment terms from Adm Cloud map to Odoo's invoice_payment_term_id. We chunk by date range (quarterly splits) to avoid import timeouts on large AP/AR tables. Open versus closed status determines whether the Odoo move is in draft or posted state.

Adm Cloud Journal Entries map to Odoo account.move records with move_type = 'entry'. We sequence journal entries after the chart of accounts so that all referenced account codes exist in Odoo before import. Entries are split by fiscal period (monthly batches) to manage batch size. Recurring journal templates in Adm Cloud are flagged separately for manual recreation in Odoo as recurring entries via Odoo's recurring entries feature.

Adm Cloud Fixed Asset records (acquisition cost, useful life, depreciation method, residual value) map to Odoo's account.asset model. We map Adm Cloud depreciation methods (straight-line, declining balance) to Odoo's asset depreciation profile. Depreciation schedules transfer as Odoo asset lines with scheduled dates and amounts. Any depreciation already posted in Adm Cloud is imported as journal entries first, then the remaining schedule is imported as pending depreciation lines.

Adm Cloud bank and cash account records map to Odoo account.journal records with type = 'bank' or 'cash'. Current balances transfer as opening balances on the Odoo journal. Reconciliation history maps to Odoo's account.move.line with matched_reconciliation_id populated. We flag any bank accounts with outstanding reconciliation items for manual review before the account is set to 'posted' state.

Adm Cloud User records (name, email, role, department, module permissions) map to Odoo res.users. Adm Cloud role names are mapped to Odoo access rights groups (base.group_user, base.group_system, or custom groups). Active/inactive status transfers to Odoo's active flag. We note that Odoo's permission model is application-level rather than module-level, so Adm Cloud's per-module permissions require translation to Odoo's application access groups during import.

Binary attachments (PDFs, images) stored in Adm Cloud's document module export via the platform's file export utility and are re-associated in Odoo via ir.attachment records linked to their parent model (account.move for invoices, res.partner for contacts) using the original record ID as a reference key. We preserve the original filename and MIME type. Documents without a resolvable parent record go to a catch-all Odoo document storage for manual assignment.

Custom fields added to standard Adm Cloud objects are discovered during pre-migration discovery and mapped individually to equivalent Odoo custom fields (created via Odoo Studio or programmatically). We apply the same field type mapping (text to char, number to float, date to date). Custom fields without a clean Odoo equivalent are stored as JSON in a dedicated Char field for customer admin review post-migration.