Migrate your iDempiere data
Community-driven, OSGi-based open-source ERP/CRM/SCM built on Java and PostgreSQL. Organizations pick it for zero licensing cost and deep customizability; they leave when they need vendor-backed support or a faster implementation path.
In its favor
Why people choose iDempiere
The signal that keeps iDempiere on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Zero licensing cost with enterprise-grade accounting, CRM, and SCM capabilities built on a proven PostgreSQL or Oracle stack.
Highly extensible through an OSGi plugin system that keeps custom code isolated from core, avoiding upgrade conflicts on the base application.
Multi-entity support lets organizations run multiple sets of books (separate legal entities or divisions) under a single login.
Active open-source community and broad international use mean the system is well-understood by regional implementors in many countries.
Cross-platform support (Linux, Windows, Mac) and Docker deployment options make it adaptable to existing infrastructure preferences.
Lack of a commercial vendor means support relies on community forums, which can be slow or inconsistent for urgent production issues.
Steep learning curve for non-developers: the platform blurs the line between an ERP and a development framework, making functional teams dependent on technical resources.
Limited official documentation compared to commercial ERPs, making initial configuration and customization time-consuming.
Customizations accumulate over time, creating upgrade friction when new iDempiere versions remove deprecated APIs or change core behaviors.
Self-hosting requirement means internal IT bears full responsibility for uptime, backups, and scaling—cost and complexity that some teams did not anticipate.
Reasons to switch
Why people leave iDempiere
The recurring reasons buyers give for replacing iDempiere. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where iDempiere fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
iDempiere pricing overview
iDempiere is free software with no licensing cost. All costs are infrastructure-related (servers, database licenses if Oracle is chosen, backup systems) plus optional paid support from third-party implementors. There are no tiers, user limits, or feature gates built into the software itself.
Community Support Add-on
Tier 1 of 1
Varies by provider
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on iDempiere's schedule — see our quote-based pricing →
What gets migrated
iDempiere object support
Object-by-object support for iDempiere migrations. Per-pair details surface during scoping.
Business Partners
Fully supportedBusiness Partners cover customers, vendors, and leads with full address, contact, and pricing-schema support. We export all BP records including location tabs and credit data via the database layer or REST API, preserving the BP group and type assignment.
Products
Fully supportedProducts include BOM structures, costing, and category assignments. We map product attributes, stocking settings, and configured variants. The plugin-based cost engine is preserved as long as cost records are included in the export scope.
Orders and Invoices
Fully supportedSales and purchase documents with header/line structures and payment schedules are fully migratable. We preserve the document status, tax treatment, and GL journal references. Lines are linked to the header via document number and line number.
Payments and Cash Management
Fully supportedPayment batches, cash journal entries, and bank statement mappings are exported with full allocation details. Open AP/AR records carry their payment terms and aging bucket assignments.
Projects and Resources
Fully supportedProject headers with phases, tasks, time entries, and milestone tracking are migratable. Resource assignments and project status are preserved. Custom project types defined in the Application Dictionary are mapped as custom fields.
Assets and Fixed Assets
Fully supportedFixed asset registers including depreciation schedules and insurance mappings are fully supported. We export the asset book, depreciation method, and service history tied to each asset record.
Accounting Schema and GL
Mapping requiredMultiple accounting schemas per tenant are supported, but the account structure dimensions (Legal Entity, Business Partner, Product, Location, etc.) must be recreated on the destination side. GL journal batches and historical entries require careful mapping of the posting date and schema assignment.
Custom Windows / Application Dictionary
Mapping requiredCustom windows created in the Application Dictionary are table-backed objects. We export the underlying table data and the AD registration metadata, but the visual form layout must be reapplied on the destination unless the same AD configuration is duplicated there.
Attachments and Archives
Mapping requiredAttachments stored in the database or filesystem are migratable via the Migrate Storage Provider plugin or direct file export. We detect the current provider at migration time and handle the corresponding extraction or re-import path.
Users, Roles, and Organizations
Mapping requiredUsers and role-based security assignments are migratable but require mapping of role-privilege records. Multi-org structures (Client and child Organizations) must be created in the correct hierarchy before user and BP records are imported.
Bank and Cash Accounts
Fully supportedBank accounts and cash journal accounts with currency and GL account mappings are fully migratable. Opening balances are preserved as GL journal entries in the target accounting schema.
Tax Codes and Categories
Fully supportedTax categories, rates, and validity windows are fully migratable. Tax jurisdiction assignments per location are preserved so the correct rates apply post-migration.
| Object | Support | Notes |
|---|---|---|
| Business Partners | Fully supported | Business Partners cover customers, vendors, and leads with full address, contact, and pricing-schema support. We export all BP records including location tabs and credit data via the database layer or REST API, preserving the BP group and type assignment. |
| Products | Fully supported | Products include BOM structures, costing, and category assignments. We map product attributes, stocking settings, and configured variants. The plugin-based cost engine is preserved as long as cost records are included in the export scope. |
| Orders and Invoices | Fully supported | Sales and purchase documents with header/line structures and payment schedules are fully migratable. We preserve the document status, tax treatment, and GL journal references. Lines are linked to the header via document number and line number. |
| Payments and Cash Management | Fully supported | Payment batches, cash journal entries, and bank statement mappings are exported with full allocation details. Open AP/AR records carry their payment terms and aging bucket assignments. |
| Projects and Resources | Fully supported | Project headers with phases, tasks, time entries, and milestone tracking are migratable. Resource assignments and project status are preserved. Custom project types defined in the Application Dictionary are mapped as custom fields. |
| Assets and Fixed Assets | Fully supported | Fixed asset registers including depreciation schedules and insurance mappings are fully supported. We export the asset book, depreciation method, and service history tied to each asset record. |
| Accounting Schema and GL | Mapping required | Multiple accounting schemas per tenant are supported, but the account structure dimensions (Legal Entity, Business Partner, Product, Location, etc.) must be recreated on the destination side. GL journal batches and historical entries require careful mapping of the posting date and schema assignment. |
| Custom Windows / Application Dictionary | Mapping required | Custom windows created in the Application Dictionary are table-backed objects. We export the underlying table data and the AD registration metadata, but the visual form layout must be reapplied on the destination unless the same AD configuration is duplicated there. |
| Attachments and Archives | Mapping required | Attachments stored in the database or filesystem are migratable via the Migrate Storage Provider plugin or direct file export. We detect the current provider at migration time and handle the corresponding extraction or re-import path. |
| Users, Roles, and Organizations | Mapping required | Users and role-based security assignments are migratable but require mapping of role-privilege records. Multi-org structures (Client and child Organizations) must be created in the correct hierarchy before user and BP records are imported. |
| Bank and Cash Accounts | Fully supported | Bank accounts and cash journal accounts with currency and GL account mappings are fully migratable. Opening balances are preserved as GL journal entries in the target accounting schema. |
| Tax Codes and Categories | Fully supported | Tax categories, rates, and validity windows are fully migratable. Tax jurisdiction assignments per location are preserved so the correct rates apply post-migration. |
Gotchas
What to watch for in iDempiere migrations
Issues we've hit on past iDempiere migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Plugin rebuild required after every major version upgrade
Multi-org hierarchy must be recreated before user and master data
Attachment storage provider split between database and filesystem
Deprecated AD_Sequence_No.CalendarYearMonth renamed in v13
Windows server deployment carries documented server-side risks
| Severity | Issue |
|---|---|
| High | Plugin rebuild required after every major version upgrade |
| High | Multi-org hierarchy must be recreated before user and master data |
| Medium | Attachment storage provider split between database and filesystem |
| Medium | Deprecated AD_Sequence_No.CalendarYearMonth renamed in v13 |
| Low | Windows server deployment carries documented server-side risks |
Leaving iDempiere?
Where iDempiere customers move next
6 destinations iDempiere can migrate to.
How a iDempiere migration works
Four steps, iDempiere-specific
Connect
Session-based cookie authentication; REST API supports OAuth 2.0 with Swagger UI for endpoint discovery into iDempiere. Scopes limited to read-only on the data we move.
Map
We translate iDempiere-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate iDempiere quirks before production.
Migrate
Full migration with iDempiere rate-limit handling. Rollback available throughout.
FAQ
iDempiere migration FAQ
Answers to the questions buyers ask most during iDempiere migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your iDempiere migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate iDempiere.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your iDempiere setup and destination — written quote back within a business day.