Accounting Firm Email Migration: Surviving Tax Season

Accounting firms have one immovable constraint: the tax calendar. Everything else in the migration plan bends around it. Move at the wrong time and the partners will notice within hours. Move at the right time, with the right preparation, and the partners will never know you did anything. This guide is the playbook for that second outcome.

The accounting firm migration calendar#

Build the timeline backwards from the calendar your firm actually keeps. The dates that matter:

• January through April 15: hard freeze. No mail platform changes. No DNS changes. No new mail rules. The phones are ringing.
• April 16 through April 30: stabilisation. Catch up on returns filed at the last minute, deal with rejected e-files, sort out the post-deadline mess.
• May through early June: planning window. Run discovery, sign contracts, pilot.
• Late June through early August: cut-over window. This is when the firm migrates.
• August 15 to September 15: stabilisation and Q3 preparation. Wrap up any loose ends.
• September 16 through October 15: hard freeze again for extension filings.
• October 16 through December 31: training, second-wave clean-up, end-of-year preparation.

Plan around those windows. The migration project plan template gives you the generic Gantt; the accounting overlay is the freeze periods.

Client confidentiality and the audit trail#

Tax correspondence is privileged in a narrower sense than legal correspondence, but it is still confidential. The IRS rules under Circular 230, state board of accountancy rules, and the AICPA Code of Professional Conduct all require you to protect client information. A migration touches every one of those obligations.

The controls that matter most:

• Only authorised personnel may touch client mail. If you use a third-party migration vendor, they need a written agreement that maps their access. A desktop tool that you run yourself avoids most of the third-party analysis.
• Encryption in transit on every mail connection, source and destination.
• An audit log per mailbox with operator, timestamps, message counts, and errors. The audit log guide describes the schema; the same shape applies here.
• A documented chain of custody for any mail exported to disk.

If you handle PHI for medical-practice clients (and many firms do), read the HIPAA migration guide. You are effectively a Business Associate to those clients during the migration window.

What the audit trail proves#

The point of the audit trail is not bureaucratic compliance. It is the answer to the question "did anything happen to client X's correspondence in June?" that you might be asked two years later. Keep the answer documentable.

A simple shape that works:

• One CSV per migration batch, written at run end.
• Columns: mailbox, source server, destination server, start UTC, end UTC, total source messages, total destination messages, delta, error count.
• Stored on the firm file server, encrypted at rest, retained as long as the underlying client workpapers.

If a client requests their data later, you can show that their mailbox was touched on a specific date, by a specific person, with a specific result.

Retention and the IRS seven-year rule#

The IRS retention requirement that drives the most decisions is the seven-year rule for workpapers and supporting documentation related to a filed return. Most firms apply this to email correspondence that supports a return. A migration is the moment to confirm your retention is enforced on the destination.

The source platform's retention policy does not migrate automatically. You need to recreate it on the destination. Microsoft Purview retention labels and policies, Google Vault retention rules, and Mimecast or Proofpoint archive retention all need to be re-configured.

Two patterns are common:

• Hot retention on the live mail platform for the full retention window. Simple, expensive at scale, and convenient for users.
• Cold retention in an archive system, with the live mail platform holding only the last 18 to 24 months. Cheaper, more complex, but well-suited to firms with decades of mail.

If you choose cold retention, plan the archive migration as a separate phase. Live mail moves first; archives move second. Pretending you can do both at once is the source of most "where did my 2019 inbox go?" tickets.

Tax-software and platform integrations#

Email is rarely the only thing that touches your mailbox. Your tax software, your practice-management platform, your e-signature tool, and your accounting platforms all send and receive mail on behalf of the firm. Each one needs attention during the migration.

The integrations that almost always need re-authorisation:

• Drake Tax, Lacerte, UltraTax, ProSeries, ProConnect, ATX: SMTP-relay or OAuth configuration for client communication and e-file confirmation.
• QuickBooks Online and QuickBooks Desktop: invoice and statement email. QuickBooks Desktop in particular still uses MAPI or SMTP relay that has to be re-pointed.
• Xero: invoice email-out, supplier email-in.
• Practice CS, ProConnect Tax Online, Karbon: notifications and client portal email.
• DocuSign, Adobe Sign, RightSignature: signing-ceremony emails.
• CCH Axcess, Thomson Reuters Onvio: cloud-tax platforms with their own SSO and mail flow.
• Bill.com, Ramp, Stampli: AP and expense systems that route by email.

Plan a re-authorisation day for these tools the week after cut-over. Most of them only break in subtle ways — silent SMTP relay failure, signature-request emails that never arrive — which means you find out about the problem from a client, not from a monitor.

QuickBooks Desktop is the usual surprise#

QuickBooks Desktop talks to mail through Outlook MAPI when configured to do so. Outlook MAPI talks to whatever Outlook profile is signed in. After a Microsoft 365 migration, the Outlook profile re-binds to the new tenant. If the QuickBooks setup is using cached SMTP credentials, those credentials may also have rotated. Both modes break silently.

Test invoice email-out from QuickBooks Desktop on every workstation that uses it within 24 hours of cut-over. Same for Xero, Drake, and any other platform that talks SMTP.

E-signature workflows#

E-signature is where client confidentiality and the migration collide most visibly. Signing ceremonies in flight at the cut-over window need to be tracked manually. If a client signed a 1040 on Friday and the migration ran Friday night, the signed copy may have landed in the source mailbox and not been forwarded.

The safer pattern:

• Pause new signature requests for 48 hours around the cut-over.
• Run a query against your e-signature platform for all envelopes in In Progress state.
• Manually verify after cut-over that completed signatures landed in the destination.
• Re-authorise the e-signature integration against the new mailbox before resuming.

Communicate the pause to the partners by name. They will accept a 48-hour delay if you tell them; they will not accept finding out a signed engagement letter went missing.

Where shared mailboxes hide#

Accounting firms accumulate shared mailboxes faster than they retire them. Common examples:

• tax@firm.com for general questions.
• audit@firm.com for audit-side correspondence.
• efile@firm.com for e-file confirmations from the IRS.
• payroll@firm.com for payroll-service correspondence.
• Per-partner assistant mailboxes that route through delegation.

Each one needs the same migration care as a user mailbox. Permissions do not transfer cleanly between platforms — Microsoft 365 shared mailbox permissions are not the same model as Google Workspace delegated access, and rebuilding them is a manual step after the data is moved.

Document the current permission map before you start. Use it as the rebuild checklist after.

The e-file confirmation mailbox is the canary#

The mailbox that receives e-file confirmations from the IRS is the one you watch most closely after cut-over. If it stops working, you stop getting acknowledgement-and-rejection notices. Test it on day one by submitting a low-risk return and confirming the acknowledgement lands.

Cut-over mechanics#

A 50-person accounting firm can usually cut over in a single weekend. Larger firms need a phased approach by department. Tax, audit, advisory, and admin are good batch boundaries because they map to distinct platforms and client lists.

A workable weekend pattern:

• Thursday evening: lock new mailbox provisioning. Pause distribution-list changes.
• Friday: bulk migration starts. Expect 90 to 150 minutes per mailbox on a typical firm connection.
• Saturday: complete any mailboxes that did not finish overnight. Re-verify counts. Test SMTP relay from tax software.
• Saturday evening: communicate to staff that cut-over is happening overnight.
• Sunday: switch DNS MX records. Run final delta sync from source. Disable the source mailboxes for write.
• Monday: stand by the helpdesk. Re-authorise the major application integrations as users hit them.

The migration timeline article has the generic weekend pattern; the accounting overlay is the application re-authorisation list.

Communicating with clients#

You usually do not need to tell clients about a migration. The address stays the same. The DNS swap is invisible. The signature block may change because you took the opportunity to update branding.

What you should tell them:

• If your sending IP or sending platform changes such that your mail might briefly land in spam, warn the top 50 clients before the cut-over.
• If your e-signature ceremony will pause, tell anyone with an envelope in flight.
• If your encrypted portal is changing, tell every client who uses it.

Most clients will not notice the migration at all. The ones who do are the ones whose specific workflow touches your email at a hand-off point. Anticipate those.

Decommissioning the source#

Tax firms hold the source server longer than most industries because of the seven-year retention. Plan for the source platform to live in read-only mode for at least the next return cycle. Some firms keep it longer.

For an Exchange on-prem source, archive the database files to encrypted cold storage after you have validated counts. For a SaaS source, drop to the cheapest mailbox tier and keep the admin account active. Either way, document who has the keys.

The decommissioning step is not glamorous and it is where most firms cut corners. Do not cut the source until you are certain that:

• All mailboxes are reconciled by message count.
• All shared mailboxes have been validated.
• All application integrations have been re-authorised and tested.
• All retention policies on the destination are firing as intended.
• All in-flight legal or tax-audit holds have transferred.

Only then do you turn the lights off on the source.

What's different from a law firm#

Many firms ask whether the accounting migration playbook is the same as the law firm one. The mechanics are similar; the freeze windows are different and the retention drivers are different. Read the law firm email migration guide for the legal-services view. The accounting-specific pieces — IRS retention, tax-software integrations, the April freeze — are the ones in this post.

FAQ#