From shared inbox to service desk: a migration guide for practices
A staged plan to move your practice off a chaotic shared inbox and onto a structured service desk your team will actually use.
Most accounting and bookkeeping practices run on a shared inbox far longer than they should. It works until it doesn't: a client emails a BAS query, three staff open it, nobody is sure who owns it, and a fortnight later the client follows up because no one replied. The shared inbox has no status, no owner, no due date, and no memory. A service desk fixes all four. This guide sets out a staged migration that keeps the lights on while you switch, and the change management that makes the team actually adopt it.
Why the shared inbox eventually breaks
A shared inbox treats every client request as a flat email. There is no concept of "open" versus "waiting on client" versus "done". Two people can work the same request without knowing. Annual leave means a mailbox full of half-answered threads with no handover. And when a principal asks "how many client jobs are sitting unactioned right now?", nobody can answer honestly.
A service desk turns each request into a work item with an owner, a status, a priority and a clear history. In Finye, inbound client emails are converted into work items automatically through email-to-ticket, so the inbox you already use becomes the front door to a structured queue rather than the place where work goes to get lost. Nothing changes for the client. Everything changes for your team.
Stage 1: map your current reality before you touch anything
Resist the urge to switch everything overnight. Spend a week watching how requests actually flow. Write down the recurring categories you see: BAS and IAS queries, payroll and STP questions, ATO correspondence, new-client onboarding, document chasing, ad hoc advice. These become your boards and your statuses, not a generic template someone copied from another firm.
Decide on a small, honest set of statuses. Most practices need no more than: New, In progress, Waiting on client, Waiting on ATO, and Done. Over-engineering the workflow at this stage is the single most common reason adoption stalls. You can always add a status later. You can rarely take one away once the team has learned it.
Stage 2: stand up the service desk and route email in
With your categories mapped, build the boards in Finye and connect email-to-ticket so new client emails land as work items on the right board. Set up assignees, priorities, checklists for repeatable jobs, and subtasks for anything multi-step. If you run recurring obligations such as quarterly BAS, configure them as templated recurring work so the jobs generate themselves instead of being remembered manually.
This is also the point to turn on the parts of Finye that make the desk feel lighter rather than heavier. AI triage can suggest a priority, assignee and category for each incoming request, which removes the daily chore of sorting the queue by hand. An AI ticket summary gives whoever picks up a long thread a fast read of what has happened so far. The goal is for the desk to save time on day one, not to add admin.
Stage 3: run a parallel period, then cut over
Do not delete the shared inbox on launch day. Run both for two to three weeks. Route new requests into the service desk while letting existing threads finish where they started. This parallel period is your safety net: it surfaces the edge cases your mapping missed and lets the team build muscle memory without fear of dropping a client.
Watch the list and kanban views together during this period. The board shows you where work is piling up; the list view is better for triage and bulk review. When the team is reaching for the desk by reflex rather than the old inbox, set a hard cut-over date, communicate it clearly, and switch inbound email fully across. After cut-over, the shared inbox should be read-only or closed.
Stage 4: manage the change so it sticks
A service desk fails for human reasons, not technical ones. Three things keep adoption alive:
- One owner, always. Make it a rule that every work item has an assignee. Unassigned work is the shared-inbox problem in disguise.
- A short daily standup on the board. Five minutes each morning looking at the queue together reinforces that the desk is where work lives, and catches anything Waiting on client that has gone quiet.
- Visible wins for the principal. Use the dashboard to show response times falling and the backlog shrinking. When leaders quote the board in meetings, staff follow.
Reinforce the new normal with the surrounding tools. Comments and attachments keep the full context on the work item instead of in someone's personal inbox. The client portal lets clients see their requests, upload documents and approve work, which cuts the back-and-forth that clogged the inbox in the first place. Pair the desk with Finye's compliance engine so lodgment obligations and due dates sit alongside the day-to-day requests, and your team has one place for everything a client needs.
What good looks like after the move
Within a month of a clean cut-over, a practice should be able to answer the questions the shared inbox never could: who owns this, what is it waiting on, when is it due, and how many are open. Handover at leave becomes trivial. New staff onboard against a visible queue rather than a folder of mystery threads. And client follow-ups drop, because nothing falls through the gap between "someone will look at it" and "someone did".
The migration is not about buying software. It is about giving every client request an owner, a status and a memory. Done in stages, with the team brought along, it is a few weeks of effort for a permanent change in how the practice runs.
If you are ready to move your practice off the shared inbox, you can start with Finye and build your first board in an afternoon, or review the options on our pricing page. For deeper how-to walkthroughs, browse our guides.