Migrate from Aptean SouthWare to Acumatica

SouthWare customer records map to Acumatica Customer entities. The Customer Class (residential/commercial) in SouthWare maps to Acumatica's Customer Class picker. Primary contact name, email, phone, and billing address transfer directly. Multi-contact support in Acumatica requires Customer Contacts tab population post-migration.

SouthWare vendor records map to Acumatica Vendor entities. Payment terms from SouthWare (Net 30, COD) map to Acumatica Terms objects. Remit-to addresses populate the Vendor Locations tab. Tax ID (EIN/VAT) goes into the Tax ID field on the vendor record.

SouthWare item records carry description, unit of measure, item class, and cost layer data. The item class controls valuation method (FIFO/average) and maps to Acumatica's Valuation Method field on Stock Items. The primary warehouse/location in SouthWare becomes the default warehouse on the Acumatica item record.

Open SouthWare sales orders migrate as Acumatica Sales Orders with original order numbers preserved in the Ext. Order Nbr. field. Order date and requested ship date transfer; the assigned sales rep resolves by email match to Acumatica users. Lines migrate with inventory item links and quantities.

Open SouthWare purchase orders migrate as Acumatica Purchase Orders with vendor link and expected receipt date preserved. If items have already been partially received in SouthWare, the open balance quantity is calculated and entered into Acumatica at migration time. Multiple line items with mixed receipt statuses transfer with their respective open quantities and unit costs. Purchase order totals reconcile to SouthWare records before closing the migration window.

SouthWare's numeric account codes (e.g., 1100-00) map to Acumatica Account CD values. Acumatica supports structured account codes with segments — if SouthWare uses department or location subcodes, each segment maps to an Acumatica Subaccount dimension. Chart of accounts structure reviewed before migration.

SouthWare departments and cost centers migrate as Acumatica Subaccounts. Subaccount codes and descriptions transfer; the Subaccount Type (e.g., Department, Project) maps to the Subaccount mask in Acumatica's chart of accounts setup. Multiple subaccount levels in SouthWare may require flattening or segment mapping.

SouthWare sales rep records map to Acumatica Salespersons. Commission rates and split percentages transfer as Salesperson Commission records linked to each salesperson entity. Email addresses on sales reps in SouthWare are used to match and resolve to corresponding Acumatica user accounts for order ownership assignment and approval routing.

SouthWare service order records and active service contracts migrate to Acumatica Field Service objects. Equipment linked to service orders in SouthWare becomes FSAssets in Acumatica with the same equipment ID and linked customer. Contract billing schedules transfer as FSContractDetail lines with the original contract end date preserved and billing frequency maintained.

SouthWare ImportMate rules define data import behavior for batch uploads. These have no direct Acumatica equivalent — Acumatica import scenarios perform the same function but require manual rebuild. FlitStack exports ImportMate rule definitions as a reference document for your Acumatica admin.

SouthWare SQLSync replicates data to MS-SQL for external reporting and business intelligence connections. Acumatica's Generic Inquiries and Report Designer provide similar reporting capabilities within the platform. Historical transactional data is migrated to Acumatica so standard reports reflect the complete fiscal timeline without external SQL dependencies. External SQL replication setup does not carry forward into the Acumatica environment.

SouthWare document attachments associated with customers, vendors, and items migrate as Acumatica Notes attached to the corresponding records. File size limitations apply with a default 25MB per file in Acumatica. Inline images embedded within notes are extracted, downloaded, and rehosted as standalone file attachments on the target record for maximum compatibility.