Migrate from ERP BOS to Infor CloudSuite Corporate

ERP BOS Customer records map directly to Infor CloudSuite Customer/Account objects. We preserve credit limits, billing address, currency assignment, and account balance. The customer_code field in BOS ERP becomes the destination customer account number; inactive accounts are flagged during scoping and excluded from the active migration count to avoid inflating the destination record count. Multi-currency customer records are mapped to Infor's multi-currency configuration with the BOS ERP currency code preserved.

ERP BOS Vendor records map to Infor CloudSuite Supplier objects. Payment terms, tax registration numbers, banking details, and purchasing contact information migrate to the destination supplier schema. The vendor_code from BOS ERP becomes the destination supplier number. Address records are mapped to Infor's address structure with multiple address type support (remit-to, ship-from, purchasing).

ERP BOS Items cover both inventory stock and non-stock products with custom fields permitted per item. We extract the full item schema during scoping, build a field-mapping table per item category (Finished Goods, Raw Materials, Trading Goods, Services), and map unit of measure, cost price, and selling price to Infor's equivalent item attributes. Multi-level BOMs are extracted as a separate dataset for BOM-specific mapping in the next object.

ERP BOS supports multi-level Bills of Materials with routing steps and custom fields per item. Infor CloudSuite represents BOMs as either assembly structures or recipe structures depending on the industry edition (Industrial uses assemblies; Food & Beverage uses recipes). We flatten multi-level BOMs into the destination structure, mapping each BOM level to the corresponding Infor assembly or recipe level, and preserve the original routing steps as work center assignments. Custom item fields used in BOM context are mapped to Infor's extended attribute framework.

ERP BOS maintains a hierarchical Chart of Accounts with account codes, descriptions, and classification (Asset, Liability, Income, Expense). We export the full COA as a structured record set and map account codes and classifications to Infor's GL account structure. Account types and classifications map directly. Intercompany income and expense accounts require special handling in the entity cross-reference step.

ERP BOS multi-entity capability means transactions between branches are tracked internally using entity IDs. We extract per-entity ledgers and assign destination company/entity codes from the entity cross-reference table built during schema design. Inter-company journal entries and elimination account pairs are mapped to Infor's elimination company or intercompany processing configuration. Elimination account treatment requires customer-side finance review before go-live to prevent consolidated reporting errors.

Outstanding payables and receivables migrate with open/closed status, due dates, amounts, and invoice references. We extract both sub-ledger balances and COA control account balances from ERP BOS and flag discrepancies before migration begins. Customers must reconcile these discrepancies in ERP BOS before we transfer open items; the destination system will carry forward imbalances that affect aged trial balances and credit limit calculations if the sub-ledger is not reconciled first.

ERP BOS Service Manager handles customer enquiry tracking and opportunity management. We migrate open service records and associate them with the migrated Customer record in Infor using a customer number lookup. Closed service records migrate as historical records with the original creation and closure timestamps preserved. Service status mapping is configured to align with Infor's service request lifecycle stages.

Tax codes and rates maintained in ERP BOS's accounting setup are extracted and mapped to Infor's jurisdiction-based tax configuration. Tax codes are mapped by tax type (VAT, GST, Sales Tax, Withholding) and rate, with the tax jurisdiction assignment based on the customer and vendor address records that were migrated earlier in the sequence.

Bank accounts and cash ledgers are part of the ERP BOS Chart of Accounts structure. We migrate bank account records separately from the COA import to establish bank account setup in Infor before cash ledger transactions are loaded. Account balances are reconciled against the last ERP BOS statement date. Bank transaction history migrates as journal entries posted to the cash account rather than as a separate bank transaction object.

ERP BOS stores binary document blobs (invoices, purchase orders, images, signed documents) linked to transactions in its document management module. We do not migrate binary document blobs through the standard data pipeline. We extract document metadata (document ID, filename, transaction reference, document type, creation date, created-by user) and produce a file-index CSV. The customer uses this index to execute a separate file transfer of binary attachments independently to avoid timeout issues with large attachment volumes.