From Excel to First ERP

Many German SMBs operate for years on a patchwork of Excel spreadsheets, simple accounting software (Lexware, DATEV) and manual processes. At some point, the patchwork breaks — operational complexity outgrows what Excel can manage, errors multiply, growth becomes painful. The transition to a first real ERP is one of the most consequential single technology decisions in an SMB's growth journey. This guide covers the signals that the transition is overdue, the typical selection process and what to expect during and after implementation.

Signals that the transition is overdue

• Spreadsheet sprawl — dozens of active Excel files with cross-references, version control issues, error-prone updates
• Duplicate data entry — same information entered repeatedly across systems (Excel for orders, accounting software for invoices, separate inventory tracker)
• Manual reconciliation pain — monthly close involves substantial manual matching across systems
• Reporting difficulty — management reports require manual data combination from multiple sources
• Customer-service friction — answering customer queries about order status, account balance, delivery requires searching multiple systems
• Inventory inaccuracy — stock-on-hand reports unreliable; periodic physical counts reveal large discrepancies
• Growth bottlenecks — the operational team cannot scale faster because each additional employee needs to learn manual processes
• Compliance friction — tax audits and Steuerberater interactions require manual document gathering

Readiness check

The transition is operationally demanding for organisations without prior ERP experience. Five readiness factors. (1) Executive commitment: the transition requires sustained leadership attention over 6-18 months. Casual sponsorship produces casual outcomes. (2) Internal capability: the organisation needs people who can act as key users, learn the system and bridge business-and-technology. Outsourcing everything to the implementation partner produces partner dependency that lasts for years. (3) Budget honesty: realistic 5-year cost expectations including implementation, subscription, ongoing-support. Underbudgeting produces compressed-scope projects that underdeliver. (4) Process documentation: current processes documented (even informally) so they can be mapped to the new system. Pure verbal-tradition processes resist clean implementation. (5) Change-management capacity: users need to learn substantially new ways of working. Training and adjustment require time and energy.

Vendor selection

SMB ERP selection differs from mid-market selection in scope and rigour. Realistic 4-6 month process: shorter than mid-market selections, focused on practical fit rather than exhaustive analysis. Demo-led evaluation: rather than long RFP, focus on hands-on demos of business scenarios. Partner-first thinking: the implementation partner often matters more than the specific product within a peer set. Reference-customer interviews: speak to comparable customers who completed similar transitions. Typical short-list: 3-4 vendors evaluated hands-on. DACH SMB common short-list: Microsoft Dynamics 365 Business Central, weclapp, Xentral, Sage 50 Connected. Specific industries shift the short-list (e.g., trade-heavy: JTL-Wawi; e-commerce: Xentral; service-heavy: weclapp).

Implementation patterns

SMB-first ERP implementations have characteristic patterns. Duration: typically 3-9 months from contract to go-live for 20-80 user operations. Compressing below 3 months risks too-thin implementation; extending beyond 9 months indicates scope problems. Method: fit-to-standard predominates — adopt the product's standard processes rather than customising. Customisation is expensive in absolute terms and especially expensive relative to SMB budget. Cost: typical total project cost for SMB first ERP: 50,000-300,000 EUR including implementation, first-year subscription, training and minor customisation. Phased rollout: many SMB implementations start with core financials and basic operations, with additional modules (advanced manufacturing, CRM, project business) added later as readiness develops. Post-go-live stabilisation: the first 3-6 months of operation involve continued partner support and frequent user-coaching. Productivity initially drops before recovering to higher steady-state.

After go-live: operating the ERP

The implementation is a project; running the ERP is an ongoing commitment. SMBs sometimes underestimate this. Internal-capability ownership: someone in the organisation must own ERP knowledge and capability. Without an internal owner, every issue becomes a partner-support ticket with substantial cost. Partner support relationship: most SMBs maintain a partner-support relationship for ongoing configuration changes, upgrade preparation, occasional development. Budget 5,000-30,000 EUR per year for partner support. Continuous user training: new employees need ERP training; existing employees benefit from refresher and advanced training. Build training into the operating model. Annual review and improvement: yearly review of how the ERP is being used — what is working, what could be better, what new functionality could deliver value. Without active review, the ERP operates at minimum-viable level over time.

Avoiding common SMB-ERP pitfalls

SMBs transitioning to ERP for the first time make several recurring mistakes. (1) Choosing on price alone: cheapest ERP option rarely produces best outcome. Implementation partner quality matters more than software price. (2) Replicating spreadsheets in the ERP: the temptation to recreate existing Excel workflows in the ERP defeats the purpose. The ERP's standard processes typically work better than home-grown spreadsheet logic. (3) Underestimating training: SMBs without prior ERP experience consistently allocate too little to training. Productivity drops post-go-live without solid training. (4) Insufficient key-user investment: SMBs sometimes try to operate without dedicated key users, relying entirely on the partner. The result is sustained partner-dependency and slow internal capability development. (5) Over-customisation to match legacy: customisation requests to make the ERP look like the old spreadsheets increase cost without improving outcomes.

Related Topics

• ERP selection
• ERP cost guide
• SaaS ERP