Migrate from Adm Cloud to Microsoft Dynamics 365 Business Central

Adm Cloud Customers map to Dynamics 365 Customer (serving as Account) with a default Contact record. Adm Cloud's contact-to-account model is implicit in Adm Cloud but explicit in Dynamics, where Customer is a polymorphic lookup referencing either a person (Contact) or organization (Account). We extract contact fields from Adm Cloud Customer records and split them into Account (company-level data) and Contact (person-level data) during the transform phase. Billing address, credit limit, and payment terms move to the Account; email, phone, and role move to the Contact.

Adm Cloud Vendors map directly to Dynamics 365 Vendor. Vendor records with associated accounts and payment terms transfer 1:1. We flag any inactive vendors that should be excluded from the scope. Vendor addresses and payment terms map to the Vendor's Addresses and Payment Terms records in Dynamics.

Adm Cloud Items map to Dynamics 365 Item (with Type = Stock for inventory items, Type = Service for service items). Adm Cloud's custom pricing tiers and cost layers normalize to a flat SKU model during transform. Variants in Adm Cloud map as child rows or as item dimensions in Dynamics. ProductCode maps from the Adm Cloud item code field. Inventory posting groups in Dynamics are set based on the item type to align with the chart of accounts.

Adm Cloud's account tree structure (account codes, names, types, and parent-child hierarchy) maps directly to Dynamics 365 Chart of Accounts. We preserve account codes and names exactly. Account type mapping (Assets, Liabilities, Equity, Revenue, Expense) maps to the corresponding Dynamics account category. Tax codes attached to specific accounts require explicit mapping to Dynamics tax group codes, particularly for SAT and CFDI-related accounts.

Outstanding invoices and credit memos from Adm Cloud carry currency, exchange rate, and aging data that map to Dynamics 365 open vendor ledger entries (AP) and customer ledger entries (AR). We chunk by date range, map payment terms to Dynamics payment terms codes, and set the Due Date and Pmt. Discount Date fields accordingly. Currency exchange rates are resolved at migration time using the Adm Cloud rate table.

Historical journal entries from Adm Cloud migrate as General Journal Lines in Dynamics 365. Because journals are high-volume, date-sensitive records with dependencies on the Chart of Accounts, we sequence them after the account structure is validated in Dynamics. We split by fiscal period to avoid import timeouts. Recurring journal templates in Adm Cloud are noted separately for manual recreation in Dynamics Recurring Journals.

Adm Cloud Fixed Asset records migrate to Dynamics 365 Fixed Assets with acquisition cost, depreciation schedule, and useful life preserved. Depreciation methods (straight-line, declining balance, units of production) map to the nearest Dynamics depreciation book equivalent. Residual value and averaging conventions require explicit customer sign-off before import because differences in rounding can affect cumulative depreciation totals.

Adm Cloud User records (role, department, and module permissions) map to Dynamics 365 User with the closest-capability role match. Role names and permission levels differ between Adm Cloud Packs and Enterprise. We extract the permission matrix from Adm Cloud, map to Dynamics security roles, and flag any permissions with no direct Dynamics equivalent for the customer's admin to resolve.

Custom fields added to standard objects in Adm Cloud are discovered during pre-migration discovery and mapped individually to Dynamics extension fields (AL field extensions in Business Central or X++ extension fields in Finance & Operations). Fields without a direct Dynamics equivalent are stored as JSON blobs in a custom text field for post-migration review. Custom field count and complexity are a primary scope determinant.

Adm Cloud's LATAM tax code table (SAT codes for Mexico, CFDI configuration) maps to Dynamics 365 tax group codes, VAT business posting groups, and tax jurisdiction configurations. Tri-currency setups (MXN/USD/COP) require explicit customer sign-off on exchange rate tables and posting profiles before import. Any unmapped tax scenarios are flagged and held for manual resolution.

Binary attachments (PDFs, images) stored in Adm Cloud's document module require separate file export and re-association by record ID in Dynamics. We extract documents from Adm Cloud, organize them by parent object (Customer, Vendor, Item, or Journal), and upload them to the Dynamics SharePoint integration or Dataverse attachments linked to the corresponding record.

Adm Cloud Bank Account records and current balances transfer as-is to Dynamics 365 Bank Accounts. Account number, bank name, SWIFT/BIC codes, and currency map directly. Reconciliation history from Adm Cloud maps to the Dynamics Bank Account Reconciliation module. Opening balance on the bank account is set as a journal entry against the bank account number during migration.

Where the Adm Cloud e-commerce module is active, order headers and line items migrate to Microsoft Dynamics 365 Sales Orders and Customer Invoices. Order status (Pending, Confirmed, Shipped, Invoiced) maps to the corresponding Dynamics document status. Payment status and gateway references migrate as external reference fields and require explicit mapping to Dynamics payment reconciliation.