How we run it
An implementation starts from the target picture — usually the scoping document — and moves in slices. Base configuration and master data first, then one business area at a time into productive use: sales, then stock, then accounting, in the order your business dictates. Each slice gets tested by the people who will live in it, on your data, before it goes live.
The point of slicing is risk. A go-live that covers everything at once has one date on which everything can fail. A go-live per area has small dates, each with a way back.
Data migration
Master data — partners, products, price lists, open items — moves completely. Historical documents move as far as they earn their place: open orders yes, five years of closed invoices usually as an archive rather than as live records. The dirty secret of every migration is data quality, so cleaning happens before import, in your old system, where errors are still recognisable.
The German and Swiss part
DATEV export to the tax adviser, e-invoicing, Swiss VAT and QR-bill where a Swiss entity is involved, and the fiscal requirements at the till where retail is. These are configuration topics with sharp edges — solved problems, but only for someone who has cut themselves on them before.
The phases
From target picture to stable operation
Foundation
companies, users, rights, chart of accounts, master data in.
First slice live
the area with the biggest pain goes productive first.
Slice by slice
each area configured, tested by key users on real data, then switched.
Stabilisation
four to six weeks with short reaction paths, then the handover into operations.
Asked in most first meetings
How long does an implementation take?
A single company with standard processes: months, not weeks. A group with several entities, integrations and data history: quarters. Anyone naming a number before scoping is guessing — the honest answer arrives with the target picture, as a range with reasons.
Can we keep working during the switch?
Yes — that is what slicing is for. The old system stays in charge of an area until its slice goes live. What we avoid is running both systems for the same area in parallel for long; double entry is where data quality goes to die.
Do you take over projects that are already running?
Yes. It starts with a short review of what exists — configuration, custom code, data — and an honest note on what to keep. Sometimes the answer is "more than you fear"; occasionally it is "less than you hope".
Community or Enterprise?
Both are real options and we run both. Enterprise brings the German localisation with TSE at the till, hosted upgrades and several apps that matter in practice. Community carries surprisingly far when the requirements allow it. The scoping settles this per case, not ideology.
Get in touch
Tell us what isn't working
Send a short description of where your processes hurt. You'll get a reply from the person who would do the work, not a sales team.