Roadmap: Becoming an ERP Developer
A concrete path from wherever you are now to a working ERP developer, and then to senior.
The honest prerequisites
You need two skill sets, and most people only have one:
ENGINEERING BUSINESS
SQL and data modelling Accounting fundamentals
One programming language How a business actually operates
Debugging Process thinking
Testing discipline Communication with non-technical people
Version control Reading a financial statement
The scarcity is in the combination. There are many good developers and many good accountants. There are far fewer people who can do both, and that gap is the entire value proposition of an ERP developer.
Phase 0 — Foundations (1–3 months)
Skip what you already have.
Engineering
- SQL, properly. Joins, aggregation, window functions, CTEs, indexes, execution plans. You will write more SQL than anything else.
- Relational modelling. Normalisation, keys, constraints, referential integrity.
- One language. Python, C#, Java, or JavaScript — whichever aligns with the platform you’ll target.
- Git.
- The command line.
Business — the part people skip
- Double-entry bookkeeping. Non-negotiable. Read Double-Entry for Developers and then do exercises until posting entries is automatic.
- Read a real annual report. Balance sheet, P&L, cash flow, and the notes. Pick a manufacturer whose products you understand.
- Free courses: any introductory accounting course (Coursera, edX, Khan Academy, or a local university’s open materials). A dozen hours gets you most of the way.
Test of readiness: you can explain, without looking anything up, what happens in the accounts when a company buys inventory on credit, sells half of it, and the customer pays late.
Phase 1 — Pick a platform (decide, then commit)
| If you… | Start with |
|---|---|
| Know Python, want to learn free | Odoo or ERPNext |
| Know JavaScript | NetSuite |
| Know C#/.NET | Dynamics 365 Business Central (AL) or Acumatica |
| Want the highest ceiling and can invest 18 months | SAP |
| Want a niche with less competition | Infor, IFS, Epicor, QAD |
| Are in South Asia / Bangladesh | Odoo, ERPNext, or SAP B1 — where the local market is |
Then commit for at least two years. Shallow familiarity with five ERPs is worth less than depth in one. The domain concepts transfer; the platform skills do not.
The free-access reality
Odoo ✅ Fully free, install locally today
ERPNext ✅ Fully free, install locally today
NetSuite ✅ Free developer account
Business Central ✅ Free sandbox / Docker container
SAP ⚠️ BTP trial, ABAP developer edition, openSAP courses
Dynamics F&O ⚠️ Trial environments; a full dev VM usually needs an employer
Oracle Fusion ❌ Effectively requires an employer or partner
If you have no employer sponsoring you, start with Odoo or ERPNext. You can be genuinely productive within months, entirely for free.
Phase 2 — Learn the domain (3–6 months, in parallel)
Use this repo. The order that works:
1. Foundations (section 01) — what ERP is, the landscape
2. Core data model (section 02) — org structure, master data, documents
3. Finance (section 03) — the ledger. THE most important section
4. Order to cash (section 05) — the process everyone knows
5. Procure to pay (section 04) — the mirror
6. Inventory (section 04) — quantity and value
7. Your industry's module (06 or 07) — manufacturing, projects, or services
8. Architecture (section 08) — how it's built
9. Integration (section 09) — where you'll spend your career
Section 03 (Finance) is the one that separates ERP developers from application developers. Learn it properly. Everything posts to the ledger eventually.
Phase 3 — Build something real (2–4 months)
Reading isn’t enough. See Portfolio Projects for specifics. The minimum viable portfolio:
- A working ERP instance you configured yourself — a fictional company, real chart of accounts, real master data, and a complete order-to-cash and procure-to-pay cycle
- A custom extension — a report, a workflow, or a custom document type on your chosen platform
- An integration — pull data from an external API into the ERP, or push documents out
- Documentation of all three, published
The configured instance matters more than the code. It proves you understand the domain, which is what employers actually can’t teach quickly.
Phase 4 — Get the first job
Where the jobs are
1. Implementation partners / VARs ← the biggest entry point, and they train
2. System integrators (Accenture, Deloitte, Infosys, TCS, Capgemini)
3. End customers' in-house ERP teams
4. The vendors themselves
5. Freelance (Odoo/ERPNext — realistic after some experience, not before)
Partners and SIs hire juniors and train them. End customers usually want experience. Start with a partner.
What to emphasise
- Domain understanding, not just coding. In an interview, explaining why a goods receipt creates a GR/IR entry is worth more than any algorithm question.
- Your configured instance — demo it.
- Willingness to learn the functional side.
- Communication skills. ERP work is 40% talking to business people.
Realistic entry paths
a) Junior developer at a partner ← most common
b) Support analyst → developer ← learn the system, move sideways
c) Business analyst → techno-functional ← if you have domain background
d) Adjacent developer → ERP team ← internal move at a company running one
e) Freelance small implementations ← Odoo/ERPNext, needs self-marketing
Path (b) is underrated. Support roles are easier to enter, and a year in support teaches you the system better than a year of building.
Phase 5 — From junior to senior (2–4 years)
What actually moves you up:
| Do this | Not this |
|---|---|
| Attend functional workshops | Wait for specs |
| Learn the config layer of your product | Only write code |
| Ask “why does the business need this?” | Build exactly what’s written |
| Learn one module functionally, deeply | Stay purely technical |
| Volunteer for the month-end close | Avoid the stressful bits |
| Write the documentation | Skip it |
| Learn to estimate accurately | Guess |
| Present to business stakeholders | Stay behind the screen |
| Understand the licence and cost implications | Ignore commercials |
The single highest-leverage habit: sit in the functional workshops. The developers who understand the business become architects. The ones who only take specifications stay juniors, however good their code is.
Phase 6 — Senior and beyond
Senior Developer ──▶ Technical Lead ──▶ Technical Architect
──▶ Techno-functional ──▶ Solution Architect ──▶ Enterprise Architect
──▶ Integration Architect
──▶ Independent consultant
──▶ Product engineer at a vendor
──▶ Founder of a vertical ERP product
The techno-functional path pays best per unit of effort, because the combination is rare. Someone who can run the workshop, design the solution, and build it is worth roughly double someone who can only do one.
Realistic timelines
| Milestone | Time |
|---|---|
| Understand ERP concepts well enough to talk credibly | 3 months |
| Productive on Odoo / ERPNext / Business Central | 6–9 months |
| Productive on NetSuite | 6–9 months |
| Productive on SAP or Dynamics F&O | 12–18 months |
| Senior on any platform | 3–5 years |
| Architect | 6–10 years |
Compensation (indicative, varies enormously by region)
Relative signals rather than absolute numbers:
SAP developer highest of the mainstream platforms
Oracle Fusion/EBS close behind
Dynamics F&O strong
NetSuite solid, US-weighted
Dynamics BC solid, high volume of roles
Acumatica / Epicor solid, smaller market
Odoo / ERPNext lower rates, but the lowest barrier to entry and
the easiest path to independent consulting
Niche (QAD, Infor, IFS) high per hour, fewer opportunities
Contracting rates are typically 1.5–2.5× permanent equivalents, and ERP has one of the healthiest contract markets in software — because projects are finite and specialists are scarce.
The 12-month plan (if starting from a general dev background)
Month 1–2 Accounting fundamentals + SQL sharpening
Month 2–3 Install Odoo or ERPNext; use it as a business user;
read sections 01–03 of this repo
Month 3–5 Configure a full fictional company; run complete O2C and P2P cycles;
read sections 04–05
Month 5–7 Build custom modules: a report, a document type, a workflow;
read sections 08–09
Month 7–9 Build an integration; read sections 11–12
Month 9–10 Study the source code of the accounting and stock modules
Month 10–11 Publish the portfolio; write up what you built and why
Month 11–12 Apply — partners and SIs first
This is achievable alongside a full-time job at roughly 10 hours a week. The main risk is quitting at month 3, when the accounting is boring and nothing looks like progress yet.