Migrate from BusinessCloud to Infor CloudSuite Corporate

BusinessCloud Customer records map to Infor CloudSuite Customer (or Business Partner depending on edition). We use the SQL Server source database as the extraction mechanism, mapping Customer code, name, address, payment terms, and credit limit. Customer type (individual vs corporate) maps to Infor's Customer Category. Tax registration numbers map to Infor's Tax ID fields. Customer is loaded before any Sales Order or AR invoice records to satisfy the parent-record constraint.

BusinessCloud Supplier records map to Infor CloudSuite Supplier (or Business Partner with Supplier role). Supplier code, name, bank details, payment terms, and tax ID migrate directly. Supplier is loaded before any Purchase Order or AP invoice records. In multi-currency deployments, the supplier's default currency maps to Infor's Supplier Currency field.

BusinessCloud Item records (products, raw materials, finished goods) map to Infor CloudSuite Item Master. We map item code, description, unit of measure, item category, and cost from the source SQL database. The source database item type (stock item vs non-stock item vs service) determines the Infor Item Type field. If BusinessCloud stores BOM relationships in separate tables, we identify and flag these for BOM sequencing in the manufacturing module.

BusinessCloud GL account codes and dimension structure map to Infor CloudSuite's Chart of Accounts. We analyze the source SQL database for account code patterns (e.g., 4-4-2-2 format common in MENA deployments) and configure Infor's account segment structure accordingly. Cost center dimensions from BusinessCloud map to Infor Cost Center or Profit Center depending on the destination CloudSuite edition's financial module configuration.

Open Sales Orders at cutover date migrate to Infor CloudSuite Sales Order. We extract records with status indicating open or partial fulfillment from the source SQL database, map order number, customer reference, order date, requested delivery date, and line items (item, quantity ordered, quantity delivered, unit price). Line-item status (backorder, partial, complete) is preserved as Infor's line-status field. Closed orders are not migrated to the live system.

Open Purchase Orders at cutover date migrate to Infor CloudSuite Purchase Order. We extract open PO records from the source SQL database, mapping vendor reference, order date, promised delivery date, and line items (item, quantity ordered, quantity received, unit cost). Receipt history and invoice matching status are preserved in Infor's PO line status and receipt fields. Closed POs are not migrated.

Open AR invoices and credit memos at cutover date migrate to Infor CloudSuite AR Invoice. We map invoice number, customer, invoice date, due date, currency, line items, tax amounts, and payment status. Invoice PDF attachments from BusinessCloud's document storage are migrated as Infor Document Management (IDM) records linked to the invoice. Historical paid invoices are not migrated to the live system; they are flagged for the Data Lake archive path.

Open AP invoices and credit memos at cutover date migrate to Infor CloudSuite AP Invoice. We map supplier, invoice number, invoice date, due date, currency, line items, and tax amounts. Payment status and any holds are preserved. Historical paid AP records are not migrated to the live transactional database.

BusinessCloud BOM records map to Infor CloudSuite Bill of Materials under the manufacturing module. We extract the parent item, component items, quantities per assembly, BOM version, and effective date from the source SQL database. If BusinessCloud stores multiple BOM versions per item, all versions migrate with effective date ranges. BOM must load after Item Master to satisfy the component item reference.

BusinessCloud routing and work center definitions map to Infor CloudSuite Work Centers and Operations. We extract work center code, description, location, capacity data, and the operation sequence (step number, description, work center assigned, standard time). Routing must load after Work Center and before any job or work order records. If BusinessCloud stores multiple routing versions per item, all versions migrate with effective date ranges.

Current inventory on-hand balances at cutover date migrate to Infor CloudSuite Inventory. We extract item, warehouse, location, quantity on hand, and lot or serial number (if applicable) from the source SQL database. Inventory valuation (unit cost or average cost) is mapped to Infor's stock valuation fields. Inventory transactions and history are not migrated to the live system.

BusinessCloud warehouse and location definitions map to Infor CloudSuite Warehouse and Bin structures. We extract warehouse code, name, address, and the bin or location hierarchy from the source database. Multi-bin warehouses in BusinessCloud map to Infor's multi-location inventory structure with the appropriate bin-level tracking enabled.