Migrate from Adm Cloud to Infor CloudSuite Corporate

Adm Cloud Customer records map to Infor Business Partner records with a party type of Customer. We preserve billing address, credit limit, payment terms, and the LATAM-specific fiscal ID (RFC in Mexico, RUC in Peru, CNPJ in Brazil) as the Infor Business Partner tax registration number. If Adm Cloud uses a separate contact model within Customer, we extract contacts to Infor Contact records linked to the Business Partner. Multi-currency pricing on the customer record maps to the Infor Business Partner's currency settings. Inactive customers are excluded from the default scope unless explicitly requested.

Adm Cloud Vendor records map to Infor Business Partner records with a party type of Supplier. Payment terms, bank details, and the vendor's tax registration number transfer as-is. We flag any vendors that share the same tax ID as an existing customer record (common in LATAM where the same legal entity can be both customer and supplier) and create a single Business Partner with dual party types rather than duplicate records.

Adm Cloud Item records map to Infor Item Master. We normalize variant structures ( Adm Cloud Pack variant schemas vs Enterprise custom variants) into a flat SKU model where variants appear as child rows with their own item codes. Cost layers from Adm Cloud map to Infor cost element structures, and pricing tiers map to Infor price lists. The Infor migration utility supports predefined item table mappings; we add custom mappings for any Adm Cloud-specific fields (e.g., HS codes for international trade, SAT product codes for Mexican tax compliance) that have no direct Infor counterpart and flag them for manual review before import.

Adm Cloud account tree (with codes, names, types, and parent-child hierarchy) maps directly to the Infor GL Account structure. We preserve account codes as the Infor account identifier and map Adm Cloud account types (Asset, Liability, Equity, Revenue, Expense) to Infor account classifications. Tax codes attached to specific accounts in Adm Cloud require explicit mapping to Infor tax codes during the LATAM tax configuration phase. The chart of accounts must be imported before any journal entries or AP/AR records because every transaction references an account code.

Outstanding AP and AR invoices from Adm Cloud map to Infor open item records. Currency code, exchange rate at invoice date, due date, and aging bucket data transfer directly. We chunk by date range (quarterly batches) to avoid import timeouts and flag any invoices in MXN/USD/COP tri-currency setups for explicit customer sign-off because exchange rate handling differs between platforms. Payment terms on the invoice header map to Infor due date rules. Credit memos and prepayment applications map as negative open items.

Historical journals are the highest-volume migration object and must be sequenced after the chart of accounts. We split by fiscal period (typically annual batches) and transform Adm Cloud line items into Infor GL journal entry format with debit/credit amounts, account code references, and source document references. Recurring journal templates in Adm Cloud do not transfer as automation (no workflow migration); we list them in the automation inventory for the customer to rebuild in Infor. The Infor Data Assessment Report flags any unbalanced journals before commit.

Adm Cloud user records with role, department, and module permissions map to Infor User records with role assignment. Role names differ between Adm Cloud Packs and Enterprise; we map by closest-capability matching during the discovery phase and document any gaps where an Adm Cloud permission has no direct Infor equivalent. We do not migrate Adm Cloud user passwords; Infor handles authentication via its own identity layer.

Adm Cloud asset master records (acquisition cost, useful life, depreciation method, residual value, location, asset tag) map to Infor Fixed Asset records. Depreciation methods differ between platforms; we map declining balance to Infor declining balance equivalents and flag any ADM-specific depreciation methods without a direct Infor counterpart. Accumulated depreciation to date transfers as an opening balance entry rather than a retroactive journal reconstruction.

Binary attachments stored in Adm Cloud's document module (PDFs, images, exported reports) are exported as files and re-associated in Infor Document Management (IDM) by matching the parent record ID. We create a file-to-record lookup table during discovery so that document re-linking happens programmatically rather than manually. Documents without a resolvable parent record are exported to a catch-all Infor IDM folder for manual classification.

Adm Cloud LATAM tax codes (SAT codes for Mexico, CFDI for invoicing compliance, regional VAT codes) require explicit mapping to Infor's tax regime configuration for the destination CloudSuite edition. This is a configuration step that runs in parallel with data migration, not a data import. We extract the full Adm Cloud tax code table and produce a written tax mapping matrix; the customer's Infor administrator or tax consultant applies the Infor tax regime configuration before AP/AR and invoice data is loaded because tax codes are validated at import time.

Custom fields on standard Adm Cloud objects are discovered during pre-migration and mapped to Infor extended properties. For Enterprise-tier Adm Cloud tenants, any custom objects without a standard Infor counterpart are documented in the custom object inventory. We do not create custom objects inside Infor; that is a schema design step performed by the customer's Infor consultant. We deliver a field-level mapping spreadsheet showing every Adm Cloud custom field, its data type, and the recommended Infor target (standard field, extended property, or JSON blob if no typed field exists).

Where the Adm Cloud e-commerce module is active, order headers and line items map to Infor Sales Order records. Payment status, gateway references, and fulfillment status map to Infor order lifecycle states. We flag any orders in a pending-payment state for customer resolution before import because Infor's order validation requires payment terms or a payment reference. Integration connections between the e-commerce platform and Adm Cloud do not migrate; the customer configures a new Infor integration post-migration.