Migrate from Solution ERP to Acumatica

Solution ERP account codes map to Acumatica Account Code (AcctCD) and optional Sub segment. In multi-entity Acumatica setups, each Solution ERP account must be assigned to the correct Subsidiary. Account types (Asset, Liability, Equity, Revenue, Expense) map to Acumatica Account Type. If Solution ERP uses cost-centers as a second segment, these map to Acumatica Sub codes — your Acumatica admin pre-creates the Sub segment values before import.

Solution ERP Customers map 1:1 to Acumatica Customers (AR303000). Customer name maps to CustomerName, account code to AcctCD, class to CustomerClass, and status to Status. Solution ERP's multi-level customer hierarchy collapses into a flat parent record with separate Location records for child entities in Acumatica. Primary contact information maps to the Contact section; additional contact persons map to the Contacts tab.

Solution ERP Vendors map to Acumatica Vendors (AP303000) with name to VendorName, account code to AcctCD, class to VendorClass, and status to Status. Payment terms from Solution ERP map to Acumatica Payment Terms via value mapping — terms like 'Net 30' map to the corresponding Acumatica TermsID. Multi-level vendor hierarchies collapse to a flat structure with separate Location records.

Solution ERP Stock Items map to Acumatica Inventory Items (IN202500). Item ID maps to InventoryID, description to Description, class to Inventory Class, item type to Item Type (Stock/Non-Stock/Service), and base unit to Base Unit. Valuation method (Average/FIFO/Standard) from Solution ERP maps to Valuation Method in Acumatica. Multiple stocking locations in Solution ERP map to separate Warehouse records in Acumatica's Warehouse Management.

Open Solution ERP Sales Orders map to Acumatica Sales Orders. Document number from Solution ERP maps to Order Nbr, customer reference to Customer Order Nbr, order date to Date, and requested ship date to Required Date. Line items (stock items) map to Detail lines with the Acumatica InventoryID lookup. Solution ERP order statuses (Open, Pending, Confirmed) map to Acumatica statuses via value mapping. Completed and invoiced orders in Solution ERP are not migrated — Acumatica begins with open transactions only.

Open Solution ERP Purchase Orders map to Acumatica Purchase Orders. Vendor reference maps to Vendor Ref, document date to Date, and expected receipt date to Expected Receipt Date. Line items map to POLine with the Acumatica InventoryID. Completed receipts and invoices in Solution ERP are not migrated. Acumatica's multi-step PO approval workflow is not enabled by default — your Acumatica admin configures approval chains separately.

Open Solution ERP AR Invoices map to Acumatica AR Invoices. Invoice number maps to Reference Nbr, customer to CustomerID, invoice date to Date, due date to Due Date, and amount to Amount. Line items map to detail lines with description and amount. Solution ERP's payment terms on each invoice override customer-level defaults via the TermsID field.

Solution ERP's customization projects add fields to standard entities — these have no automatic equivalent in Acumatica. We export custom field definitions from Solution ERP and recreate them in Acumatica's Customization Project Editor before data import. Each custom field in Solution ERP becomes a separate USR-defined field on the corresponding Acumatica screen. Custom fields must be deployed and published before their values can be imported.

Solution ERP's separate workflow engine (automated approval chains, escalation rules, email alerts, conditional field updates) has no direct equivalent in Acumatica. These must be rebuilt in Acumatica's configuration environment: Business Events, notification templates, and screen-level workflows. We export Solution ERP workflow definitions as a rebuild reference document and provide a mapping plan identifying each workflow and its nearest Acumatica counterpart.

Solution ERP's native reports and dashboard configurations do not migrate. The underlying data migrates to Acumatica, but reports must be rebuilt using Acumatica's Report Designer or Generic Inquiry tool. We flag which Solution ERP reports are used most frequently so your Acumatica admin can prioritize rebuild. Saved searches from Solution ERP are exported as reference lists.

Solution ERP users who have been assigned as document owners map to Acumatica Employees and Users. OwnerID on each record resolves by email match against Acumatica Users. Users with read-only access in Solution ERP are not automatically provisioned in Acumatica — your Acumatica admin creates their Employee record and assigns appropriate Roles before migration.

File attachments stored against Solution ERP customers, vendors, or orders migrate as Acumatica Files. Files are re-uploaded to the corresponding Acumatica record's attachments tab. Solution ERP's file size limits and document storage configuration map to Acumatica's file attachment settings. Large document archives may require Acumatica's external storage configuration.

Historical GL batches and journal entries in Solution ERP are generally not migrated unless specifically required for audit continuity. Migrating historical journal entries is high-risk because Solution ERP's account structure may differ significantly from Acumatica's mapped chart of accounts. If historical continuity is required, a targeted analysis of account code mapping is performed before committing any GL import.

Solution ERP payment terms (Net 30, Net 60, 2/10 Net 30, etc.) map to Acumatica Payment Terms records. Each Solution ERP term value requires a value-mapping entry to the corresponding TermsID in Acumatica. If Solution ERP uses non-standard term descriptions, the Acumatica admin creates matching Terms records before migration so that the value mapping resolves correctly.