Migrate from Embrace ERP to Infor CloudSuite Corporate

Embrace account codes, descriptions, and hierarchical structure are extracted from the relational COA table and mapped to the Infor Cloudsuite account master. We preserve the full account tree with parent-child hierarchy for financial reporting in Infor. This must be loaded before any transactional data (Customers, Vendors, or AP/AR) because account codes are referenced as foreign keys throughout Infor's financial tables. Infor's Database Schema Report is used to confirm column names and data types for each account field.

Embrace customer master records include billing addresses, contact details, and tax registration, all mapped to Infor's Customer form. The customer account code from Embrace becomes the Infor Customer Number as the primary key. Payment terms migrate as Code-to-Code mapping. We extract all active and historical customer accounts and include any customer-specific pricing or discount structures as additional fields.

Vendor master records in Embrace mirror the customer structure with supplier-specific fields including banking details for payment configuration. We extract the full vendor list and map vendor account codes to Infor's Vendor Number. Banking details (bank name, branch code, account number) migrate to Infor's vendor payment setup fields for electronic payment configuration post-migration.

Inventory items in Embrace include stock codes, costing methods, warehouse locations, and reorder parameters. We extract BOM hierarchies and variant structures where present and perform multi-level BOM traversal during migration scoping to map the complete as-designed, as-built structure. Infor's costing method settings are configured in the destination item master before bulk import. Items with kit or bundle relationships are resolved into Infor's product structure.

Embrace BOM hierarchies with multi-level parent-child relationships are extracted and resolved against Infor's BOM table structure. A single Embrace BOM may resolve to multiple Infor BOM lines across revision levels. We map the as-designed BOM to Infor's engineering BOM and the as-built BOM to Infor's manufacturing BOM, flagging any BOM lines with custom routing or work center assignments for manual configuration review before production orders are raised.

Outstanding vendor invoices and credit notes are extracted with full aging detail (current, 30-day, 60-day, 90-day buckets). We map each open AP item to Infor's AP register with the vendor account, invoice number, invoice date, due date, and amount. Partial payments and credit note applications are reconciled at migration cutover to ensure Infor's AP aging reflects the true outstanding position at go-live. Any unallocated credit memos are flagged for manual allocation review.

Outstanding customer invoices and credit notes are extracted with full aging detail and mapped to Infor's AR register. Each AR item carries the customer account, invoice number, invoice date, due date, and amount. We preserve any payment terms, discount terms, and credit hold status from Embrace. Partial receipts and credit note applications are reconciled at cutover, and any disputed or flagged invoices are noted for the customer's AR team to review post-migration.

Transaction history migrates for the fiscal years agreed during scoping. We extract posted journals and batch details from Embrace and map them to Infor's journal entry format. Any report-specific calculations or groupings embedded in Embrace's custom report definitions do not translate; these are flagged as manual rebuild items. We scope the required fiscal-year depth with the customer and include batch headers, journal line amounts, and account code references in the export. Opening balances for each migrated fiscal period are reconciled against Infor's trial balance after import.

Documents linked to transactions or master records in Embrace's document management layer are extracted via the available file export path. We produce a structured file inventory with record linkage metadata (document type, associated transaction number, date) so that the customer can reload documents into Infor IDM post-migration. Any documents that require manual extraction or are stored in formats not supported by the export path are flagged for manual retrieval during the cutover window.

Embrace user-defined fields on master and transaction records vary between installations. We discover the complete custom-field schema during migration scoping using the Embrace database metadata, map each field to an equivalent Infor property or custom field, and flag any fields with unsupported data types (such as bespoke picklist values not documented in the base schema) for manual review before final import. The full custom-field inventory is included in the written migration scope delivered before any data moves.