Switching from Lexware to a Mid-Market ERP

Lexware (Haufe Group) serves the German SMB segment with popular products for bookkeeping, invoicing, payroll and small-business operations. Many German SMBs operate Lexware successfully through their formative years. As organisations grow beyond 20-30 employees with broader operational complexity (inventory, manufacturing, multi-entity), they outgrow Lexware's functional scope and migrate to mid-market ERP. The switch is a meaningful step up in system complexity and cost — one of the most-consequential single technology decisions in an SMB's growth journey.

Migration drivers

Three classical drivers. (1) Inventory and order complexity: Lexware handles basic invoicing well but struggles with multi-warehouse, complex pricing, batch tracking, configurable products. Growing operations hit these limits. (2) Manufacturing or service-business complexity: Lexware lacks substantial production-planning, project-accounting or service-management capabilities. Manufacturing or service-focused growth justifies mid-market ERP. (3) Multi-entity or international operations: subsidiary structures, foreign operations or multi-currency needs exceed Lexware's scope. When not yet: stable SMB operations under 20 employees with simple invoicing, no inventory complexity. Lexware serves these well at very competitive TCO; premature migration to mid-market ERP rarely pays back.

Mid-market ERP options

For Lexware-graduating SMBs in DACH, four products dominate the evaluation short-list. Microsoft Dynamics 365 Business Central: broadest mid-market coverage, strong DACH partner network, Microsoft 365 integration, cloud-native. The most-frequent Lexware-upgrade target. weclapp: DACH-built cloud-native ERP, B2B-strong, faster deployment than Business Central. Suits e-commerce-and-B2B operations. Sage 50 Connected or Sage 100: established mid-market platforms with mature German configuration. Sage 50 Connected fits smaller migrations; Sage 100 fits larger. Xentral: e-commerce-focused cloud-native ERP, dominant in DACH DTC and online retail. Suits online-business growth. Other: SAP Business One (smaller, Mid-Market-focused SAP), JTL-Wawi (e-commerce-focused mid-market). The right choice depends on industry, growth trajectory and IT stack preferences.

Migration methodology

The migration from Lexware is conceptually straightforward but operationally demanding. (1) Vendor selection: 3-6 month evaluation including demos, references and contract negotiation. Decisive partner choice matters as much as product choice. (2) Master-data export and cleanup: Lexware-exported customers, suppliers, items reviewed and cleansed before import. (3) Chart-of-accounts setup: SKR 03 or SKR 04 configured in the new ERP, mapped from Lexware. (4) Open-transaction migration: open AP, AR, inventory, POs at cutover. Historical data typically remains in Lexware for audit access. (5) Process design and training: users learn substantially different workflow from Lexware. Training investment matters. Implementation duration: 4-9 months typical for SMB-to-mid-market 20-80 user migrations. Cost: 50,000-300,000 EUR including implementation, first-year subscription and training. Migration TCO over 5 years: 300,000-1,500,000 EUR.

Practical considerations

Three patterns for successful Lexware-to-mid-market migrations. (1) Don't over-buy: the temptation to leapfrog directly to enterprise ERP (SAP S/4HANA, Oracle Cloud ERP) almost always backfires for SMBs. Stay in the mid-market tier; revisit enterprise ERP later when scale truly justifies it. (2) Maintain DATEV connection: most German SMBs work closely with a Steuerberater on DATEV. The new ERP must integrate with DATEV (CSV export or DATEVconnect API). Verify this during vendor selection. (3) Manage the change pace: SMBs without prior ERP experience face material change shock. Plan thorough training, hyper-care support post-go-live and conservative scope. Companies that try to transform too much in one project consistently produce implementation pain.

Long-term considerations

Three long-term considerations beyond the migration project. (1) Ongoing TCO accumulation: subscription costs accumulate. A mid-market ERP at 100-180 EUR per user per month for 30 users runs 36,000-65,000 EUR per year — substantially above Lexware operating cost. Plan budget accordingly. (2) Continuous system evolution: cloud ERPs receive regular updates with new features and occasional disruptions. Build the operational discipline for ongoing change — training updates, regression testing, change communication. (3) Talent and skills: ERP-bearing operations need internal capability for ongoing support, configuration changes, integration management. SMBs graduating from Lexware often underestimate this need. Plan for ERP-skilled internal staff or strong partner support relationship as part of the long-term operating model. The migration is a project; running the new ERP is an ongoing operational commitment.

Frequently Asked Questions

Can we keep Lexware Lohn after switching the ERP?

Yes. Lexware Lohn operates independently of the operational ERP and continues regardless of the ERP choice. The payroll-to-ERP integration reconfigures for the new ERP. Many German SMBs keep Lexware Lohn (or DATEV Lohn) for many years after migrating the operational ERP.

Is cloud or on-premises mid-market ERP right for SMBs?

Cloud almost always wins for SMBs. Lower upfront investment, faster deployment, vendor-managed operations, automatic upgrades. The cloud-cost accumulation over years matches but does not exceed the on-premises infrastructure-plus-operations cost for SMB scale. On-premises remains valid only for specific regulated industries or unusual data-sovereignty needs.

How big is too big for Lexware?

Typical thresholds: above 15-20 employees with inventory, above 30 employees in service operations, above 50 employees in any case. Specific symptoms of outgrowing Lexware: Excel substitution for missing ERP features, manual cross-system reconciliation, inability to produce consolidated reporting across entities. When these symptoms appear, ERP evaluation should start.