Migrate from Focus ERP to Acumatica

Extract Focus data via API and assess schema gap

FlitStack AI connects to Focus ERP through its available export API endpoints—direct database read access or CSV export—depending on your Focus deployment type. We extract customer records, vendor records, inventory items, GL account codes, open sales orders, open purchase orders, AP/AR open items, and project/job records in parallel. During extraction, we catalog every custom field in use, note multi-company segmentation, and flag records that lack required foreign keys (e.g., a sales order referencing a customer that does not exist). The extraction produces a source-data manifest and a schema-gap report that identifies what Acumatica entities must be created before the load sequence begins.

Configure Acumatica schema: Companies, Branches, GL structure, and tax zones

Before any data lands in Acumatica, we work with your Acumatica administrator to configure the destination-side schema. This includes creating Acumatica Companies (or Branches) matching your Focus multi-company structure, setting up the chart of accounts with all required segments and subaccounts, enabling the Inventory, AP, AR, and Projects modules, and populating tax zones and tax categories that correspond to your Focus tax codes. If custom fields are required for Focus custom-field data, we create them at this stage using Acumatica's Customization Project editor. The goal is a destination system that is schema-ready when data begins loading.

Resolve master-data dependencies and load order for GL, inventory, vendors, and customers

Acumatica enforces referential integrity—customers must exist before sales orders, vendors must exist before purchase orders, and GL accounts must exist before inventory or AP transactions. FlitStack sequences the load in dependency order: GL accounts first (establishing the chart of accounts), then inventory items (so SKUs are available for order lines), then vendors, then customers. For multi-company setups, we load each company's GL and inventory before loading that company's customers and orders. Each load step runs a row-count validation against the source extract and an Acumatica record-count check to confirm completeness before the next phase begins.

Run a sample migration on a representative data slice and generate field-level diff

A representative slice—typically 200–500 records spanning customers, vendors, inventory items, GL entries, open sales orders, and AP/AR open items—migrates to Acumatica first. FlitStack generates a field-level diff that compares every migrated field against the source value. The diff report surfaces discrepancies such as a customer credit limit truncated to zero because Acumatica's currency precision differs, an inventory item that landed under the wrong item class, or a GL account that was deactivated because its account type was unmapped. You review the diff with our team, we correct the mapping, and the sample re-runs until the diff passes before the full migration commits.

Execute full migration with delta-pickup window and audit log

The full migration loads all validated records into Acumatica in the established sequence. A delta-pickup window—typically 24–48 hours after the full load completes—captures any records created or modified in Focus ERP during the cutover period when your team is still operating in the source system. Every operation is logged to the FlitStack audit trail, including record counts loaded per entity, field-level transformation decisions, and any records that failed validation and were deferred. If reconciliation fails or Acumatica record totals do not match Focus source totals, one-click rollback reverts the Acumatica environment to its pre-migration state so the team can re-diagnose and re-run.

Deliver migration summary, custom-field manifest, and workflow export for rebuild

After the migration and delta-pickup complete, FlitStack delivers a migration summary report: record counts by entity, any deferred records requiring manual resolution, and a list of records that received post-migration adjustments (such as AR/AP open items with partial payment history stored as notes). We also deliver the custom-field manifest (Focus custom field name → Acumatica custom field name and location) and a structured workflow export document (workflow name, trigger condition, approver list, notification action). Your Acumatica administrator uses these documents to complete the schema setup for custom fields and to rebuild Focus-equivalent workflows in Acumatica's screen-level approval and business-event tools.