Migrate your Xentral ERP data
German cloud ERP built for e-commerce and B2B SMEs. Connects order processing, inventory, shipping, and accounting with a built-in middleware layer.
In its favor
Why people choose Xentral ERP
The signal that keeps Xentral ERP on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Fast implementation timelines for e-commerce teams — Lieblingsstück shipped customer orders in 18 days; PetRhein went live in 6 weeks, a fraction of typical ERP timelines.
Built-in Xentral Connect middleware enables code-free integrations with Shopify, Shopware, eBay, Amazon, and niche marketplaces without third-party iPaaS tools.
Unlimited user pricing removes headcount-based cost friction as teams grow, particularly valued by scaling SMBs adding multiple departments.
German and EU server hosting addresses data residency requirements for DACH-region businesses operating under GDPR compliance.
Continuous feature releases with an active public roadmap give customers visibility into planned capabilities and upcoming integrations.
Non-intuitive interface requires significant user training and creates friction during onboarding, especially for non-technical staff unfamiliar with ERP workflows.
Steep learning curve for complex features like production planning, multi-warehouse stock rules, and advanced accounting workflows leads to underutilisation of the platform.
Limited customisation compared to open-source alternatives — businesses with highly specific industry workflows eventually outgrow the platform's standard configuration options.
Support quality inconsistent — some users report slow ticket resolution and difficulty reaching senior technical engineers for complex configuration issues.
Reasons to switch
Why people leave Xentral ERP
The recurring reasons buyers give for replacing Xentral ERP. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Xentral ERP 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
Xentral ERP pricing overview
Xentral prices on a per-month model with all tiers offering unlimited users. Business and Pro tiers include 1,500 orders per month with €0.20 overage charges. Annual billing provides at least 10% savings versus monthly payments. The platform also offers Assisted Onboarding and Partner Onboarding add-ons as separate paid services.
Starter
Tier 1 of 3
€239/month
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Xentral ERP's schedule — see our quote-based pricing →
What gets migrated
Xentral ERP object support
Object-by-object support for Xentral ERP migrations. Per-pair details surface during scoping.
Addresses (Customers and Vendors)
Fully supportedXentral stores address records as a unified Address object used for both customers and vendors. We map this 1:1 and preserve custom Address fields configured in System Settings. Tax IDs and payment terms carry over as standard properties.
Articles (Products and Items)
Fully supportedArticles are Xentral's product master data object, supporting custom fields, multilingual labels, and item-specific pricing rules. We export Articles with all configured custom fields and preserve the article number as the primary key for downstream mapping.
Sales Orders
Fully supportedSales Orders in Xentral include line items, status, assigned warehouse, and shipping information. We preserve the original order number, creation date, and all document associations (invoices, delivery notes) at migration time.
Purchase Orders
Fully supportedPurchase Orders capture procurement records with vendor assignments, expected delivery dates, and received quantities. We map open and closed PO records, preserving the po_number field and linking them to their corresponding incoming goods records.
Invoices (Outgoing and Incoming)
Mapping requiredXentral generates both AR and AP invoices as document objects. We preserve document numbers, dates, and amounts. Multi-currency invoices require exchange rate mapping at the destination. PDF attachments are exported as binary blobs alongside the record.
Inventory and Warehouse Records
Mapping requiredStock levels, warehouse assignments, and batch/serial information are stored per Article. Real-time stock snapshots during migration require a freeze period. Batch tracking fields vary by warehouse configuration and may need custom mapping logic.
Financial Records and Chart of Accounts
Mapping requiredXentral's accounting module stores the chart of accounts, journal entries, and bank account connections. We map account codes and names, but tax code configurations and cost centre assignments must be validated against the destination's accounting rules.
Projects
Mapping requiredProjects in Xentral can be linked to orders, invoices, and custom fields. We export project records with their assigned custom fields, but project-level task dependencies and time entries require separate mapping review.
Custom Fields (Articles, Addresses, Projects)
Mapping requiredXentral supports custom fields for Articles, Addresses, and Projects only. Custom Object creation is not a native feature. We export custom field values as properties, but the field definitions themselves must be manually re-created at the destination.
Documents (Delivery Notes, Credit Notes)
Mapping requiredDelivery notes and credit memos are document-type objects tied to parent orders or invoices. We preserve the document hierarchy during migration. PDF rendering of documents is exported separately from structured data.
Workflows (Xentral Flows)
Not in this platformWorkflows configured in Xentral Flows are automation rules stored in the Xentral Connect middleware layer. These are not exposed via the standard REST API and cannot be exported. We document which workflows were active and provide a requirements spec for re-implementation at the destination.
Attachments
Fully supportedFile attachments linked to orders, articles, and addresses are accessible via the API and can be downloaded and re-uploaded to the destination. We preserve the original filename and association during migration.
| Object | Support | Notes |
|---|---|---|
| Addresses (Customers and Vendors) | Fully supported | Xentral stores address records as a unified Address object used for both customers and vendors. We map this 1:1 and preserve custom Address fields configured in System Settings. Tax IDs and payment terms carry over as standard properties. |
| Articles (Products and Items) | Fully supported | Articles are Xentral's product master data object, supporting custom fields, multilingual labels, and item-specific pricing rules. We export Articles with all configured custom fields and preserve the article number as the primary key for downstream mapping. |
| Sales Orders | Fully supported | Sales Orders in Xentral include line items, status, assigned warehouse, and shipping information. We preserve the original order number, creation date, and all document associations (invoices, delivery notes) at migration time. |
| Purchase Orders | Fully supported | Purchase Orders capture procurement records with vendor assignments, expected delivery dates, and received quantities. We map open and closed PO records, preserving the po_number field and linking them to their corresponding incoming goods records. |
| Invoices (Outgoing and Incoming) | Mapping required | Xentral generates both AR and AP invoices as document objects. We preserve document numbers, dates, and amounts. Multi-currency invoices require exchange rate mapping at the destination. PDF attachments are exported as binary blobs alongside the record. |
| Inventory and Warehouse Records | Mapping required | Stock levels, warehouse assignments, and batch/serial information are stored per Article. Real-time stock snapshots during migration require a freeze period. Batch tracking fields vary by warehouse configuration and may need custom mapping logic. |
| Financial Records and Chart of Accounts | Mapping required | Xentral's accounting module stores the chart of accounts, journal entries, and bank account connections. We map account codes and names, but tax code configurations and cost centre assignments must be validated against the destination's accounting rules. |
| Projects | Mapping required | Projects in Xentral can be linked to orders, invoices, and custom fields. We export project records with their assigned custom fields, but project-level task dependencies and time entries require separate mapping review. |
| Custom Fields (Articles, Addresses, Projects) | Mapping required | Xentral supports custom fields for Articles, Addresses, and Projects only. Custom Object creation is not a native feature. We export custom field values as properties, but the field definitions themselves must be manually re-created at the destination. |
| Documents (Delivery Notes, Credit Notes) | Mapping required | Delivery notes and credit memos are document-type objects tied to parent orders or invoices. We preserve the document hierarchy during migration. PDF rendering of documents is exported separately from structured data. |
| Workflows (Xentral Flows) | Not in this platform | Workflows configured in Xentral Flows are automation rules stored in the Xentral Connect middleware layer. These are not exposed via the standard REST API and cannot be exported. We document which workflows were active and provide a requirements spec for re-implementation at the destination. |
| Attachments | Fully supported | File attachments linked to orders, articles, and addresses are accessible via the API and can be downloaded and re-uploaded to the destination. We preserve the original filename and association during migration. |
Gotchas
What to watch for in Xentral ERP migrations
Issues we've hit on past Xentral ERP migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Xentral Flows workflows are not exported via API
CSV export requires mandatory masking character selection
Custom fields limited to three object types
Order volume limits create billing surprises on Business tier
API rate limits are documented but not fully public
| Severity | Issue |
|---|---|
| High | Xentral Flows workflows are not exported via API |
| Medium | CSV export requires mandatory masking character selection |
| Medium | Custom fields limited to three object types |
| Medium | Order volume limits create billing surprises on Business tier |
| Low | API rate limits are documented but not fully public |
Leaving Xentral ERP?
Where Xentral ERP customers move next
6 destinations Xentral ERP can migrate to.
How a Xentral ERP migration works
Four steps, Xentral ERP-specific
Connect
OAuth 2.0 into Xentral ERP. Scopes limited to read-only on the data we move.
Map
We translate Xentral ERP-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Xentral ERP quirks before production.
Migrate
Full migration with Xentral ERP rate-limit handling. Rollback available throughout.
FAQ
Xentral ERP migration FAQ
Answers to the questions buyers ask most during Xentral ERP migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Xentral ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Xentral ERP.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Xentral ERP setup and destination — written quote back within a business day.