Migrate from Sage 100cloud to Epicor Prophet 21

Sage 100cloud stores the GL account master in a flat table with optional segment columns (Type, Division, Department). We export the full account structure via SQL query, preserving account code, description, account type, and active status. Epicor Kinetic GL Accounts are created with the same account code structure; segment-aware accounts map to Epicor's standard or advanced account codes depending on the customer's chart configuration. Parent account lookups are resolved before child account inserts to satisfy referential integrity.

Sage 100cloud AR_Customer records include billing and shipping addresses, payment terms, credit limits, salesperson assignments, and 1099 flag. We export the full customer table, validate address completeness, and map each Sage customer to Epicor Kinetic Customer. The Sage customer code becomes the Epicor CustomerCmp.CustID. Payment terms are mapped to Epicor Terms tables, and any Sage customer-specific discounts are preserved as customer price group assignments in Epicor.

Sage 100cloud AP_Vendor records include address, 1099 settings, payment terms, W-9 status, and 1099 box assignments. We export the vendor table and map to Epicor Kinetic Supplier. The Sage vendor code becomes Epicor Supplier.SupplierID. 1099 flag values and W-9 status are preserved in Epicor Supplier fields. Payment terms map to Epicor Terms records. Any vendor-specific discounts are recorded as supplier terms adjustments in the destination.

Sage 100cloud Inventory module supports multi-warehouse, multi-bin, lot/serial tracking, and BOM structures across IC_Item and IC_BOM tables. We export Part master records including the stocking unit, costing method, cost levels, and commodity code. The Sage item code becomes Epicor Kinetic Part.PartNum. Stocking UOM and purchasing UOM map to Epicor Part.UOMClass and PartFrostings. For parts using lot or serial tracking, we map the Sage lot-numbering scheme to Epicor's lot and serial number configuration. Bin locations map to Epicor WarehseBin records.

Sage 100cloud IC_BOM tables define multi-level bill of material structures with quantity-per, scrap percentages, and operation steps. We reconstruct the BOM hierarchy in Epicor Kinetic using Part.BOM and PartRev records with the correct revision level, effective dates, and quantity-per relationships. Phantom BOMs, sub-assemblies, and BOM rollups are resolved by traversing the Sage BOM structure before insertion to ensure parent parts exist before their component BOMs are created.

Open accounts receivable from Sage 100cloud are exported as individual invoice records with original invoice date, due date, amount remaining, aging bucket, and payment status. We preserve the original invoice number, invoice date, and open balance. Sage invoices with partial payments retain the payment history as applied amounts in Epicor's AR Invoice payment records. Unapplied credits migrate as AR Credit memos linked to the customer account. CustomerCmp.CustID is resolved via the customer mapping before invoice insert.

Sage 100cloud AP_Invoice and AP_Payment tables are queried to export open accounts payable with header and line-item detail. We preserve vendor ID references, invoice date, due date, payment terms, and balance remaining. Epicor Kinetic AP Invoice records are created with VendorID resolved via the supplier mapping. Sage pre-payments and partially-applied invoices are mapped to Epicor AP adjustments and prepayment records. Historical check registers export as AP Payment records with check number and date preserved.

FA_Asset records in Sage 100cloud include acquisition cost, depreciation method, book value, useful life, asset class, location, and accumulated depreciation. We export the full fixed asset register and reconstruct depreciation schedules in Epicor Kinetic Fixed Asset records. Sage depreciation methods (straight-line, declining balance, sum-of-years) map to Epicor depreciation method codes. Placed-in-service date and asset life in months transfer directly. Sage asset classes map to Epicor Asset Group codes.

Sage 100cloud SO_SalesOrder and OE_Invoice headers and line items are accessible via SQL. We export open and held sales orders with customer reference, order date, ship date, and line-item detail including part number, quantity ordered, unit price, and discount. These map to Epicor Kinetic OrderHed and OrderDtl records. Epicor OrderHed.CustNum is resolved via the customer mapping. Custom fields attached to order headers require a separate sidecar extraction and manual mapping to Epicor OrderHed user-defined fields.

PO_PurchaseOrder records in Sage 100cloud are accessible via SQL but often include partial receipts already applied in inventory. We export PO header records with vendor reference, terms, and line-item detail including part number or description, quantity ordered, unit cost, and received quantity. Epicor Kinetic POHeader and PODetail are created with SupplierID resolved via the vendor mapping. Any partially-received POs are flagged during scoping so the customer decides whether to export the PO as open or as received before migration.

Sage 100cloud JC_Job and JC_Transaction tables hold project cost tracking data including phases, cost codes, budget vs. actual amounts, and labor and material transactions. Job structures map to Epicor Kinetic Project (for project-based tracking) and JobMfg records (for shop-floor production jobs) depending on the customer's usage. We export phase budgets and cumulative actuals, then reconstruct them in Epicor as project phases with WBS elements. Job transactions requiring Epicor job cost codes are mapped during the scoping phase because the cost code structure differs between platforms.

Sage 100cloud stores user-defined fields in module-specific extension tables whose schema varies by company database and are not exposed through any standard export path. We identify every UDF during discovery by querying the database schema for non-standard column names per module, export them to a sidecar CSV file, and flag them for manual re-entry in Epicor Kinetic. The sidecar CSV lists the UDF name, the source module, the record types it applies to, and a recommended Epicor UD field target. This step requires planning and budgeting because UDF content is customer-owned re-entry work.