Migrate from Maximum Software to Acumatica

Maximum Software customers map directly to Acumatica Customers. If the source uses location-based addresses (ship-to), these become separate Customer Locations in Acumatica under the same customer account. Branch scoping is applied during import based on source customer assignment. We also verify that each customer's tax registration ID is present in the Acumatica Tax table before import to avoid mismatched tax settings.

Vendors map 1:1 to Acumatica Vendors. Remit-to addresses and multiple payment terms per vendor require separate Vendor Locations in Acumatica. We preserve original vendor IDs in Source_System_ID__c for reconciliation. During import we validate that each vendor's tax ID matches an Acumatica Tax Registration record, and we flag any duplicate vendor names for cleanup before insertion.

Maximum Software account codes are mapped to Acumatica accounts with segment awareness. If Maximum Software uses multi-segment codes (e.g., 4000-000), we split them into Acumatica Account + Subaccount segments. Account classes (Asset, Liability, Income, Expense) are set per Acumatica requirement.

Inventory items migrate as Acumatica Stock Items. Lot/serial numbers, warehouse-specific stock quantities, and minimum reorder points map to the corresponding Acumatica Inventory ID, Warehouse, and Item Management fields. If Maximum Software uses lot tracking, we create Lot/Serial classes in Acumatica before import.

Maximum Software item variants (size, color, configuration) become Acumatica Subitems. Subitem requires a parent Stock Item; we create the parent during migration and link variants as subitems with the original variant code preserved in SubitemCD. We also ensure that each subitem is assigned to the correct inventory valuation method of its parent, and we record any lot or serial class associations in the subitem attributes.

Open Sales Orders migrate as Acumatica Sales Orders with original order dates and promised ship dates preserved. Order statuses (pending, confirmed, shipped, cancelled) map to Acumatica status codes. Completed orders are migrated as historical records with appropriate completion dates. We also preserve any order-level notes in a custom field for reference.

Open Purchase Orders map to Acumatica Purchase Orders with original PO dates and expected receipt dates. Receipts linked to POs in Maximum Software are reconstructed as separate Receipt transactions in Acumatica linked to the PO. We also carry forward any PO-level notes and the buyer contact information into a custom field for visibility.

Maximum Software AR documents become Acumatica AR Invoices. If the source stores invoices as part of a register (batch of entries), we split them into individual AR Invoice documents with original posting dates and reference numbers preserved. Terms and customer location assignment carry forward.

Maximum Software AP bills map to Acumatica AP Invoices. Vendor-specific terms and hold status are preserved. If Maximum Software stores bill batches, we create individual AP Invoice records in Acumatica with original invoice dates and vendor references.

Cash receipts and payments migrate as Acumatica Payments. Each payment is linked to the corresponding AR or AP document via reference fields. Unapplied cash balances are preserved as open payment entries in Acumatica. We also record the original payment method and any bank reference numbers in custom fields to maintain a full audit trail.

Historical GL batches migrate as Acumatica GL Journal Vouchers. Original posting dates, batch descriptions, and source module references are preserved. Batch-level approval status maps to Acumatica's hold/finalize workflow. We also verify that each voucher’s account and subaccount codes exist in Acumatica’s chart of accounts, and we flag any batch that references a closed fiscal period for prior review.

Maximum Software companies map to Acumatica Branches or separate Companies depending on whether inter-company eliminations are needed. Each branch gets its own GL, tax, and reporting settings. We require the target branch structure to be configured before migration runs. The mapping worksheet also records the default currency for each branch.

Custom fields in Maximum Software are created as Acumatica Custom Fields in the appropriate DAC (Customer, Vendor, StockItem, etc.). We support both column-style custom fields (added as DB columns) and name-value-pair fields depending on the field's usage pattern. We also ensure the custom field's access rights are set appropriately in the Acumatica security configuration.

Maximum Software users are resolved by email match against Acumatica users. Unmatched owners are flagged before migration; your team either creates Acumatica user accounts or assigns records to a fallback owner. Original user IDs are preserved in Source_System_ID__c. We also map each user's role and notification preferences to Acumatica's security groups during the import.

File attachments stored in Maximum Software are re-uploaded to Acumatica file storage and linked to the corresponding record. Large files may require Acumatica file size configuration adjustments. No document management workflow is recreated automatically. We also preserve the original file name and creation date as metadata within Acumatica's file entry for straightforward retrieval.