Spreadsheet Clients vs Software Clients: Onboarding Two Different Bookkeeping Habits

15 September 2026·5 min read

Quick answer: A spreadsheet client and a software-native client are arriving from completely different habits, so one generic onboarding checklist will under-serve one of them every time. Spreadsheet clients need a gentler migration with reassurance built in; software clients need a tidy-up and consolidation, not a rebuild. Run two tracks. 📈

We've watched plenty of bookkeeping businesses hand every new client the exact same onboarding checklist — same welcome pack, same "please connect your bank feed" instructions, same week-one call script — regardless of whether that client just emailed through a decade of hand-built spreadsheets or already lives inside Xero with forty connected apps. It's efficient to run one process. It's also why one type of client always feels rushed and the other always feels babied 💖. They need different starting points, not different quality of service.

What most bookkeeping businesses get wrong

The mistake isn't a lack of process — most bookkeeping businesses have a perfectly good onboarding checklist. The mistake is assuming that checklist is client-agnostic. A spreadsheet client is often anxious about "losing" years of familiar data and doesn't know what a bank feed even is; treating them like a software client skips straight past that anxiety and loses trust in week one. A software-native client, on the other hand, gets bored and disengaged being walked through basics they already know, and starts wondering what they're paying for.

The Two-Track Onboarding Checklist

Track A — Spreadsheet clients:

Week 1: acknowledge the spreadsheet by name — "we've had a look through your tracker, it's actually really well organised" — before introducing anything new
Week 1: explain in one sentence what changes for them day-to-day, not what changes on the back end
Week 2: run a short side-by-side — "here's the same transaction in the old sheet and the new system" — so the jump feels like translation, not replacement
Week 3: keep the old spreadsheet accessible (read-only) for a defined period rather than deleting access immediately
Week 4: check in specifically on confidence, not just data accuracy — ask "does this feel manageable yet?"

Track B — Software-native clients:

Week 1: skip the basics entirely — ask what's currently connected and audit for redundant or conflicting app integrations
Week 1: agree on a single source of truth where duplicate tools overlap (e.g. two expense apps doing the same job)
Week 2: set up custom reporting/dashboards around what they actually check, not the default templates
Week 3: tidy the chart of accounts and categorisation rules inherited from their previous bookkeeper
Week 4: confirm reporting cadence and hand over a short "who to contact for what" reference, since these clients expect efficiency over hand-holding

Tradie client running a shared spreadsheet for eight years: Rather than migrating everything in one sitting, the bookkeeper kept the spreadsheet as a live reference for the first month, mapping each familiar column to its new home in the software. The client's main comment afterwards wasn't about features — it was "I didn't feel like I lost anything."

E-commerce client already in Xero with 40 connected apps: The onboarding call skipped setup entirely and became an audit — three apps were doing overlapping jobs, costing the client money each month for functionality they'd already replaced elsewhere. That consolidation conversation did more for the relationship than any welcome pack would have.

Hybrid client, part spreadsheet habits and a poorly set up MYOB file: Treated as a software client at first, they kept quietly reverting to their spreadsheet for anything they didn't trust yet. Once the bookkeeper noticed and switched them onto a blended version of both tracks, the reverting stopped.

How to actually tell which track a client needs

Ask before you assume

A simple pre-onboarding question — "what are you using to track this at the moment?" — tells you almost everything. Don't infer it from business size or industry; plenty of sophisticated businesses still run on spreadsheets by choice.

Watch for reverting behaviour

If a "software client" keeps sending you spreadsheet exports instead of using the connected system, that's a signal they were onboarded on the wrong track, not that they're being difficult.

Don't badge one track as the upgrade

Avoid language that implies spreadsheet clients are behind and software clients are ahead — some spreadsheet users have genuinely tight, well-built systems, and some software setups are a mess underneath the shiny dashboard.

💡 Don't delete the spreadsheet on day one. Cutting off a client's familiar system before they trust the new one is the single fastest way to create a nervous, disengaged client who quietly double-checks everything you do.

Mistakes to avoid

Running identical onboarding for every new client regardless of their starting habits
Removing access to a client's old spreadsheet before they've built trust in the new system
Walking software-native clients through basics they already know
Assuming business size or industry predicts which track a client needs
Treating a client's reverting behaviour as stubbornness instead of a signal to adjust the approach

Frequently asked questions

Should we push every spreadsheet client onto software immediately?

It depends on the client, honestly. For a very small, low-transaction business, a well-run spreadsheet can genuinely be the right-sized tool, and pushing them onto paid software adds cost and complexity without a real benefit. The trade-off is more manual work on your end reconciling it — worth weighing against the extra fee you'd need to charge to make that manual effort sustainable.

How long should the "old spreadsheet as backup" period last?

Long enough for one full reporting cycle so the client sees the new system produce a result they recognise and trust — often around four to six weeks, but it can be shorter for a confident client or longer for an anxious one.

What if a software-native client wants to be walked through everything anyway?

Some do, even if they don't need to be — let them set the pace rather than assuming. The track is a starting point, not a rigid script; adjust based on what the client actually asks for in week one.

Is it worth building a formal onboarding questionnaire to sort clients into tracks?

Yes, and it doesn't need to be elaborate — three or four questions about current tools, comfort level, and what's frustrating them now is usually enough to route them correctly without turning onboarding into an interrogation.

Keep reading 🤍

Written by

Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦