Migrate your Adm Cloud data

Core Receivables object. Adm Cloud standard contact-to-account model maps cleanly to most destination CRMs. We preserve billing address, credit limit, and payment terms as direct field mappings.

Core Payables object. Vendor records with associated accounts and payment terms transfer 1:1. We flag any inactive vendors that should be excluded from the scope.

Item master may use custom pricing tiers, cost layers, or variant structures unique to Adm Cloud Packs versus Enterprise. We normalize to a flat SKU model and map variants as child rows or custom properties in the destination.

Account structure is a standard tree in Adm Cloud. We preserve account codes, names, types, and parent-child hierarchy. Tax codes attached to accounts require explicit mapping to destination tax regimes.

Outstanding invoices and credit memos carry currency, exchange rate, and aging data. We chunk by date range and map payment terms to the destination's equivalent dunning or due-date fields.

Historical journals are high-volume, date-sensitive records. We sequence them after the chart of accounts and split by fiscal period to avoid import timeouts. Recurring journal templates require separate template-to-automation mapping.

Binary attachments (PDFs, images) stored in Adm Cloud's document module require separate file export and re-association by record ID. We preserve the link between document and its parent object (Invoice, Purchase Order, etc.) via a lookup mapping table.

User records include role, department, and module permissions. Role names and permission levels differ between Adm Cloud Packs and Enterprise. We map to destination roles by closest-capability matching.

Custom fields added to standard objects in Adm Cloud are discovered during pre-migration discovery and mapped individually to equivalent custom fields in the destination, or stored as JSON blobs if no equivalent exists.

Tax configuration is region-specific and tied to the LATAM edition. We extract the full tax code table and map each to the destination's tax agency codes, flagging any unmapped tax scenarios for customer review.

Asset master with depreciation schedules, acquisition cost, and useful life. Depreciation methods vary; we map to the nearest equivalent method and flag residual value discrepancies.

Where the e-commerce module is active, order headers and line items map to the destination's sales order or opportunity objects. Payment status and gateway references require explicit mapping.

Adm Cloud's BI module stores saved report definitions tied to its own data warehouse schema. These do not export cleanly and are recreated post-migration in the destination BI tool.

Bank account records and current balances transfer as-is. Reconciliation history maps to the destination's bank reconciliation module.