Short answer: ERPNext deployment and customisation means choosing where the system runs (a managed cloud, your own AWS or Azure account, or on-premises servers), then shaping it to your processes with custom fields, doctypes, workflows, print formats, reports and scripts. Good projects also cover integrations, data migration, training and a plan for upgrades.
ERPNext is a fully open-source ERP built on the Frappe framework. It covers accounting, stock, purchasing, sales, manufacturing, projects and HR, and it is popular with businesses that want flexibility without per-user licence fees for the software itself. If you are still comparing platforms, start with our guide to Odoo vs ERPNext vs Oracle. This post is for businesses that have chosen ERPNext, or are close to it, and want to know what deployment and customisation actually involve.
Where can ERPNext be deployed?
There are three main options for ERPNext hosting, and each shifts responsibility in a different way.
Managed ERPNext cloud. Frappe offers a hosted service, and you can sign up and start configuring quickly. The provider looks after servers and updates, but you have less control over the environment, custom apps and where data is stored.
Self-hosted in the public cloud (AWS or Azure). ERPNext runs on Linux virtual machines or containers in your own cloud account. You choose the region, so you can keep data in an Australian data centre, and you control backups, scaling and access. You are also responsible for patching, monitoring and security. Our cloud solutions team sets up and manages this kind of environment.
On-premises. Some businesses prefer ERPNext on their own servers, often for site connectivity or internal policy reasons. It gives the most control, but you carry the hardware, power, backup and disaster recovery burden.
Whichever option you choose, plan for separate production and test environments. Customisations and upgrades should be tested before they reach live users.
Our team deploys ERPNext using either the official Docker setup or the Frappe bench tooling, depending on your hosting and how you want upgrades managed. Docker suits containerised cloud hosting, while bench gives fine-grained control on a dedicated server.
What can be customised in ERPNext?
One of ERPNext’s strengths is how much you can change without touching the core code. The main tools are:
- Custom fields. Add fields to existing forms, such as a delivery window on sales orders or a compliance reference on suppliers.
- Custom doctypes. A doctype is ERPNext’s building block for a record type. You can create new ones for things the standard system doesn’t track, such as equipment hire, inspections or job cards.
- Workflows. Define states, approvers and rules, for example purchase orders over a set value needing manager approval.
- Print formats. Design quotes, invoices, delivery dockets and statements with your branding and the details your customers expect, including GST information.
- Reports and dashboards. Use the built-in report builder for simple reports, or query and script reports for more complex analysis.
- Scripts. Client scripts change form behaviour in the browser. Server scripts handle validation, calculations and automation on the server.
- Custom apps. For larger changes, a separate Frappe app keeps your code apart from the standard product, which makes upgrades much easier.
The rule we follow is simple: configure first, customise second, and write code only where it gives you a real advantage. When a requirement goes beyond ERPNext, our software development team can build it as a custom app or a separate service.
How does ERPNext integrate with other systems?
ERPNext exposes a REST API for its records and supports webhooks, so other systems can read and write data or react to events. Common ERPNext integrations for Australian businesses include:
- E-commerce stores, for orders, stock levels and pricing
- CRM platforms, for customers and quotes
- Microsoft 365, for email, documents and single sign-on
- Payroll and banking, including bank statement imports
- Warehouse, shipping and field service apps
Some integrations are ready-made, while others need a custom connector. We design each one with error handling and logging, so a failed sync is caught rather than silently losing an order. See our integration services for how we approach this.
How is data migrated into ERPNext?
ERPNext includes a data import tool that loads records from CSV or Excel templates. The tool is the easy part. The real work is the data itself:
- Decide what to move. Usually customers, suppliers, items, price lists, chart of accounts, open orders and opening balances. Full transaction history is often better kept in an archive.
- Cleanse. Remove duplicates, fix inconsistent units and close out obsolete items.
- Map. Match old fields and codes to ERPNext’s structure, including custom fields.
- Trial load. Load into the test environment, check it, fix it and repeat.
- Reconcile. Confirm stock values and balances match your old system before go-live.
What affects an ERPNext implementation timeline?
There is no standard timeline, but these factors drive it most:
- The number of modules in scope, such as accounting only versus stock, manufacturing and projects
- How much customisation and how many custom doctypes you need
- The number and complexity of integrations
- Data volume and quality
- Number of entities, warehouses and currencies
- How available your staff are for workshops, testing and sign-off
- Training needs and how many users go live at once
A phased rollout, starting with core finance and stock and then adding modules, often reduces risk for small and medium businesses.
What ongoing support and upgrades does ERPNext need?
ERPNext has major version releases, along with frequent minor updates. Staying current gives you fixes and new features, but every upgrade needs a plan:
- Test the new version against your customisations in a staging environment
- Check custom apps and scripts for changes in the framework
- Back up before every upgrade and confirm restores work
- Schedule upgrades outside busy periods such as end of financial year
Beyond upgrades, expect ongoing user support, new reports, workflow tweaks, user changes and performance monitoring. Loginet’s in-house team handles ERPNext implementation, customisation, hosting and support, so the people who built your system also look after it.
Frequently asked questions
Is ERPNext free?
The software is open source with no licence fees for the software itself. You still pay for hosting, implementation, customisation, training and support, which make up most of the total cost.
Can ERPNext data be kept in Australia?
Yes, if you self-host. On AWS or Azure you can choose an Australian region. With a managed service, check where the provider stores your data.
Will customisations break when ERPNext is upgraded?
They can if they change core code. Keeping changes in custom fields, scripts and separate custom apps greatly reduces upgrade risk, and testing in staging catches the rest.
Does ERPNext handle Australian GST?
ERPNext can be configured with Australian tax templates for GST. Check BAS reporting and payroll needs during discovery, because they may need extra setup or integration.
Can we move from spreadsheets or accounting software to ERPNext?
Yes. Most projects start that way. We cleanse, map and trial-load your data, then reconcile balances before go-live.
Do we need a developer to customise ERPNext?
Not always. Many changes, such as fields, workflows and print formats, are made through the interface. Scripts, integrations and custom apps need development skills.
Ready to deploy ERPNext?
Whether you want ERPNext on AWS, Azure or your own servers, our team can design, customise and support it. Book a free ERP discovery session to review your processes, and see our ERP solutions for the wider picture.
