Migrate from Spectrum ERP to Acumatica

Spectrum vendor records map directly to Acumatica Vendors. Acumatica requires a Location record (with address and contact details) for each vendor before the vendor can receive purchase orders — FlitStack creates a primary Location automatically. Vendor hold status and payment terms are preserved as VendorClass assignment and TermsID lookup respectively.

Spectrum customer records map to Acumatica Customers with the primary Contact details carried over as a related Contact record. Acumatica Customers require an AccountType (BAccountType) of either Customer or Combined — for pure AR customers, Customer is assigned. Customer classes map to Acumatica CustomerClasses for AR terms and credit limit inheritance.

Spectrum's flat GL account codes map to Acumatica's segmented account structure. FlitStack parses the Spectrum account code and distributes segments according to the configured Acumatica subaccount mask. If Spectrum uses cost codes, these become separate subaccount segments — for example, a Spectrum account '4-120-COSTCODE' becomes Acumatica account '4-120' with subaccount 'COSTCODE'. Mask configuration must be defined before this mapping runs.

Spectrum journal entries migrate as Acumatica GL Journal Transactions with original entry date, batch description, and source module preserved. Multi-line entries are recreated as individual GL transactions within the same batch reference. FlitStack maps Spectrum's debits and credits to the corresponding Account records using the account mapping established in the GL Account step.

Spectrum inventory items map to Acumatica Stock Items with the base unit of measure carried over. Acumatica requires Warehouse records to exist before inventory quantities can be assigned — FlitStack creates a default warehouse from Spectrum's primary warehouse location if multi-warehouse is not in use. Lot/serial number tracking settings migrate as the same type in Acumatica (Lot, Serial, or None).

Open and closed Spectrum purchase orders migrate as Acumatica Purchase Orders. The order status (Open, Closed, Cancelled) is preserved as the PO status in Acumatica. Line items link to the mapped Vendor and Inventory Item records. If a Spectrum line references a non-stock item, Acumatica's Non-Stock Item (IN202000) is used — FlitStack creates the non-stock item automatically if it does not exist.

Open Spectrum sales orders migrate to Acumatica Sales Orders with customer, line items, quantities, and unit prices preserved. Tax calculations in Acumatica are destination-side tax zone dependent — FlitStack flags orders where Spectrum tax jurisdiction does not have a direct Acumatica TaxZone equivalent for admin review before finalization. Completed orders with no open quantities migrate as historical records.

Spectrum employee records map to Acumatica Employees with HR info (department, position, supervisor) carried over. Employee earnings items (pay types, deductions, benefits) migrate as Pay Group entries in Acumatica Payroll — this mapping is type-aware so hourly-rate employees get a different PayGroup than salaried. Active and terminated status is preserved.

Spectrum manufacturing work orders map to Acumatica Manufacturing Production Orders. If Spectrum tracks material and labor by operation, these become Material and Tool/Labor overhead items in the Production Order. The production order status (Released, In Process, Completed) maps directly. FlitStack surfaces bill of materials mismatches if Spectrum's BOM structure does not have a 1:1 equivalent in Acumatica's AM module.

Spectrum project records migrate as Acumatica Projects with start date, end date, status, and customer link preserved. Acumatica Projects require a customer to be assigned before the project can be released for billing — FlitStack sequences the migration so customers are loaded before projects. Spectrum cost codes map to Acumatica project Tasks using the subaccount or cost code translation established in the GL step.

Spectrum equipment records migrate to Acumatica Fixed Assets with acquisition date, cost, useful life, and depreciation method preserved. Acumatica Fixed Assets have a separate posting to the GL — the mapped GL accounts from the Spectrum equipment's depreciation accounts are used for the FA book setup. Active, under-maintenance, and retired statuses map directly.

Spectrum payroll batches and time entries migrate as Acumatica Time Entries linked to the corresponding Employee and Project/Task records. Billable flag and labor item code are carried over. Entries already processed through Spectrum's payroll cycle are migrated as Approved — entries in draft status are migrated as Pending Approval for Acumatica workflow handling.

Spectrum user-defined properties on any standard entity migrate as Acumatica custom fields. In Acumatica, custom fields are created via the Customization Project editor with a __C suffix convention — FlitStack's migration plan lists each custom field, its source data type, and the Acumatica field type it maps to (string, integer, date, boolean, or picklist). Picklist value mappings are defined value-by-value.

Spectrum file attachments on any record (vendor documents, employee records, work order specs) are downloaded and re-uploaded to Acumatica's file storage linked to the corresponding record. File size limits in Acumatica are enforced per upload — files exceeding the limit are flagged for split or compression before the migration run.

Spectrum workflow definitions, approval routing rules, and automation scripts have no direct Acumatica equivalent. Acumatica uses Screen-Based Workflows and the generic Workflow Engine — both require manual rebuild. FlitStack exports your Spectrum workflow definitions as a structured reference document that your Acumatica admin can use to recreate each rule in Acumatica's workflow designer. This is always a manual step outside the data migration scope.