Two decisions cause most of the pain
First, choosing a closed system for your core records — customers, orders, finance. If you cannot get data out programmatically, every future automation is either impossible or expensive.
Second, letting each department choose independently. It feels empowering and produces five systems that do not talk, with the same customer represented five ways.
The one question to ask about every tool
“Can I get all of my data out, in a structured format, without asking you?” If the answer is anything other than a straightforward yes, weigh that heavily. It determines what you can do later and what leaving would cost.
A published API and a full export are not luxuries for a small business. They are what makes the next five years possible without a migration project.
A stack shape that works
- One system of record per entity. One place that owns customers, one that owns finance. Everything else reads from those.
- Accounting: mainstream, well-integrated, whatever your accountant supports.
- CRM: chosen for how your sales actually work rather than for feature count.
- Operations: the tool specific to your industry — this is where specialism beats breadth.
- Communication and documents: one suite, not several.
- A thin integration layer once you pass three or four systems.
All-in-one or best of breed
All-in-one suites reduce integration work and are usually mediocre at the thing your business actually does. Best of breed gives you excellent tools and an integration problem.
The pragmatic answer for most small businesses: an all-in-one for the generic functions, and one specialist tool for the operation that is your actual business. Integrate those two properly and ignore the rest.
Signals it is time to change something
- People maintain a spreadsheet to work around the system
- The same data is typed into two places routinely
- You cannot answer a basic business question without a manual export
- Licence cost is rising faster than headcount or revenue
- The vendor has stopped shipping meaningful updates
One of these is tolerable. Three at once means the cost of staying is now higher than the cost of moving.
Changing systems without losing the business
Never change two core systems at once. Migrate outside your busy season. Keep the old system readable for months. And profile the data before committing to a date, because the surprises are always in the data.
Most re-platforming disasters come from optimism about how clean the existing data is. A week of profiling prevents most of them.