Migrate from Sage 100cloud to Infor CloudSuite Corporate

Sage 100cloud stores a flat list of account codes with optional Type, Division, and Department segments. Infor CloudSuite Industrial requires an 8-segment account code in the format 1-8-1-2-2-2-2-2 (eight positions total: one digit, up to eight characters, one digit, two digits, two digits, two digits, two digits, two digits). We parse each Sage account code, map its segments to the corresponding Infor positions, and flag any account that exceeds Infor's segment length limits. The chart of accounts structure must be finalized in Infor CloudSuite before any GL transaction data can be imported, which means this mapping is the first step in the transformation phase and requires coordination with Infor's implementation team during their initial configuration sprint.

Sage 100cloud AR_Customer records map to Infor CloudSuite Business Partners with BP Type = Customer. We preserve billing and shipping addresses, payment terms, credit limits, salesperson assignments, and the customer classification code. The BP Code in Infor is generated from the Sage customer number or account code. Customer-specific UDFs are exported to a sidecar CSV for manual re-entry because Infor CloudSuite does not support equivalent custom fields natively.

Sage 100cloud AP_Vendor records map to Infor CloudSuite Business Partners with BP Type = Supplier. We preserve address, 1099 settings, payment terms, W-9 status, and tax identification. The 1099 flag values must be preserved explicitly during transformation because Infor CloudSuite uses a different enumeration for tax reporting codes. BP Code is derived from the Sage vendor number.

Sage 100cloud IC_Item and IC_BOM tables export multi-warehouse, multi-bin, lot/serial tracking, and BOM hierarchies. We reconstruct BOM parent-child relationships in Infor CloudSuite Industrial's Item Master with bill of materials, map warehouse and bin assignments, and preserve lot/serial numbers as Infor inventory lot records. Multi-bin locations from Sage become Infor warehouse-bin combinations. The migration must occur after the chart of accounts is configured because inventory valuation accounts in Sage reference GL account codes that must exist in Infor before import.

Open accounts receivable are exported as individual invoice records with original invoice date, due date, amount remaining, aging bucket, and payment status. We preserve the original invoice date and due date, map the Sage AR clerk to an Infor user, and flag any invoices with a status other than open for customer review before migration. Invoices that have been partially paid carry the remaining balance amount only.

Open accounts payable records are pulled from the AP_Invoice and AP_Payment tables. We export invoice header and line-item detail, preserving vendor ID references, payment terms, and invoice numbers. Historical checks already cleared in Sage do not migrate; only open vouchers and invoices with a remaining balance transfer. The vendor BP record must exist in Infor before AP invoices can be imported because each invoice line references the supplier BP Code.

Sage 100cloud FA_Asset records include acquisition cost, depreciation method, accumulated depreciation (book value), useful life, and asset class. We export the full fixed asset register and reconstruct depreciation schedules in Infor CloudSuite. Sage supports multiple depreciation books per asset; we migrate the primary book and flag secondary books for manual verification. The asset's gl_account mapping must reference Infor account codes already established during the chart of accounts configuration phase.

Sage 100cloud SO_SalesOrder and OE_Invoice headers and line items are accessible via SQL. We export order header fields (order number, customer reference, order date, requested ship date) and all line items (item number, quantity ordered, unit of measure, unit price, warehouse, tax code). Custom fields attached to order headers require separate extraction and manual mapping to Infor's sales document structure because the field types differ. Partially invoiced sales orders are flagged for customer review.

PO_PurchaseOrder records are accessible via SQL but often include partial receipts already applied in inventory. We flag partially-received POs during scoping so the customer can complete receipt processing or void remaining lines before migration begins. Infor CloudSuite expects clean PO data without partial receipt conflicts. The PO header maps to Infor PO, line items map to PO lines, and vendor references resolve to the BP Supplier record established during vendor migration.

Sage 100cloud JC_Job and JC_Transaction tables hold project cost tracking data including job structures with phases, cost codes, budget amounts, and actuals versus estimate. Job structures, phase hierarchies, and cost code assignments map to Infor CloudSuite's project costing object. Budget versus actual values transfer directly. Cost code references to GL accounts require account code mapping already completed during chart of accounts configuration.

Sage 100cloud GL_Transaction and GL_Batch records export journal entry headers and line items with account codes, debit or credit amounts, and descriptions. We verify that all source fiscal periods are unlocked and fully posted before extraction. Batch numbers, journal entry numbers, and posting dates preserve. Account codes are reformatted to Infor's 8-segment format during transformation. Historical GL data migrates on a best-efforts basis for audit continuity; the customer should consult their auditor about whether historical periods require re-posting in Infor CloudSuite.

Payroll module data resides in PR_Payroll and PR_Employee tables. Year-to-date earnings, tax withholdings, and benefit deductions are exportable. Employee master data (address, hire date, pay frequency, exempt status) maps to Infor CloudSuite's Employee record. Deduction codes, garnishment setups, and benefit plan assignments require manual mapping by the customer's payroll administrator because benefit and deduction plan structures differ between Sage and Infor. Current-year payroll runs should be posted and finalized before migration begins.