ERPNext Implementation Guide: Setup Decisions, Data Import and Go-Live

ERPNext's setup wizard gets you to a working system in minutes. That speed is useful and dangerous: the decisions it makes quietly on your behalf are the ones that are hardest to change later. This guide covers the choices that determine whether an ERPNext implementation produces a system people trust. For the general method that applies to any platform, see our ERP implementation guide.

1. Make the irreversible decisions deliberately

A few settings shape every transaction that follows. Decide them with finance and operations in the room, and write down why.

Company structure. One company or several? Separate legal entities usually need separate companies; branches usually do not and are better handled with cost centres or accounting dimensions.

Chart of accounts. The wizard offers a standard template per country. Review it against how you report today and how your accountant files returns. Restructuring accounts after a year of transactions is painful.

Stock valuation. ERPNext supports FIFO and moving average, set per item or as a default. Perpetual inventory is enabled per company. Changing valuation after stock transactions exist means reposting.

Item design. Decide naming, item groups, templates versus variants, stock and purchase UOMs, and which items need batch or serial tracking. Weak item design causes more post-go-live friction than anything else.

Warehouses. Plan the warehouse tree for how stock really moves, including work-in-progress, transit and rejected warehouses if you manufacture or ship between sites.

2. Phase the rollout

Do not try to go live with everything. A sensible first phase covers:

• Selling: quotation, sales order, delivery note, sales invoice
• Buying: material request, purchase order, purchase receipt, purchase invoice
• Stock: transfers, reconciliation, reorder levels
• Accounting: payments, bank reconciliation, taxes, period close

Manufacturing, Frappe HR and payroll, projects, assets and portals follow in later phases, once the core flow is stable.

3. Configure taxes properly

ERPNext uses sales and purchase tax templates, item tax templates and tax categories. Get these right before go-live, test them with real invoices, and have your accountant sign off. In India, install and configure the India Compliance app — see our ERPNext GST guide.

4. Prepare and import data

ERPNext's Data Import tool loads CSV or Excel files into any DocType, inserting new records or updating existing ones. It is approachable, which makes it tempting to load data straight from the old system. Don't.

1. Profile and clean. Remove duplicates, inactive items and customers, and inconsistent units.
2. Load masters. Customers, suppliers, items, price lists, BOMs.
3. Load open documents. Pending sales and purchase orders, unpaid invoices.
4. Load opening balances. Stock by warehouse and batch via stock reconciliation, account balances via an opening journal entry.

Rehearse the full import at least twice on a staging site and reconcile stock value and the trial balance against the old system. Our ERP data migration guide covers the method in more depth.

5. Keep customisation disciplined

Use the lightest tool that works: settings first, then Customize Form and custom fields, then workflows and print formats, and only then scripts or a custom app. Export customisations as fixtures in a custom app so they live in Git. See ERPNext customisation: what to configure, script or build.

6. Set permissions before users arrive

ERPNext's role-based permissions are granular. Create roles that match real jobs, restrict who can submit, cancel and amend financial documents, and use user permissions to limit access by company or warehouse where needed. Fixing permissions after go-live means taking access away, which users notice.

7. Train on real work

Train each role on the transactions they will actually perform, using your own items and customers on the staging site. A one-page cheat sheet per role beats a long generic manual.

8. Cut over and support

Pick a period boundary, freeze the old system, run the final import, reconcile, and go. Plan daily check-ins for the first weeks and close support through the first month-end close. Most issues surface in the first period closing, not on day one.

Getting help

Many teams implement ERPNext themselves successfully. If you want experienced help on the decisions that matter most — or on the whole project — see our ERPNext implementation services.