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.

Häufig gestellte Fragen

How long does a first ERP implementation take when moving from a self-built Excel/Access solution?

With clearly documented requirements, a committed project team and manageable data volumes, you should expect around four to nine months, while a mid-sized first-time project with more complex processes tends to take six to twelve months. The majority of this time is spent not on the actual software installation but on requirements clarification, data cleansing and training. A lean cloud entry such as Lexware or Sage 50 can often be implemented in two to four months, whereas a classic mid-market solution such as Sage 100 or Microsoft Dynamics 365 Business Central usually takes six to ten months. The actual duration depends heavily on process complexity, data quality and the availability of internal key people.

How do I know that Excel and Access are no longer enough and an ERP makes sense?

Typical warning signs are diverging file versions, the daily question “Who has the current spreadsheet?”, and systematic transfer errors between lists maintained in parallel. As a rough guide, manual spreadsheet workflows reach their breaking point at around ten to fifteen employees or several thousand documents per year. More decisive than sheer company size, however, is process complexity: as soon as the manual maintenance effort blocks day-to-day business, operations depend on individual people, or additional sales channels are added, the benefits of an integrated system outweigh the costs. A key risk is dependence on individuals, when only one person knows how a complex spreadsheet construct works.

Is a self-built Excel/Access solution even GoBD-compliant, or does bookkeeping force me into an ERP?

Excel and Access solutions generally do not reliably meet the GoBD requirement of immutability, because entries can be overwritten or deleted at any time without any logging. The GoBD require that tax-relevant records be kept in a traceable, complete, correct, timely, orderly and unalterable manner, and procedural documentation (Verfahrensdokumentation) is required for every system in use. A spreadsheet can at best be secured with additional versioning, logging and storage in an audit-proof archive or document management system, which however increases the effort considerably. An ERP system typically covers these requirements out of the box, including audit-proof posting locks and change logs, which is why growing compliance obligations are a frequent trigger for the switch.

What does a first professional ERP cost for a small to medium-sized company?

The total cost of a first implementation covers the licence, implementation, data migration, training and the hypercare phase after go-live, and differs greatly depending on the target system. A lean entry with Lexware or Sage 50 sits roughly in the range of EUR 10,000 to 40,000, a cloud mid-market ERP such as Weclapp or Xentral more in the range of EUR 30,000 to 100,000. For a classic solution such as Sage 100 or Microsoft Dynamics 365 Business Central in an SME environment, EUR 80,000 to around 300,000 is realistic, while a partner-led Odoo implementation can range from a low five-figure amount up to this bracket depending on module scope and depth of customisation. On top of these one-off costs come ongoing licence and maintenance fees depending on the number of users; all figures are indicative values and are no substitute for an individual quote.

Why is data migration from Excel and Access so often underestimated?

In practice, spreadsheet data is often of poor quality: numbers are formatted as text, spellings are inconsistent, and there are duplicates, dead records and missing mandatory fields. An ERP implementation acts like an X-ray machine for such data errors, because validation rules and mandatory fields in the new system immediately expose inconsistencies that previously went unnoticed. According to industry figures, around three quarters of data migration projects fail to stay within their original time or budget frame, which is why cleansing should take place before the first migration run and often takes four to eight weeks. It also makes sense to focus on active master data, open transactions and legally relevant information instead of migrating all legacy data.

Should I choose cloud or on-premises for my first ERP, and can Excel keep running in parallel?

For first-time implementations, the cloud is usually the obvious choice because it requires lower upfront investment, needs no in-house server maintenance and applies updates automatically. On-premises is more worthwhile for very specific requirements around data sovereignty or depth of customisation, which however add extra complexity to a first project. Excel and Access can temporarily continue as a read-only archive during the transition, but should not be maintained permanently in parallel with the ERP, as data consistency problems would otherwise arise again. Excel remains useful for evaluations and ad-hoc analyses, for example complemented by native ERP reports or business intelligence tools such as Power BI.