Migrate from SAVIO ERP to Acumatica

SAVIO ERP lacks a documented public API — data export requires direct database access or CSV dumps

SAVIO ERP does not expose a documented REST or SOAP API for programmatic data extraction. The application's API reference page describes only a token-based integration endpoint for pushing feedback into SAVIO, not for reading transactional data out. Most SAVIO instances run on a local SQL Server database, meaning the migration extraction phase relies on direct SQL SELECT queries against the SAVIO tables. We coordinate with your IT team to obtain read-only SQL credentials and map the physical schema (table names, column names, foreign-key relationships) before writing any extraction queries. If the SAVIO database is hosted on a shared server without dedicated read access, we use the application layer's built-in export function to generate CSVs — this is slower and may require manual column mapping. The extraction method is agreed upon before the migration plan is finalized.

Acumatica enforces UOM groups — SAVIO's free-form unit entries will fail import without pre-mapping

SAVIO ERP allows users to enter unit-of-measure values as free text (e.g., 'per sheet', 'kg', 'roll') without requiring association to a formal unit group. Acumatica's inventory module validates every Stock Item's BaseUnit and sales-order line UOM against an active UOM Group — an import record with a UOM that does not belong to a UOM Group will be rejected with a validation error at load time. Before any inventory or order data is loaded, we audit every distinct UOM string in the SAVIO export, match each to an existing Acumatica UOM Group (or create a new one), and write the mapping into the migration specification. This pre-work typically adds 2–4 days to the planning phase but prevents silent data rejection during the bulk import step.

SAVIO production/press-planning data has no native Acumatica equivalent and requires UDF scope decisions

SAVIO ERP stores manufacturing-specific fields — press number, plate specification, dryer schedule, load sequence, bar-code configuration, and per-sheet expense rules — as part of its production requisition and inventory screens. Acumatica's standard Manufacturing Order (AM201500) and Production Order screens have no native fields for these laminate-specific concepts. The only migration path is to create User-Defined Fields (UDFs with the UFL prefix) on the Manufacturing Order DAC. This requires an Acumatica Customization Project and a certified Acumatica partner to publish the customization to the tenant. We deliver a complete UDF schema specification (field name, type, label, pick-list values if applicable) so your reseller can pre-create the fields before the production-order import step runs. If the customization is not published before import, those fields cannot be loaded and the records will need a second-pass update.

Acumatica configuration and customization are reseller-mediated — extension delays affect migration timing

Acumatica's extension model — Customization Projects, UDF publication, screen-level business logic overrides, and report designer layouts — requires a certified Acumatica reseller to apply changes to a live tenant. Unlike self-service platforms, you cannot log into an admin panel and create a custom field; a reseller must publish the customization project. If your Acumatica implementation partner is not engaged early, the UDF schema pre-creation step (required for manufacturing data and non-standard UOMs) becomes a blocking item. FlitStack coordinates directly with your reseller to deliver the UDF schema specification and confirms publication status before the production-data import begins. Any delay in reseller engagement extends the migration timeline proportionally.

SAVIO's SMS/email alert logic and HR-Payroll module do not have Acumatica counterparts

SAVIO ERP's built-in SMS-email alert system (triggered on invoice generation, payment receipt, followup reminders, and outstanding balance) and the HR-Payroll module (attendance, visitor management, gate-in-out) have no functional equivalent in Acumatica's core Financials, Distribution, and Manufacturing suites. Acumatica handles notifications through its notification template framework and relies on third-party or custom integrations for SMS delivery. The HR-Payroll module must be sourced separately (Acumatica does not include native HR-Payroll). We export the alert rule definitions from SAVIO as a written specification document and flag the HR-Payroll gap explicitly in the migration plan. Rebuilding these capabilities in Acumatica is scoped as a separate implementation workstream outside the data-migration scope.