Migrate from Acumatica to ERPNext

How to migrate from Acumatica to ERPNext without losing balances

Moving from Acumatica to ERPNext is a data and process project, usually led by finance and IT with an implementation partner, and the schedule is set by your renewal notice period rather than by the software. If your renewal is approaching, or a pricing change or data residency requirement has made you reconsider the platform, start by agreeing who owns the cutover decision and the sign-off on balances. The effort is driven less by the number of users and more by how much business logic you have built around Acumatica. The hardest parts are open balances (open receivables, payables, purchase orders, sales orders and inventory in transit), the customizations and the integrations that feed or read from Acumatica. Those are the items that most often slip.

The sequence matters more than any single tool. Start by inventorying customizations, Acumatica customization packages, reports, automation schedules and integration endpoints, and decide for each whether ERPNext covers it natively, through configuration, or through a Server Script that must be enabled with the server_script_enabled setting in version 15 and later. Then choose the extract path: a backup copy of the SQL Server database gives you full history for analysis, while API-based extraction gives you cleaner entity-level data. Map Acumatica branches and companies to ERPNext companies, and decide early how dimensions such as projects, departments or segments will be represented, because these decisions affect every later import.

Cost is mostly people time and the cost of the platform you run. The software license is not the main line item, since ERPNext is GPL-3.0 licensed and self-hosting it is free according to the ERPNext pricing page. Ask any implementation partner for a fixed-scope quote built from a written list of entities, integrations, customizations and reports, and confirm what is included in data cleansing, test cycles and cutover support. Confirm also which version you will target, since ERPNext v14 reached end of life on January 31, 2026 according to Frappe's supported versions page. Plan for at least one full trial load and a parallel reconciliation of balances before go-live, and treat the reconciliation report as the acceptance test.

Which Acumatica capabilities map to ERPNext, and what needs rework

This table compares the main Acumatica areas with the ERPNext modules that usually cover them and labels each row clean, needs rework or gap. Read the labels as a starting point for a written fit-gap review, since module depth and Acumatica customizations vary by implementation. The main takeaway is that standard financials and inventory tend to move cleanly, while customizations, industry-specific screens and integrations carry most of the rework.

Acumatica area	ERPNext counterpart	Status	What to confirm
General ledger and financials	Accounting module with companies, chart of accounts and fiscal years	Clean	Confirm how Acumatica branches and entities map to ERPNext companies and cost centers
Inventory and warehouses	Stock module with warehouses, items and batch or serial tracking	Clean	Confirm lot, serial and unit of measure conversions against your item master
Sales and purchasing	Selling and Buying modules with quotations, orders, invoices and purchase receipts	Needs rework	Confirm pricing rules, approval flows and returns logic against the Acumatica configuration
Manufacturing	Manufacturing module with bills of materials, work orders and job cards	Needs rework	Confirm routing depth, costing method and any shop floor screens used today
Projects	Projects module with tasks, timesheets and project-based billing	Needs rework	Confirm whether project costing and revenue recognition rules match your current contracts
Customizations and Acumatica customization projects	Custom fields, Server Scripts and custom apps built on the Frappe Framework	Needs rework	Confirm which screens, Server Scripts and approval steps are needed, since Server Scripts are disabled by default from version 15
Industry-specific or third-party extensions	Available only where a Frappe app exists or must be built	Gap	Confirm each extension in writing and treat any without a matching app as new development
Integrations with banks, shipping and tax services	REST API and custom integrations built for your endpoints	Needs rework	Confirm each connector, its data volume and who maintains it after go-live

What data can be extracted and what integrations must be rebuilt

Acumatica gives you two extraction paths, and each one covers different data. Masters, open documents, balances, attachments and integrations each need their own extract, mapping and test before cutover. The order matters, because ERPNext records link to one another and must exist before the records that reference them.

Acumatica API extraction

The API returns records through Acumatica's own endpoints, so you can control the entity order, filters and batch sizes. It only returns what those endpoints expose, which may leave out some customizations, system reports or attachments. Ask your Acumatica administrator which endpoints your edition and customizations expose, and run a full extract of one entity, such as customers, to check field completeness before you commit to a plan.

SQL Server backup copy

A backup copy of the SQL Server database holds the raw tables, so it often contains more data than an API extract. Reading it requires SQL Server tooling, and your team must map the schema to ERPNext fields and rebuild any logic the application computed in code. Restore the copy in a separate environment, compare row counts against Acumatica reports, and confirm the backup format and retention terms with Acumatica in writing.

Masters loaded first

Customers, suppliers, items, warehouses, the chart of accounts and branch-to-company mappings form the base layer. The ERPNext Data Import tool loads CSV or Excel files built from downloadable templates and supports child table rows, which suits item variants and address lines. The documentation advises importing only a few thousand records at a time, so plan batches and rerun the same template after each correction.

Open documents and balances

Open sales orders, purchase orders, unpaid invoices and stock on hand must load after the masters they reference. Opening balances need a reconciliation against the trial balance and inventory valuation at cutover, not just a count of imported records. Agree on a cutover date, freeze transactions in Acumatica during the final extract, and keep the last extract as the audit reference for the balances you load.

Attachments and document files

Contracts, scanned invoices, certificates and drawings often sit outside the transaction tables, so they can be missed in a records-only extract. Confirm how your Acumatica extract delivers files, including file names, linked record keys and folder structure. Then test how each file is re-linked to its ERPNext document in a staging site. Treat files as a separate workstream with its own acceptance check.

Integrations and custom logic

Bank feeds, tax services, eCommerce connectors, reporting feeds and any custom Acumatica logic must be listed and rebuilt or retired. In ERPNext, custom logic often runs as Server Scripts, which from version 15 are disabled by default and must be enabled with the server_script_enabled setting. Frappe Cloud public shared benches do not allow them, so confirm your hosting model before designing these rebuilds.

The migration sequence from inventory to decommission

This sequence moves Acumatica data into ERPNext in controlled stages, so each company's balances are proven before finance relies on the new system. Each step produces a named artifact that the next step depends on, and the cutover does not happen until the parallel run reconciles.

Inventory companies, customizations and integrations
List every Acumatica company, branch, ledger, customization, report, screen change and integration that touches finance, inventory, sales or purchasing. Record which ones feed other systems such as banks, payroll, tax or reporting tools, and which ones are retired. Finance owners and the internal Acumatica administrator sign off the list. The output is an inventory register that names each object, its owner and whether it is migrated, rebuilt in ERPNext or dropped.
Design the target data model and mapping workbook
Decide how Acumatica branches, companies and dimensions map to ERPNext companies, cost centers, accounts and any custom dimensions you need. Map the chart of accounts, items, units of measure, customers, vendors, warehouses and open document types field by field, including which ERPNext fields hold each Acumatica value. Agree the treatment of historical transactions, opening balances and document numbering. The output is a mapping workbook approved by finance and operations, with each source field tied to a target field and a load order.
Extract source data and archive a copy
Extract the source data through the method your Acumatica contract and environment allow, such as the database backup, API-based extraction or both, and record which method you used. Store a read-only archive of the extract with checksums and a note on its date and scope. Confirm with your vendor and internal administrator which data the extract covers, especially attachments, audit history and custom tables. The output is an archived source copy and an extraction log that the later reconciliation steps can reference.
Load a pilot company and reconcile its ledger
Choose one representative company with a small master data set and load its masters, then its open documents and opening balances, into a non-production ERPNext site. Use the Data Import tool with the downloadable templates, and keep each file small, since the documentation advises importing only a few thousand records at a time. Compare trial balances, open receivables and payables, and item quantities against the source for the same cutoff date. The output is a reconciled pilot ledger, with every difference logged and explained before the next step begins.
Run test loads with balance checks
Repeat the load for all companies in the agreed order, starting with masters and moving to open transactions, on a fresh non-production site each time. After each run, compare control totals for accounts, customers, vendors, stock valuation and open documents with the mapping workbook expectations. Record each load's files, errors and fixes so that reruns are repeatable. The output is a signed-off balance report per company and load, with an agreed tolerance for any rounding differences.
Operate a parallel run before cutover
Run ERPNext in parallel with Acumatica for a defined period agreed by the business, entering new transactions in both systems or in ERPNext with Acumatica as the reference, and reconcile results at each period close. Test reports, integrations, user roles and approval workflows that were rebuilt, and confirm that any Server Scripts you need are enabled on your deployment. Record each discrepancy and its root cause. The output is a parallel-run reconciliation pack that finance signs off as the basis for cutover.
Cut over and freeze the source system
Schedule the final extract, load and balance check against a documented cutoff, and freeze transactions in Acumatica during the window. Confirm the final balance report matches the approved parallel-run figures, then switch users, integrations and bank connections to ERPNext. Keep a rollback plan with a named decision owner. The output is a cutover record listing the cutoff time, the final balance sign-off and the owners who approved go-live.
Archive the source and decommission Acumatica
After the business confirms that open items, reports and audit queries are answered in ERPNext, retain the read-only archive and the final extract under your records policy, and confirm with your vendor how access and retention will be handled. Revoke Acumatica user accounts and integration credentials, then cancel or reduce the subscription as your contract allows. The output is an archived source copy with an index, a credential revocation record and a written decommission confirmation.

How to run Acumatica and ERPNext in parallel and cut over

Plan the cutover around the Acumatica renewal notice period in your contract, because that date sets how long you can run both systems at once. Confirm the notice terms, the end date of the current subscription and any post-termination access window directly with Acumatica before you fix a go-live date. A parallel period matters because the first ERPNext balances will almost always differ from Acumatica in small ways: rounding on multi-currency revaluation, open sales orders with partial shipments, and inventory valuation by warehouse. Reconciling trial balances, open AR and AP aging, and item quantities for at least one full closed period in both systems gives your finance team evidence that the differences are explained, not guessed at.

Freeze transactions at a defined cutover timestamp. Ask the business to stop posting in Acumatica at that point, close the open batches, and record the last Batch and document numbers in each module so the delta extract has a clean boundary. Then extract only what changed after the freeze, using the Acumatica API with a modified-date filter or a fresh copy of the SQL Server backup, and load it into ERPNext with the Data Import tool in small batches, since the documentation advises a few thousand records at a time. Keep the masters loaded earlier in sync with any changes made during the parallel period, and recheck the balances after each delta load before users are switched on in ERPNext.

How the migration changes by company size and starting point

A single-entity company with one chart of accounts usually has the most direct path. The migration centers on one company record in ERPNext, one chart of accounts, one set of warehouses and one fiscal calendar. Most of the effort goes into cleaning item masters, customer and supplier records and open invoices, because there are fewer structural decisions to make.

Chart of accounts: Map each Acumatica account to an ERPNext account once, and confirm account types (asset, liability, income, expense) match so reports still roll up correctly.
Open items: Decide whether open receivables and payables are loaded as opening balances or as transactional documents, and confirm the tie-out to the Acumatica trial balance.
Item and unit cleanup: Remove duplicate and inactive items before import, since the Data Import tool works best on clean, bounded batches.
Fiscal periods: Confirm the ERPNext fiscal year matches the Acumatica period structure so comparatives line up after go-live.
Customizations: Identify which Acumatica customizations are business rules and which are reports, because only the first set needs an equivalent in ERPNext.

Confirm with your finance team whether the single-entity assumption holds across all subsidiaries, branches and tax jurisdictions before you commit to this path.

The hosting choice changes who operates the migration environment, who controls the database and which settings are available. On Frappe Cloud, the platform handles infrastructure and some operations. On your own servers, your team or your implementation partner owns the stack, including backups, restores and the bench or Docker environment. Both paths need a staging site for test imports before production.

Settings access: Confirm which configuration options you need, such as Server Scripts. The Frappe documentation says they are disabled by default from version 15 and must be enabled with server_script_enabled, and Frappe Cloud public shared benches do not allow them.
Import limits: Plan imports in batches of a few thousand records, since the documentation advises against larger single loads on any host.
Backup ownership: Define who takes restore points before each import run and who tests them.
Support coverage: Check the Frappe supported versions page and the plan that matches your version before go-live, since warranty coverage depends on it.
Infrastructure work: For self-hosting, the frappe_docker setup covers MariaDB, Redis, workers, the scheduler and Nginx, and the single-file demo is for short evaluation only.

Confirm with the hosting provider and your security team which deployment model meets your data residency and access control requirements.

What drives migration cost and duration

This table lists the main drivers that move the cost and timing of an Acumatica to ERPNext migration, with the reason each one matters and how to keep it under control. Use it to shape the written scope you send to implementation partners, since the same drivers appear in every quote. Cost sits across the implementation partner, internal staff time and hosting, so compare quotes on the same scope rather than on headline totals.

Driver	Why it changes cost or effort	How to keep it down
Number of companies and dimensions	Each Acumatica company, branch or segment needs a mapped ERPNext company, cost centers and dimensions, plus separate balance checks.	Decide the ERPNext company structure before extraction and retire unused branches and dimensions first.
Data history volume	Years of closed transactions multiply extraction, transformation and reconciliation work, and large files need batching.	Migrate balances and open documents, and keep older history in the read-only archive you export.
Customizations and integrations	Acumatica customization projects, screens, business logic and third-party connectors must be rebuilt, replaced or dropped in ERPNext, where server scripts are disabled by default from version 15.	Inventory every customization and integration, then classify each as keep, replace with standard ERPNext, or retire.
Quality of master data	Duplicate customers, vendors, items and inconsistent units of measure force manual cleanup before import and repeated load cycles.	Cleanse masters in Acumatica before extraction and agree the cleanup owner and deadline in the scope.
Hosting choice	Self-hosting on your own servers through Docker Compose or bench adds infrastructure, backup, patching and monitoring work, while Frappe Cloud shifts some of that to a hosting contract.	Confirm hosting, backup and recovery responsibilities in writing and price each option against the same migration scope.
Import volume per load	The Data Import tool is documented for a few thousand records at a time, so large masters and transaction sets need many staged loads and validation passes.	Plan load sequences by entity, import masters first, and validate each batch before the next.
Internal staff time	Finance, inventory and IT staff must confirm mappings, review balances and test open orders, which the partner cannot do alone.	Name the business owners and reserve their time in the project plan before work starts.

What usually goes wrong and how to prevent it

Most failed Acumatica to ERPNext migrations fail on data and process, not software. The six risks below connect at cutover: a balance that does not reconcile, an account structure that does not map, or a batch that cannot be loaded will each block the next step. Check each one with a named owner before go-live.

Unreconciled opening balances

Opening balances for receivables, payables, inventory and bank accounts must equal the Acumatica trial balance and subledger totals on the cutover date, down to the cent. Set a reconciliation gate: no ERPNext period opens for transactions until the controller signs off each account against the source extract. Keep the extract, the import file and the reconciliation together as one evidence package.

Mismatched chart of accounts and dimensions

Acumatica branches, segments and custom dimensions do not map one to one onto ERPNext companies, accounts and cost centers. Build a mapping workbook that lists every source account, dimension value and item class with its target, and have finance approve it before any import. Test a single month of transactions through the mapping to catch a missing account before it reaches the full load.

Data Import batches that are too large

The ERPNext Data Import tool is documented for a few thousand records at a time, and child table rows, such as invoice lines, count toward the work. Split masters and transactions into ordered batches, load them in a staging site first, and log the row counts and errors per batch. Reloading one corrected batch is far cheaper than cleaning up a half-finished full load.

Undocumented customizations and integrations

Acumatica customizations, customization packages, scheduled reports and third-party connectors often hold business rules that nobody has written down. Inventory every custom screen, report, automation and inbound or outbound integration before design starts, and assign each one a keep, rebuild or retire decision. Server Scripts in ERPNext are disabled by default from version 15 and must be enabled with the server_script_enabled setting, so confirm that the target environment permits any rebuilt logic.

Missing user access design

Acumatica role-based access does not transfer automatically, and an ERPNext user with the wrong role can post, approve or view data they should not. Design roles and permissions from the segregation of duties matrix before loading users, then test that each role can complete its own transactions and cannot approve its own. Confirm how identity is federated, for example through LDAP or social login, before users log in to the new system.

Cutover without a freeze

If Acumatica stays open while balances are extracted, the transactions entered after the extract never reach ERPNext and the balances diverge. Define a transaction freeze window, agree the cutoff timestamp in writing, and run a final delta extract for anything posted after the first pass. Keep Acumatica read-only until the reconciliation gate passes, and keep the source data available for audit queries after it does.

Questions buyers ask before migrating from Acumatica to ERPNext

How long does an Acumatica to ERPNext migration take?

No duration can be given without a scoped inventory, because the timeline depends on the number of companies, the years of history you need, the count of open documents, and how much custom code and integration must be rebuilt. Start by counting entities: branches, chart of accounts segments, items, customers, vendors, open sales orders, open purchase orders and open invoices. Each of these drives the size of the import and the number of validation rounds. ERPNext's Data Import tool advises importing only a few thousand records at a time, so large masters and transaction histories are loaded in batches across several passes. Ask any implementation partner to base its estimate on that inventory and to write the assumptions into the scope before work starts.

What does it cost to move from Acumatica to self-hosted ERPNext?

The software has no license fee: ERPNext is GPL-3.0 licensed, and according to the ERPNext pricing page, self-hosting ERPNext is free. The recurring costs are the infrastructure you run (servers, database, backups, storage, and network), staff time for administration and upgrades, and any support contract you choose. The one-time costs are the migration work (extraction, mapping, import, validation, and cutover), rebuilding integrations, and user training. If you prefer managed hosting, the pricing page lists Frappe Cloud shared site hosting from 5 US dollars per month and Frappe Cloud servers from 20 US dollars per month for shared instances and 125 US dollars per month for dedicated servers. Ask any quote to separate one-time migration effort from recurring hosting and support, and to list each Acumatica subscription component it replaces.

Can our own team migrate from Acumatica to ERPNext without a partner?

Yes, a capable internal team can run the import, but the work is more than uploading spreadsheets. ERPNext's Data Import tool uses downloadable templates and supports child table rows, so accounting and inventory staff can prepare masters and open transactions, while engineers handle the extraction, transformation and reconciliation. Teams that lack a Frappe or ERPNext administrator, a staging environment, or someone who owns the chart of accounts mapping usually need outside help at specific points. Decide early which tasks stay internal and which are contracted, and write that split into the scope. Some Frappe support arrangements also depend on the version you run, so confirm the supported version list before choosing an install path.

What do finance and IT teams have to provide during an ERPNext migration?

Finance owns the decisions and the sign-off, and IT owns the environment and the data path. Finance must approve the chart of accounts mapping, the treatment of open receivables and payables, opening balances by period, tax codes, item costing and the cutover date. IT must provide the Acumatica extraction method, a SQL Server backup or API access, a hosted ERPNext environment with backups and access control, identity integration, and a staging environment for repeated test loads. Both teams should agree on who signs off each reconciliation report. Without named owners on both sides, mapping decisions stall and the import is repeated.

Do Acumatica customizations and Server Scripts carry over to ERPNext?

Not automatically. Acumatica customizations and integrations are written against Acumatica's own model, so each one must be inventoried, then either replaced with standard ERPNext features or rebuilt. In ERPNext, Server Scripts run Python on document events or as API endpoints. According to the Frappe Framework documentation, from version 15 they are disabled by default and must be enabled with the server_script_enabled setting. Frappe Cloud public shared benches do not allow them, so a custom logic requirement may push you toward a private bench or a self-hosted deployment. Confirm the exact version and hosting option before designing custom logic, and treat every rebuilt customization as a tested change.

How do we validate balances before going live on ERPNext?

Validate balances in layers before any user works in production. First, reconcile trial balances by period and company between Acumatica and ERPNext, including retained earnings and opening balances. Second, reconcile subledgers: customer and vendor balances, open invoices and payments, and inventory quantities and values by warehouse. Third, run a sample of open transactions end to end, such as an order through invoice and payment. Repeat the full load on a staging site until the reconciliation differences are zero or explained and signed off. Keep the reconciliation workbook and the import files as evidence for auditors and for your own change record.

Which parts of a migration does DeployOpen cover?

DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure, and most engagements are fixed-scope with scope, deliverables and timelines agreed in writing before work starts. For an ERPNext migration, that can include the extraction plan, mapping workbook, import runs, reconciliation evidence and cutover support, depending on what the written scope includes. DeployOpen does not publish a price list, and a quote follows from the written scope. Ongoing support and upgrades are available as retainers. DeployOpen does not issue audit reports or certifications, so any compliance evidence it prepares is reviewed by your independent auditor.

What should we ask for in an ERPNext migration quote?

Ask for a written scope that names the Acumatica data you will extract, the companies and branches in scope, the chart of accounts mapping approach, and the open documents to migrate. Request the list of deliverables: mapping workbook, import templates, validation reports, test loads, cutover runbook, and rollback plan. Ask who owns each reconciliation and what happens if differences remain at cutover. Ask how hosting, backups and upgrades are priced separately from the migration, and what support is included after go-live. A quote that cannot itemize these items is not yet comparable with another quote.

What changes for finance, IT and users after go-live

After go-live, the organization owns the upgrade and backup cycle. Acumatica handles platform maintenance under its subscription. With ERPNext on your own infrastructure, IT schedules backups of the MariaDB or PostgreSQL database and the site files, tests restores, and plans every version change. Confirm which ERPNext version you will run before the cutover. Frappe's supported versions page lists the end-of-life dates for each release line, and a version past its end of life will not receive fixes. Also confirm whether you will buy a Frappe Cloud support plan, because Frappe's policy ties warranty coverage to running a listed version with a matching support plan. Self-hosting itself carries no license fee, so that choice is a decision about support, not about software cost.

The minor release cadence matters more day to day. The frappe/erpnext releases page shows both supported major lines receiving frequent minor releases, so IT needs a standing routine: read the release notes, apply updates to a staging copy of the site, run the finance reconciliations again, and only then promote to production. Finance should agree who signs off on a change to the chart of accounts or to posting logic before it is deployed. Plan for at least one internal administrator who understands the Frappe bench commands, the scheduler and background workers, and the difference between a system setting and a customization. Server Scripts are disabled by default from version 15, so any custom logic that depends on them needs a deliberate decision about re-enabling them.

For users, the change is mostly in access and support. Confirm how identities will be provided: whether ERPNext will authenticate against your directory through the LDAP integration or through a social login provider configured with a Social Login Key, and who owns those integrations after go-live. Confirm who answers a user who cannot sign in, who approves new roles, and which partner or internal team handles fixes outside working hours. Those answers should be written into a support model before cutover, because nobody else will be running the system for you.

How DeployOpen scopes and runs an Acumatica to ERPNext migration

DeployOpen plans, implements, customizes, integrates, hardens, backs up, documents and supports self-hosted open-source platforms inside your own infrastructure, including ERPNext. For an Acumatica to ERPNext move, we start from a written scope that names the entities, companies, data extracts and validation checks involved.

How we scope

Inventory Acumatica companies, branches, dimensions, customizations and integrations that feed the ERPNext design.
Agree in writing which masters, open transactions and balances move, and which history stays in an archive.
Confirm the extraction route with you, either the SQL Server backup or API exports, before work begins.

How we build

Map Acumatica entities to ERPNext companies, accounts, items, warehouses and cost centers in a reviewed mapping document.
Set up ERPNext on your infrastructure with Docker Compose or the bench tool, sized to the scope you agreed.
Load masters and open documents in batches with the Data Import tool, then test each batch against the source.

How we hand over

Reconcile trial balances, open receivables, payables and inventory quantities against Acumatica before go-live.
Document the data mapping, import order, validation results and rollback steps in a handover pack.
Walk your finance and operations staff through the ERPNext screens, roles and the cutover runbook.

How we support

Offer ongoing support, upgrades and continuous testing as a retainer after go-live.
Plan version upgrades around the ERPNext release line you choose, with testing before each change.
Confirm with us in the quote which post-cutover fixes and reporting changes are covered by the retainer.