Migrate from Accolent ERP to Acumatica

Accolent ERP has no public API — migration requires custom database extraction

Accolent ERP does not publish a REST or SOAP API for external data access (verified on GetApp: 'No, Accolent ERP does not have an API available'). This means FlitStack AI cannot connect to Accolent using standard integration endpoints. We work around this by extracting data directly from Accolent's underlying database tables using a read-only connection scoped to the specific entities in scope. The extraction process requires a database connection string, read-only credentials, and the Accolent version number so we can map the correct table schemas — which change between Accolent releases. Teams should coordinate with their Accolent hosting provider or IT team to grant read-only database access before migration planning begins.

Multi-warehouse inventory in Accolent becomes LocationID in Acumatica — a schema pre-decision required

Accolent treats each warehouse as a first-class entity with its own stock records, purchase orders routed to specific sites, and receiving windows per location. Acumatica consolidates inventory at the company level and uses LocationID to distinguish sites within a single Warehouse record. The mapping decision — whether one Accolent warehouse equals one Acumatica Warehouse, or all Accolent warehouses collapse into Locations under one Acumatica Warehouse — must be made before migration because it controls how every inventory-related record (orders, receipts, adjustments) resolves its SiteID. We surface this decision in the pre-migration schema plan and flag any Accolent data anomalies (duplicate warehouse codes, orphaned stock records) before the migration runs.

Accolent extended properties map to Usr-prefixed DAC fields that must be pre-created in Acumatica

Accolent stores custom extended properties on any entity in internal tables with no standardized naming convention exposed in its UI. Acumatica requires custom fields to be defined as Usr-prefixed fields within the appropriate DAC (Data Access Class) using Acumatica's Customization Project editor before any data loads. This means every Accolent extended property column requires a corresponding Usr* field to exist in Acumatica — data cannot land in a non-existent field. We generate a field creation manifest from the Accolent extended property inventory, specifying the DAC name, proposed Usr* field name, field type, and pick-list values where applicable. Acumatica administrators must create these fields in the destination tenant before migration validation runs.

Accolent pricing tiers (Contract, Advertised, Special, Quantity Breaks) require decomposition before loading to Acumatica Price Classes

Accolent stores customer-specific pricing across multiple sub-tables: Contract Pricing, Advertised Pricing, Special Pricing, and Quantity Break tiers — each can coexist for a single customer-item combination. Acumatica's pricing model uses Price Classes and individual Price Records, where each rule is a separate row linked by CustomerID, InventoryID, and quantity breakpoints. The challenge is that Accolent allows multiple active pricing types simultaneously while Acumatica evaluates rules in a defined priority order. We extract every pricing rule as an independent row and assign a priority weight so the most favorable discount wins in Acumatica's evaluation — but this priority logic must be confirmed with the business before migration because it can change the prices shown to customers at quote time.

Accolent reports, dashboards, and saved report definitions do not migrate — underlying data does

Accolent ships hundreds of standard reports and allows users to build custom reports against its database tables. Reports integrate with Phocas BI and Power BI via nightly data sync. Acumatica has its own Report Designer and Generic Inquiry tool with a different schema structure. We migrate all transactional and master data so that Acumatica's native reporting tools can query the same information — but saved Accolent reports, Phocas dashboards, and Power BI datasets that reference Accolent field names must be rebuilt in Acumatica's report designer. We provide a data dictionary mapping Accolent field names to their Acumatica equivalents so the Acumatica admin can use it as a rebuild reference when recreating reports.