Business Central vs ERPNext: when each one fits your ERP decision
Choose Business Central when your company already runs on Microsoft 365 and has Dynamics or Microsoft partner skills in place. Choose ERPNext when a per-user license fee, a hosting rule or a data residency requirement makes a self-hosted, license-free core the better starting point. Both products cover accounting, inventory and purchasing for small and midsize companies, so the decision turns on who pays for each user, where the data must sit and who will maintain the system after go-live. Use the points below to test each option against your renewal date and your own environment.
Business Central fits when Microsoft 365 is the center of daily work, when identity and administration already follow Microsoft standards, or when an existing Dynamics or Microsoft partner can deliver implementation and support under a contract you already trust. Manufacturing requires the Premium plan, so the licensing math changes once production users are counted. ERPNext fits when you want no per-user license fee for the ERP core, when you want to run it inside your own cloud accounts or data center, or when you prefer Frappe Cloud as a managed host. Self-hosting ERPNext is free according to its pricing page, while Frappe Cloud shared hosting starts at 5 US dollars per month. Those figures cover hosting only, so add implementation, support and staff time before comparing totals.
Four factors should drive the decision. First, count users by plan: confirm current Essentials and Premium per-user prices with Microsoft or your partner, and separate office users from shop-floor users. Second, test manufacturing and service depth against your own bills of materials, work orders and service contracts. Third, plan release discipline. ERPNext v14 reached end of life on January 31, 2026, v15 is planned to be supported until the end of 2027 and v16 until the end of 2029, and Frappe warranty requires a matching support plan. Fourth, check in-house skills: from version 15, Server Scripts are disabled by default and need the server_script_enabled setting, and Frappe Cloud public shared benches do not allow them.
Business Central or ERPNext: which scenario fits you
This table maps common buyer scenarios to the platform that usually fits better and the condition that makes the advantage matter. Read each row against your own user mix, data rules and team skills, because the better fit changes when those conditions change. Treat the examples as starting points to test, not as a verdict on either product.
| Scenario | Better fit | Why and when it matters |
|---|---|---|
| Microsoft 365 is the core of daily work | Business Central | Teams that already run Outlook, Excel, Teams and Entra ID get the closest integration with Business Central. The advantage matters most when finance staff live in Excel and approvals run through Microsoft tools. ERPNext can still integrate through its own SSO options, so confirm the connectors you need. |
| Many occasional users, such as approvers or sales reps who enter a few records a month | ERPNext | Business Central licenses are priced per user on Essentials or Premium plans, so each occasional user adds a recurring cost. ERPNext has no license fee for self-hosting, so the cost of user growth is mainly infrastructure and support. Confirm the current Business Central licensing terms with Microsoft or a partner before comparing. |
| Manufacturer with shop-floor users who need production and work orders | Depends on depth needed | Manufacturing in Business Central requires the Premium plan. ERPNext covers bills of materials, work orders and subcontracting in its manufacturing module. Choose by which functions your planners need and how many shop-floor users must log in, then test both against a sample routing. |
| Data must stay in your own data center or air-gapped network | ERPNext | ERPNext can run on your own servers with Docker Compose or the bench command line tool, with MariaDB or PostgreSQL. Business Central on premises can also stay in your data center, but it must be kept current on Microsoft's release waves. Confirm residency rules with your assessor before choosing. |
| Team with strong Python skills and a plan to customize | ERPNext | ERPNext customizations use Frappe apps, and server scripts run Python on document events. Starting with version 15, server scripts are disabled by default and must be enabled with the server_script_enabled setting, and Frappe Cloud public shared benches do not allow them. Business Central customizations use AL extensions, so AL skills matter more than Python skills in that case. |
| Team with AL developers and existing extensions | Business Central | Existing AL extensions and partner-built add-ons keep their value in Business Central, and rebuilding them as Frappe apps is a separate project. The advantage matters when extension count is high. Ask your partner to inventory extensions before deciding. |
| Preference for managed hosting over self-operation | Depends on hosting model | Business Central online is hosted by Microsoft in the Microsoft cloud. ERPNext can run on Frappe Cloud, which offers shared and dedicated hosting, or on your own servers. Choose managed hosting if your team has no capacity to patch and back up. Confirm Frappe Cloud support plans and version coverage against Frappe's supported versions page. |
| Need to keep a version without forced upgrades on a fixed schedule | ERPNext | ERPNext versions have published end-of-life dates, and minor releases arrive frequently, so you plan upgrades on a schedule you set. Business Central on premises must stay on a supported release wave to remain supported. Check your version against the supported versions page before deciding. |
| Exit or migration from Business Central later | Depends on data access | Business Central online can export a BACPAC file to Azure storage, but only with a paid subscription and up to 10 times per month per environment. Microsoft does not support creating a working on-premises environment from that BACPAC. Plan your extraction route early, whichever platform you choose. |
What the license fee buys on each side
Business Central charges per user under Microsoft's plans, while ERPNext's software carries no license fee. On the open-source side, recurring costs move to servers, support, upgrades and any implementation partner. Use these cards to sort which charges recur and which must appear in a written quote.
Business Central Essentials and Premium plans
Business Central is licensed per user, and Essentials and Premium are the two plans this comparison covers. Premium carries the manufacturing functions, so a manufacturer's user count often drives the largest recurring line. Plan prices are not in the facts for this page, so confirm current per-user rates with Microsoft or a partner. Ask whether the quote includes online hosting or on-premises licensing.
ERPNext under GPL-3.0
ERPNext is licensed under GPL-3.0, and the pricing page states that self-hosting ERPNext is free, so the software itself carries no license fee. Costs move to the servers, the database, backups and the staff or partner who runs them. Review what GPL-3.0 means for any custom Frappe apps you distribute outside your organization, and confirm the position with counsel before you ship them.
Frappe Framework under MIT
The Frappe Framework that ERPNext runs on is MIT licensed, a separate license from ERPNext's GPL-3.0. Custom apps and framework code you build on it are governed by their own terms, so a licensing review should cover both layers. Your team will also plan framework upgrades alongside ERPNext upgrades, and the cost of that work belongs in the internal estimate.
Frappe Cloud support plan for warranty
Frappe's supported versions policy says a customer must run a listed version and hold a matching Frappe Cloud support plan to receive warranty coverage from Frappe. Self-hosting without that plan leaves support to your own staff or a partner. Ask any quote to state which ERPNext version is covered, how long that version is supported, and who responds when a release changes behavior.
Certified implementation partners
The ERPNext pricing page says implementation is available through certified partners, so implementation is a separate service that must be quoted. Ask each partner to show its Frappe certification and the ERPNext versions it has implemented. Put the data migration, custom apps, integrations and go-live testing into the written scope, with deliverables and timelines agreed before work starts.
Frappe Cloud hosting tiers
According to the ERPNext pricing page, Frappe Cloud dedicated servers start at 125 US dollars per month, shared servers at 20 US dollars per month, and shared site hosting at 5 US dollars per month. These are starting points, not a full quote. Compare database backup, storage, region and support terms with the cost of your own servers before you choose a tier.
Business Central vs ERPNext capabilities, feature by feature
This table compares core ERP capabilities, data import, identity and hosting between Business Central and ERPNext. ERPNext entries reflect its documented scope and supported versions, while Business Central entries flag what to confirm with Microsoft documentation or a partner for your plan. Use it to shortlist gaps early, then test every item marked for confirmation against your own process list.
| Capability | Business Central | ERPNext |
|---|---|---|
| Accounting | Core financials in the Essentials and Premium plans. Confirm dimensions, posting groups and tax handling for your jurisdiction. | Accounting is in core scope. Confirm multi-currency, tax setup and period closing for your jurisdiction. |
| Order and inventory | Sales, purchasing and inventory are included. Confirm warehouse, lot and serial tracking against your plan. | Order and inventory management is in core scope. Confirm batch, serial and valuation methods in the ERPNext docs. |
| Manufacturing | Manufacturing requires the Premium plan. Confirm which production planning and shop-floor features it includes. | Manufacturing is in core scope. Confirm bills of materials, work orders and subcontracting fit your process. |
| Service and projects | Confirm service management and project accounting features with Microsoft or a partner for your plan. | Projects are in core scope. Service depth needs confirmation against current ERPNext modules. |
| Asset management | Confirm fixed asset depreciation methods and disposal support in Microsoft documentation. | Asset management is in core scope. Confirm depreciation methods and disposal workflows you need. |
| Reporting | Confirm built-in reporting and Microsoft 365 export options for your plan and user roles. | Confirm report builder, scheduled reports and export options in current ERPNext documentation. |
| Data import | Bulk loading from an existing system usually starts with a BACPAC export. See the migration pages for the path. | Data Import reads CSV or Excel templates, child table rows and public Google Sheets. Import a few thousand records at a time. |
| Identity options | Confirm sign-in options with Microsoft, including how on-premises identity is handled for your deployment. | Frappe documents LDAP integration and social login keys. Confirm the setup against your directory before rollout. |
| Hosting and release cadence | Online on Microsoft's cloud, or on premises kept current on six-month release waves. | Self-host with Docker, bench or a manual install, or use Frappe Cloud. v15 is supported until end of 2027 and v16 until end of 2029. |
How six-month Business Central waves compare with ERPNext supported versions
Business Central ships on Microsoft's six-month release waves, and the cadence you live with depends on where it runs. Online tenants receive each wave on Microsoft's schedule, so the change reaches your environment whether or not your team has finished testing it. On-premises owners must keep up with the waves to stay supported, which turns every wave into an upgrade project that touches AL extensions, integrations and reports. Treat each wave as a dated obligation. Ask your partner which wave your version belongs to, when that wave's support ends, and how much of your AL code must change for the next one. Microsoft's deployment overview describes the online and on-premises models and is the right starting point for that conversation.
ERPNext sets its support windows per major version. According to Frappe's supported versions page, version 14 reached end of life on January 31, 2026, version 15 is planned to be supported until the end of 2027, and version 16 until the end of 2029. That gives you a planning horizon measured in years, and you decide when to move between majors inside it. Minor releases arrive far more often. The ERPNext releases page lists v15.123.0 on October 14, 2026 and v16.51.1 on October 15, 2026. The warranty condition matters more than the calendar. Frappe's policy says customers must be on a listed version and subscribed to a matching Frappe Cloud support plan to receive warranty coverage, so if you self-host, confirm with Frappe whether a support plan fits your setup and which version it covers before you commit to a major version.
Test each cadence against a different checklist. For Business Central waves, run a sandbox copy of production through the new wave before it reaches production, and cover posting routines, extension compilation, reports and any API consumers that call the service endpoints. For ERPNext, the test is narrower but sharper. After every major upgrade, confirm that server scripts still run, because from version 15 they are disabled by default and need the server_script_enabled setting. Check that custom Frappe apps are pinned to a version that matches the target major. Rehearse each minor release in staging, since patches arrive often enough that an untested patch will eventually reach production. Agree a written patch window with whoever runs the platform, so the frequency is a decision you own.
AL extensions, Frappe apps or server scripts: how customization differs
Business Central customizations are built as AL extensions, written in the AL language and developed with Visual Studio Code and the AL development tools. An extension adds fields, pages, reports and logic on top of the base application without modifying Microsoft's code, which is what allows the base to be upgraded. The main cost sits in the upgrade path: each release wave can change base objects that extensions depend on, so teams rebuild and retest extensions against the new version before each wave.
- Event subscribers: Extensions hook into published events in the base application, which limits breakage between versions compared with objects that are changed directly.
- Upgrade testing: Each release wave requires building and regression testing every extension against the new base, and this effort recurs for the life of the deployment.
- Deployment paths: Online extensions are published to the tenant, while on-premises deployments install them into the server instance. Confirm the current steps in Microsoft's deployment overview.
- Dependency review: Identify which customizations rely on base objects that are not exposed as events, since those are the ones most likely to need rework at each wave.
Skills for this model are AL, the Business Central object model, Visual Studio Code and familiarity with the base application's posting logic. Check the number of extensions that touch posting and standard tables before estimating upgrade work with your partner.
ERPNext runs on the Frappe Framework, and a Frappe app is a Python package with its own doctypes, pages, client-side JavaScript and hooks. Apps are installed into a bench or a Docker-based deployment and live in a repository your team controls. This model supports larger functional additions than server scripts, and it is the path most suited to logic that needs tests, code review and versioned releases.
- Code ownership: The app is versioned, reviewed and deployed like any other software, so changes can be traced and rolled back.
- Container builds: On self-hosted installs, apps are added to the bench or to a custom image built from the frappe_docker repository. Confirm the build process your container setup requires.
- Major version moves: When ERPNext or Frappe moves to a new major version, the app must be tested and adapted. The supported versions page lists which major versions are in service and when each reaches end of life.
- Hosting fit: Self-hosting and dedicated hosting leave app installation under your control, while shared public benches restrict what can be installed.
Skills for this model are Python, the Frappe Framework's doctype and hook model, Git and container tooling. Confirm the target major version and whether your hosting plan permits custom apps before you scope the build.
Server Scripts are Python snippets created in the ERPNext interface that run on document events, such as before save or on submit, or that expose an API endpoint. They are the lightest customization path because they need no app repository and no deployment step. They are also the hardest to govern, because a change made in the interface can alter production behavior immediately. From version 15, they are disabled by default and must be enabled with the server_script_enabled setting, and Frappe Cloud public shared benches do not allow them.
- Enablement: On self-hosted installs, the
server_script_enabledsetting must be switched on before any script runs. A security owner should approve that change and record it. - Hosting constraint: Frappe Cloud public shared benches do not allow server scripts, so this path requires self-hosting or a hosting plan that permits them. The Server Script documentation describes the supported events and endpoints.
- Scope limits: Scripts suit small validations and simple integrations. Larger logic belongs in a Frappe app with tests and version control.
- Change control: Define who may create and review scripts, and keep an audit trail of edits to production logic.
Skills for this model are Python and the ERPNext document events, with clear administrative ownership of the site. Check that each planned script runs under your hosting plan and decide in advance which scripts should move into a Frappe app as they grow.
Where the data sits: Microsoft cloud, your servers or Frappe Cloud
Business Central and ERPNext differ most in where the database lives and who operates it. The four hosting paths below decide data residency, backup access, patching and who answers for each. Check each option against your residency rules and your team's operating capacity before comparing licenses.
Business Central online in the Microsoft cloud
Microsoft hosts the Business Central database in its cloud, so patching and platform operations sit with Microsoft under the subscription. Your team controls tenant settings and environments, not the underlying infrastructure. Confirm which Microsoft cloud regions and data location commitments apply to your tenant, and whether your residency rules accept that location. Ask how database exports are handled, since a BACPAC export is limited to a paid subscription and 10 times per month per environment.
Business Central on premises on SQL Server
On-premises deployment places the database on your own SQL Server, so you control data location, backups and network access. Your team carries patching, server sizing, disaster recovery and the upgrade work that comes with each release wave. Confirm which SQL Server and Windows versions your release supports, and who on your side will run the upgrades. Note that Microsoft does not support building a working on-premises environment from a BACPAC exported from Business Central online.
ERPNext self-hosted with Docker Compose or bench
ERPNext runs on your own servers, in your own cloud account or in an air-gapped network, using either Docker Compose or the bench command line tool. Your team owns the MariaDB or PostgreSQL database, Redis, background workers, the scheduler, backups and TLS. The production Docker images are maintained in the frappe_docker repository, while its single-file demo setup is meant only for short-lived evaluation. Ask an implementer to confirm the topology, backup scheme and restore tests before go-live.
Frappe Cloud shared and dedicated hosting
Frappe Cloud is the managed option, with shared sites and dedicated servers. Shared site hosting starts at a low monthly figure, while dedicated servers start higher, so server tier drives the recurring cost. Frappe Cloud public shared benches do not allow Server Scripts, which affects customization choices. Confirm the data region, backup retention, restore process and whether your chosen plan meets your residency requirement before committing.
MariaDB and PostgreSQL database choice
ERPNext supports both MariaDB and PostgreSQL, so your database team can standardize on the engine it already runs and supports. This choice affects backup tooling, replication, monitoring and the skills needed for restores. Business Central instead uses SQL Server, either in Microsoft's cloud or on your own servers. Ask your ERPNext implementer to confirm which database version the target release supports and how point-in-time recovery will be configured.
Identity and compliance responsibilities
Business Central identity runs through Microsoft Entra ID, while ERPNext can use LDAP and social login keys for single sign-on. Access logs, retention periods and encryption at rest become your responsibility on self-hosted deployments. Compliance readiness, including control design and evidence collection, is prepared by your team and assessed by independent auditors, not by the hosting vendor. Confirm which controls your framework needs and who will hold the evidence.
What drives the cost of each side
On the Business Central side, the recurring cost is the per-user subscription on the Essentials or Premium plan, and Premium is the plan that manufacturing requires. Confirm the current per-user rates and which plan each of your roles needs directly with Microsoft or your partner, because the mix of full users and limited users drives the monthly total more than any other single input. The one-time cost is the partner work: implementation, data migration, and extension development in AL. Partner services are usually the largest line in the first year, and they recur in smaller amounts through support and changes. Ask each partner for a written, fixed-scope proposal that separates configuration, data migration, each AL extension, testing and go-live support, so you can compare line items rather than totals.
On the ERPNext side, the software itself carries no license fee, and self-hosting is free according to the ERPNext pricing page. The costs you carry are the ones you would otherwise buy from the vendor: servers or cloud instances, MariaDB or PostgreSQL storage, Redis, backups with tested restores, monitoring, TLS certificates and the staff time to patch and upgrade. If you prefer managed hosting, Frappe Cloud shared site hosting starts at 5 US dollars per month, and Frappe Cloud servers start at 20 US dollars per month for shared instances and 125 US dollars per month for dedicated servers, per the same pricing page. Check current figures on that page before budgeting, since they can change. Implementation is available through certified partners, and the same written-scope discipline applies. Frappe warranty coverage also depends on running a listed version with a matching Frappe Cloud support plan, so ask any support provider which version and plan the quote assumes.
Across both sides, the biggest swing factors are the same: how much of your customization must be rebuilt, how often you upgrade, and who carries the upgrade work. Business Central customers on premises must keep pace with release waves, and ERPNext customers must stay on a supported major version, so budget a recurring upgrade effort either way. Ask every quote to state the number of AL extensions or Frappe apps in scope, which server scripts need to be enabled, who tests each upgrade, and what happens to fees when the scope grows. Whichever vendor or partner you choose, ask for the cost of the first upgrade after go-live in writing.
What moving from Business Central to ERPNext involves
The sequence turns Business Central master data, open balances and customizations into a tested ERPNext environment on your own infrastructure, with a documented cutover that your finance and operations teams sign off.
Confirm scope, version and deployment
Record which Business Central version you run, whether it is online or on premises, which companies, modules and currencies are in use, and which AL extensions and integrations depend on the data. DeployOpen and your team agree the in-scope data objects in writing before extraction starts. Your side supplies the license list, the extension inventory, the list of reports finance relies on and the named business owners for sign-off. The step is done when the scope document is approved and every extension has a keep, rebuild or retire decision.
Export data from Business Central
The export path depends on deployment. A Business Central online database can be exported as a BACPAC file to an Azure standard storage account, but only with a paid subscription and up to 10 times per month per environment, according to Microsoft Learn. Microsoft does not support creating a working on-premises environment from that BACPAC, so online data is loaded into SQL Server for extraction. On-premises customers extract directly from their SQL Server database. Your Azure administrator or database team provides storage access and the export window. The step is done when a complete export is restored to a staging SQL Server and row counts for key tables match the source.
Map the chart of accounts and dimensions
Map Business Central general ledger accounts, dimensions, posting groups, VAT and number series to ERPNext accounts, cost centers, item groups, tax templates and naming series. Finance leads make the decisions on account structure and dimension values, and DeployOpen documents each mapping as a table. Confirm how ERPNext will represent your dimensions, since ERPNext uses cost centers and other masters that may not map one to one with Business Central dimensions. The step is done when every posting group and dimension value has a target and the finance owner has approved the mapping file.
Load master data and open balances in batches
Create import templates from ERPNext's Data Import tool for customers, suppliers, items, accounts and opening balances, then load them in order: masters first, then transactions that depend on them. ERPNext's documentation advises importing only a few thousand records at a time, so large tables are split into batches and each batch is reconciled before the next starts. Keep the source record IDs in a dedicated field so later reloads update rather than duplicate records. The step is done when each batch has a reconciliation report showing loaded, rejected and updated counts, and the trial balance in ERPNext matches the Business Central figures at the cutoff date.
Rebuild AL extensions as Frappe apps or server scripts
Each AL extension is classified as replaced by standard ERPNext functionality, rebuilt as a Frappe app, or rebuilt as a server script. Server scripts run Python on document events or as API endpoints, and from version 15 they are disabled by default and must be enabled through the server_script_enabled setting. Frappe Cloud public shared benches do not allow them, so that hosting choice must be settled before this step. Your developers and DeployOpen build the custom logic and test it against migrated data. The step is done when every retained extension has a test case, an owner and a documented deployment path.
Run parallel tests and reconcile results
Run ERPNext in a non-production environment with migrated data and execute the same transactions as Business Central: sales orders to invoices, purchase orders to receipts, inventory adjustments, period-end close and the reports that finance and auditors use. Compare outputs line by line and log each variance with its cause and fix. Confirm that users, roles and single sign-on are configured as intended, using ERPNext's LDAP or social login guides where your identity provider is involved. The step is done when open variances are zero or accepted in writing and the user acceptance sign-off is recorded.
Cut over to production
Freeze transactions in Business Central, run a final export and delta load, reconcile the cutoff balances again, and switch users to ERPNext. Confirm backups for both systems before the freeze, and keep read-only Business Central access for a defined retention period agreed with finance and compliance. Decide in advance how any transactions entered during the parallel run are handled. Your IT team confirms DNS, certificates, scheduled jobs and integrations. The step is done when the cutover checklist is signed, the production trial balance matches the frozen source, and the rollback plan has been reviewed.
Hand over operations and document the environment
After cutover, DeployOpen delivers runbooks for backups, upgrades, user onboarding, custom app deployment and incident response, along with the mapping files, test evidence and reconciliation reports. Plan for the ERPNext release rhythm by checking the supported versions page and the release history before each upgrade. Decide whether production stays self-hosted with Docker or bench, or moves to Frappe Cloud, and confirm which support plan applies. The step is done when your team has run one routine task unassisted and the document set is stored in your own repository.
Questions buyers ask before choosing Business Central or ERPNext
What does ERPNext cost to run compared with Business Central?
ERPNext has no license fee under GPL-3.0, so the recurring costs are hosting, support and staff time. Self-hosting ERPNext is free according to its pricing page, while Frappe Cloud shared site hosting starts at 5 US dollars per month and dedicated servers start at 125 US dollars per month, according to the same page. Business Central is licensed per user on Essentials or Premium plans, and the Microsoft license is a recurring cost on top of any partner fees. Ask each vendor or partner for the license count by plan, the hosting model, and what support and upgrade work is included in a written quote.
How long does a migration from Business Central to ERPNext take?
The duration depends on the number of entities, the volume of history you keep, how much of your chart of accounts, dimensions and posting groups must map cleanly, and how many AL extensions must be rebuilt. ERPNext's Data Import tool is designed for a few thousand records at a time, so large histories need batched loads and repeated validation. No fixed duration is supplied for this work. Ask any implementation partner to break the timeline into data extraction, mapping, test loads, extension rebuild and cutover, and to tie each phase to written deliverables.
Can an internal team self-host ERPNext without a partner?
Yes, a capable internal team can install ERPNext, since it runs on Frappe Cloud, with Docker Compose, or manually with the bench command line tool. The harder part is running production: backups, background workers, the scheduler, upgrades and security patching all become your responsibility. The frappe_docker repository provides production images, but its single-file demo setup is meant only for short-lived evaluation. Confirm internally who owns on-call support, restore testing and version upgrades before choosing self-hosting over a managed option.
Does Frappe Cloud have to be used to run ERPNext in production?
No. ERPNext can be self-hosted with Docker or bench, and Frappe Cloud is one of several supported installation paths. Frappe Cloud does carry a specific rule: according to Frappe's supported versions policy, customers must be on a listed version and subscribed to a matching Frappe Cloud support plan to receive warranty coverage from Frappe. If you self-host, the warranty question is separate, so ask Frappe directly what coverage applies to your deployment and which versions are currently supported.
How do Business Central updates affect AL extensions and custom code?
Business Central releases arrive in waves that Microsoft schedules, and extensions must be tested against each wave before they are relied on in production. Online tenants receive these updates on Microsoft's schedule, which limits how much you control timing. ERPNext customizations are built as Frappe apps or server scripts, and from version 15 server scripts are disabled by default and must be enabled with the server_script_enabled setting, while Frappe Cloud public shared benches do not allow them. Ask your extension vendor and Microsoft partner to document the test effort per release wave before you commit.
Can Business Central data be moved out without Microsoft's help?
Online databases can be exported as BACPAC files to an Azure standard storage account, but only with a paid subscription and up to 10 times per month per environment, according to Microsoft Learn. Microsoft does not support creating a working on-premises Business Central environment from that BACPAC. The practical route is loading the BACPAC into SQL Server and extracting data from there. Confirm the export permissions, storage setup and monthly limit with Microsoft or your partner before planning the extract.
When is it worth hiring a partner for an ERPNext project?
A partner is worth considering when the migration involves many entities, heavy manufacturing or service workflows, or extension logic that must be rebuilt rather than dropped. Frappe's pricing page notes that implementation is available through certified partners. DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades and documents self-hosted open-source platforms inside your own infrastructure, typically under a fixed-scope agreement with written deliverables and timelines. A quote follows from that written scope, so ask any firm for the scope, data validation steps and post-go-live support before comparing offers.
How DeployOpen helps you evaluate, implement or migrate
DeployOpen is a Chainscore Labs company that plans, implements, integrates, hardens, backs up, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For Business Central vs ERPNext, we start with the written scope of what you need to keep, move or replace, then build and hand over an ERPNext environment you control.
How we scope
- Map which Business Central modules, plans and AL extensions your business actually uses before choosing a target.
- Document the ERPNext apps, manufacturing and service needs that must be covered, and where gaps need a decision.
- Agree scope, deliverables and timelines in writing before work starts, since most engagements are fixed-scope.
How we build
- Install ERPNext in your infrastructure using Docker Compose or the bench command line tool, with your choice of database.
- Rebuild required AL logic as Frappe apps or server scripts, noting that server scripts must be enabled in version 15 and later.
- Load master and transaction data through the Data Import templates in controlled batches, then reconcile balances against the source.
How we hand over
- Deliver configuration, data mapping, test results and runbooks that your finance and IT teams can review and keep.
- Walk through user access, single sign-on options and role settings so administrators can run the system without us.
- Confirm the version policy and upgrade plan with you, including which Frappe version is supported at handover.
How we support
- Offer ongoing support, upgrades and continuous testing as a retainer after go-live, scoped in writing.
- Plan minor-release updates and major-version upgrades on your schedule, checking which versions are still supported.
- Ask us to confirm hosting and support choices with Frappe, since Frappe Cloud support depends on a matching plan.
