Migrate from Aptean SouthWare to Infor CloudSuite Corporate

SouthWare Customer master records map to Infor Customer (or Business Partner) with address, contact, credit limit, and payment terms preserved. SouthWare stores the customer file with integrated AR terms; we map payment terms to Infor's payment code table. Custom field-level objects discovered during profiling map to Infor custom fields on the customer form. The Customer must import before any Order or AR record because Infor enforces the parent lookup at insert time.

SouthWare Vendor records map to Infor Supplier with address, 1099 settings, and accounts payable terms preserved. 1099 classification maps to Infor's tax code and reporting configuration. The vendor-to-item cross-reference relationships stored in SouthWare's Vendor Maintenance file are exported separately and mapped to Infor's Supplier Item Cross-Reference table during item import.

SouthWare Item records (description, cost, price, UOM, warehouse tracking, bin locations) map to Infor Item Master. Assembly work order items and kit structures require decomposition: SouthWare stores kit components as line items with a kit header; Infor BOM and work order modules handle these as separate structures. We split kit headers and components into Infor BOMs and routings during the transform phase before writing.

SouthWare stores outstanding invoices, credit memos, and payment applications as distinct transaction files with open/closed status. We map these to Infor's AP and AR open item records, preserving invoice number, date, due date, amount, and applied payment status. The key constraint is that the vendor and customer parent records must exist in Infor before AP/AR import, and all unposted SouthWare transactions must be posted or explicitly excluded from the migration scope before cutover.

SouthWare GL maps to Infor GL with account structure preserved as Infor account codes with configurable segment separators. Journal entry lines migrate for open and current fiscal years; pre-closed fiscal years (SouthWare seals the GL when a fiscal year closes) migrate as account balance snapshots rather than individual entry lines. We flag all pre-closed periods and handle them as read-only historical balances, preventing any attempt to post retroactive entries in Infor.

SouthWare Sales Orders and Purchase Orders (headers, line items, fulfillment status) map to Infor Sales Order and Purchase Order respectively. We separate posted vs. unposted orders: posted orders migrate as historical closed records in Infor; unposted orders migrate as open orders with status that Infor's order workflow can continue. Order number, dates, terms, and line-level pricing, discounts, and tax codes map directly.

SouthWare warehouse tracking, quantity on hand, and bin locations migrate to Infor's warehouse structure. Assembly Work Order inventory sub-types map to Infor work orders with BOM and routing references. Equipment Rental Management module items migrate to Infor's rental or equipment tracking module if the target CloudSuite edition includes it; otherwise they map to a custom item configuration.

SouthWare stores Job Cost as a distinct file type for project-service businesses with phase-level profitability tracking. This maps to Infor's Project or Job Cost module. We preserve phase-level cost and revenue entries, job status, and the job-to-customer relationship. If the target CloudSuite edition does not include a project module, Job Cost maps to Infor's work order or cost center structure as a custom configuration.

SouthWare Fixed Asset records (register, depreciation schedules, asset classifications) map to Infor Fixed Assets. Accumulated depreciation and book value fields migrate to Infor's asset lifecycle model. Depreciation methods map to Infor's depreciation code table. Asset-to-location and asset-to-customer or vendor cross-references are preserved as Infor asset relationship records.

SouthWare payroll history (earnings, deductions, tax withheld, year-to-date figures) migrates to Infor CloudSuite HCM or the payroll module if included in the target edition. FICA and tax data require careful tax code mapping to Infor's tax jurisdiction table; federal, state, and local tax codes must be configured in Infor before payroll import begins. We export current-period and YTD compensation figures; individual paycheck records are optionally migrated as payroll history entries depending on the payroll module's data model in the target edition.

SouthWare Service Orders include dispatch scheduling, technician assignment, repair history, and warranty references. These map to Infor's Service Management module (available in specific CloudSuite editions). Warranty history migrates as linked asset service records; technician assignment migrates as resource allocation entries. If the target CloudSuite edition does not include service management, service orders migrate as work order or project task records.

SouthWare Field-Level Objects and custom Field Filters created by Solution Partners are discovered only during data profiling. We run a full metadata discovery pass on the source database before building the mapping spec, identify all custom field definitions, and generate per-field mappings to Infor custom fields. The destination CloudSuite edition must support the equivalent custom field type. Any custom object that cannot map to a standard Infor object is documented as a custom object requiring Infor Configuration Console setup before import.