Migrate your metasfresh data
Open-source ERP for SMEs with no license fees, Docker-based self-hosting, and a heavily customizable data model rooted in ADempiere. Best fits companies with technical capacity to manage their own infrastructure.
In its favor
Why people choose metasfresh
The signal that keeps metasfresh on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Zero license cost as GPLv2/GPLv3 open-source software makes metasfresh financially attractive to SMEs that want ERP capabilities without annual per-seat fees.
Docker-based deployment allows installation on Kubernetes, dedicated servers, or cloud VMs, giving teams full control over their infrastructure and data residency.
Source code access means metasfresh can be customized to look and behave like major commercial ERP systems without licensing fees that cost thousands annually.
The platform includes DATEV accounting export natively, making it straightforward for DACH-region companies to hand off financial data to tax advisors.
Active community and 60,000+ GitHub commits demonstrate reliable ongoing development, reducing the risk of using abandoned open-source ERP software.
Steep learning curve when configuring the system for industries outside its default food and beverage workflows, requiring significant consultant time.
Installation and build times can be slow, with users reporting the application sometimes hanging during Docker image builds.
Not a turnkey solution — companies without technical staff or ERP experience may struggle to configure and maintain metasfresh without external help.
Self-hosting responsibility means no vendor-managed updates, backups, or SLA, which some companies prefer to outsource to a SaaS provider.
Reasons to switch
Why people leave metasfresh
The recurring reasons buyers give for replacing metasfresh. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where metasfresh 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
metasfresh pricing overview
metasfresh is fundamentally free software with no per-user or per-company license cost. The primary cost is infrastructure for self-hosting or the managed cloud tier at €24 per month. Paid support contracts and implementation consulting are available separately through metas GmbH and its partner network.
Open Source (Self-Hosted)
Tier 1 of 2
Free
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on metasfresh's schedule — see our quote-based pricing →
What gets migrated
metasfresh object support
Object-by-object support for metasfresh migrations. Per-pair details surface during scoping.
Business Partners (Customers and Vendors)
Fully supportedBusiness Partners are first-class objects with address, contact, and financial relationship data. We map them 1:1 using metasfresh's partner export format, preserving vendor vs customer classification and bank account details.
Products
Fully supportedProducts include BOMs (bill of materials), categories, and pricing. metasfresh provides an XLS export for all product specifications. We read product data from the M_Product and related tables to ensure full attribute fidelity.
Sales and Purchase Orders
Mapping requiredOrders are stored across multiple tables including C_Order and its lines. Header-to-line relationships and document status must be preserved during migration. We reconstruct the full document tree from the database schema.
Invoices
Mapping requiredInvoices reference Business Partners and Orders. metasfresh supports both AR and AP invoices. We map invoice headers and line items separately, preserving the allocation to the originating order where it exists.
Pricing Systems and Price Lists
Mapping requiredPricing is organized into systems containing multiple price list versions with effective dates. We export the full pricing hierarchy and map it to the destination, handling versioned pricing as of specific dates.
BOMs (Bill of Materials)
Mapping requiredManufacturing BOMs define product component relationships and quantities. Stored in pp_product_bom tables. We preserve the bill structure and link components to their Product records in the destination.
Projects and Project Lines
Mapping requiredProjects in metasfresh have a header plus lines that track time, costs, and deliverables. We map project structure including phases and milestones, linking them to the owning Business Partner.
Bank Accounts and Payment Terms
Fully supportedBank accounts are stored per organization and linked to Business Partners. Payment terms (net 30, etc.) are reference data. Both export cleanly and map 1:1 to destination equivalents.
Tax Categories and Tax Codes
Fully supportedmetasfresh provides default tax categories that can be extended. Tax rates are tied to tax categories and geographic zones. We preserve the full tax configuration including effective date ranges.
Attachments and Documents
Not in this platformmetasfresh stores archived document PDFs and file attachments in the database as byte arrays or references to storage paths. These cannot be reliably extracted and re-imported without direct database access and file system navigation that falls outside standard migration tooling. We exclude attachments from the migration scope.
Complaints and Service Repairs
Mapping requiredCustomer complaints and repair workflows create service project records linked to returned products. We map the complaint header and related repair project, preserving the link back to the original Sales Order.
Custom Fields (AD_Column extensions)
Mapping requiredmetasfresh allows extending tables via the System Administrator role through Table and Column settings. Custom fields added by the customer require us to inspect the AD_Column metadata table to discover and include them in the migration export.
| Object | Support | Notes |
|---|---|---|
| Business Partners (Customers and Vendors) | Fully supported | Business Partners are first-class objects with address, contact, and financial relationship data. We map them 1:1 using metasfresh's partner export format, preserving vendor vs customer classification and bank account details. |
| Products | Fully supported | Products include BOMs (bill of materials), categories, and pricing. metasfresh provides an XLS export for all product specifications. We read product data from the M_Product and related tables to ensure full attribute fidelity. |
| Sales and Purchase Orders | Mapping required | Orders are stored across multiple tables including C_Order and its lines. Header-to-line relationships and document status must be preserved during migration. We reconstruct the full document tree from the database schema. |
| Invoices | Mapping required | Invoices reference Business Partners and Orders. metasfresh supports both AR and AP invoices. We map invoice headers and line items separately, preserving the allocation to the originating order where it exists. |
| Pricing Systems and Price Lists | Mapping required | Pricing is organized into systems containing multiple price list versions with effective dates. We export the full pricing hierarchy and map it to the destination, handling versioned pricing as of specific dates. |
| BOMs (Bill of Materials) | Mapping required | Manufacturing BOMs define product component relationships and quantities. Stored in pp_product_bom tables. We preserve the bill structure and link components to their Product records in the destination. |
| Projects and Project Lines | Mapping required | Projects in metasfresh have a header plus lines that track time, costs, and deliverables. We map project structure including phases and milestones, linking them to the owning Business Partner. |
| Bank Accounts and Payment Terms | Fully supported | Bank accounts are stored per organization and linked to Business Partners. Payment terms (net 30, etc.) are reference data. Both export cleanly and map 1:1 to destination equivalents. |
| Tax Categories and Tax Codes | Fully supported | metasfresh provides default tax categories that can be extended. Tax rates are tied to tax categories and geographic zones. We preserve the full tax configuration including effective date ranges. |
| Attachments and Documents | Not in this platform | metasfresh stores archived document PDFs and file attachments in the database as byte arrays or references to storage paths. These cannot be reliably extracted and re-imported without direct database access and file system navigation that falls outside standard migration tooling. We exclude attachments from the migration scope. |
| Complaints and Service Repairs | Mapping required | Customer complaints and repair workflows create service project records linked to returned products. We map the complaint header and related repair project, preserving the link back to the original Sales Order. |
| Custom Fields (AD_Column extensions) | Mapping required | metasfresh allows extending tables via the System Administrator role through Table and Column settings. Custom fields added by the customer require us to inspect the AD_Column metadata table to discover and include them in the migration export. |
Gotchas
What to watch for in metasfresh migrations
Issues we've hit on past metasfresh migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No well-documented public REST API for data migration
Attachment and archived document extraction is unreliable
BOM and manufacturing data requires deep schema knowledge
Custom fields discovered at runtime, not import time
| Severity | Issue |
|---|---|
| High | No well-documented public REST API for data migration |
| High | Attachment and archived document extraction is unreliable |
| Medium | BOM and manufacturing data requires deep schema knowledge |
| Medium | Custom fields discovered at runtime, not import time |
Leaving metasfresh?
Where metasfresh customers move next
6 destinations metasfresh can migrate to.
How a metasfresh migration works
Four steps, metasfresh-specific
Connect
Not publicly documented into metasfresh. Scopes limited to read-only on the data we move.
Map
We translate metasfresh-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate metasfresh quirks before production.
Migrate
Full migration with metasfresh rate-limit handling. Rollback available throughout.
FAQ
metasfresh migration FAQ
Answers to the questions buyers ask most during metasfresh migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your metasfresh migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate metasfresh.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your metasfresh setup and destination — written quote back within a business day.