Migrate from Adm Cloud to Epicor Prophet 21

Adm Cloud Customer records map to Epicor Customer or ARCustomer depending on the Epicor product line (Kinetic vs Eclipse). We preserve billing address, credit limit, payment terms, and the LATAM-specific CFDI usage field as a custom UD field in Epicor. Customer type (national, international, export) maps to Epicor's CustomerType field. We resolve the country/region code mapping from Adm Cloud's LATAM country list to Epicor's ISO-compliant country table before import.

Adm Cloud Vendor records map to Epicor Supplier or APSupplier. We preserve payment terms, bank account details for EFT, and any LATAM-specific RFC (Mexico) or tax ID fields as UD fields. Inactive vendors are flagged for exclusion unless the customer requests they be brought over for historical AP reference. Vendor types (domestic, import) map to Epicor's SupplierType field.

Adm Cloud Items map to Epicor Part (for inventory-stocked items) or Product (for non-stocked, order-only items). Adm Cloud's variant structure (size/color variants) maps to Epicor's Part UOM conversions and Part-specific attributes. Standard cost, last cost, and average cost layers transfer to Epicor's PartCost records. The item pricing tiers in Adm Cloud Packs map to Epicor's Price Schedules or CPQ configuration sets depending on pricing complexity.

Adm Cloud's account tree structure maps to Epicor's GL Account hierarchy with full parent-child relationship preservation. Account codes, names, types (asset, liability, equity, revenue, expense), and active/inactive status transfer directly. Tax codes attached to accounts in Adm Cloud require explicit mapping to Epicor's Tax Zone and Tax Category configuration; this is a high-scrutiny step for LATAM migrations because SAT tax codes must map to Epicor's tax agency codes.

Open AR invoices carry currency, exchange rate, aging data, and payment terms. We map Adm Cloud's invoice headers to Epicor ARInvoiceHead and line items to ARInvoiceDetail. Exchange rates are preserved from Adm Cloud's transaction-time rate; aging buckets are recalculated in Epicor using the destination company's fiscal calendar and due-date logic. CFDI UUID references from Adm Cloud invoices transfer as UD fields for Mexican statutory compliance.

Open AP invoices map to Epicor APInvoiceHead and APInvoiceDetail. Payment terms, vendor references, and invoice dates transfer. Foreign-currency AP invoices carry the original currency, amount, and exchange rate; Epicor recalculates the functional-currency equivalent using its configured rate logic. Vendor RFC tax IDs transfer as UD fields.

Historical journal entries are high-volume and date-sensitive. We sequence them after the chart of accounts is validated, then split by fiscal period to avoid import timeouts. Adm Cloud journal batches map to Epicor GLJrnHed (header) with individual journal lines as GLJrnDtl. Recurring journal templates in Adm Cloud are flagged for manual rebuild in Epicor's recurring journal module post-migration.

Adm Cloud fixed asset records map to Epicor FAAsset with depreciation schedules, acquisition cost, useful life, and residual value. Depreciation methods (straight-line, declining balance, units-of-production) map to Epicor's FA depreciation method codes. We flag any residual value discrepancies for customer sign-off before import because depreciation assumptions differ by jurisdiction.

Adm Cloud bank account records and current balances transfer to Epicor BankAcct. Reconciliation history maps to Epicor's bank reconciliation module if active. Multi-currency bank accounts carry both functional and foreign currency balances; we map currency codes from Adm Cloud to Epicor's ISO currency codes.

Adm Cloud user records include role, department, and module permissions. Role names and permission levels differ between Packs and Enterprise. We map Adm Cloud roles to Epicor security roles by closest-capability matching and flag any Enterprise-specific custom permissions for the customer's Epicor admin to configure post-migration. User provisioning (Active/Inactive status, email, manager hierarchy) transfers as-is with a reconciliation step to resolve any Adm Cloud users who do not have a corresponding Epicor identity.

Adm Cloud custom fields on standard objects migrate to Epicor User-Defined (UD) fields on the equivalent tables. Enterprise-tier custom objects without a standard Epicor equivalent are mapped to UD tables (UD01-UD19) with their own BAQ (Business Activity Query) definitions. UD field types (character, date, number, checkbox, dropdown) are mapped to Epicor's UD field type equivalents. All UD fields are pre-created in Epicor via the Cloud SDK or REST API before data migration begins.

Adm Cloud binary attachments (PDFs, images) stored in the document module export as files with their parent record reference. We re-associate each file to the corresponding Epicor record via ContentDocumentLink or Epicor's DMS module depending on the Epicor edition. The link between document and parent Invoice, Customer, or Part is preserved by matching on the source record ID stored as a UD field or file metadata.

Where the Adm Cloud e-commerce module is active, order headers map to Epicor OrderHed and line items to OrderDtl. Payment status and gateway references transfer as UD fields. If Adm Cloud e-commerce is a separate hosted storefront rather than a module, order data may live in a separate database or export; we scope this separately and map to Epicor accordingly. Payment reconciliation and gateway sync require post-migration integration rebuild.