Migrate your Sage 100cloud data

The GL account structure is a flat list of account codes with optional segments (e.g., Type, Division, Department). We export the full account master via SQL query or BIE data view, preserving account codes, descriptions, and classification flags. The destination GL chart is built in account-code order with rollup mappings.

Customer records include billing/shipping addresses, payment terms, credit limits, and salesperson assignments. We pull from the AR_Customer master table, mapping each customer to the destination's account or contact object. Open AR invoices are exported separately as line-item transactions.

Vendor master records include address, 1099 settings, payment terms, and W-9 status. We export the AP_Vendor table and match to the destination's vendor object. 1099 flag values must be preserved explicitly as they affect year-end reporting.

Sage 100cloud Inventory module supports multi-warehouse, multi-bin, lot/serial tracking, and BOM structures. We export IC_Item and IC_BOM tables, reconstructing BOM hierarchies in the destination. Bin and lot data are mapped as supplementary fields unless the destination has native lot/serial support.

Open accounts receivable are exported as individual invoice records with payment status, aging bucket, and balance. We preserve the original invoice date, due date, and amount remaining. Invoices with full payments applied are exported as historical records if scoped for migration.

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 and payment terms. Historical checks and 1099 amounts are included when historical transaction migration is requested.

FA_Asset records include acquisition cost, depreciation method, book value, and useful life. We export the fixed asset register and reconstruct depreciation schedules in the destination. Sage 100cloud depreciation methods (straight-line, declining balance, MACRS) are mapped to the destination's equivalent schedules.

SO_SalesOrder and OE_Invoice headers and line items are exportable via SQL. Custom fields attached to order headers require separate extraction and manual mapping to the destination's sales document schema. Multi-segment pricing (price matrix by warehouse/customer) often needs value-level mapping.

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 decide whether to export the PO as a closed document or carry forward open receipt lines.

JC_Job and JC_Transaction tables hold project cost tracking data. Job structures (phases, cost codes, budget vs. actual) map to project-management or job-costing objects in modern ERPs but require field-level reconfiguration because the schema differs significantly from destination-native project models.

Sage 100cloud stores custom fields and user-defined fields in separate extension tables whose schema varies by company database and module. There is no standardized API or export path for these. We flag every custom field identified during discovery and recommend manual re-entry or a post-migration cleanup pass.

Payroll module data resides in PR_Payroll and PR_Employee tables. Year-to-date earnings, tax withholdings, and benefit deductions are exportable, but deduction codes and Garnishment setups require mapping to the destination's payroll schema. Effective-dated changes across multiple pay periods complicate historical export.