09/04/2026
I keep seeing conversations where a bookkeeper takes on a new client, discovers the client uses accounting software they aren't familiar with, and the immediate solution is:
^We need to move them to the platform I use."
That concerns me.
A client's accounting system should not be changed simply because their new bookkeeper or accountant is more comfortable using something else.
A system migration should have a legitimate business case behind it.
Does the existing system no longer support the business?
Are there reporting limitations?
Has the organization outgrown it?
Are there integration, scalability, control, or operational issues?
Will another platform actually provide enough benefit to justify the cost, disruption, and risk of migrating?
And migration itself isn't just pushing a button.
Before moving financial data, the existing records need to be reviewed and validated. Historical information needs to be protected. Backups and readable records need to be retained. Mapping needs to be evaluated. Balances need to be reconciled and validated before and after conversion.
Most importantly, "the recommendation should be made in the client's best interest."
If the client's existing system meets their needs and the only problem is that you don't know how to use it, that isn't necessarily a software problem.
Sometimes the right professional decision is to learn the system.
And sometimes it's to recognize the engagement isn't the right fit and refer the client to someone who already has that expertise.
"Your client's accounting infrastructure should not be redesigned around your comfort zone."
