How Should Systems and Client Records Be Transferred During an Accounting Practice Handover?
Updated: Oct 24
GUEST AUTHOR | Blackhall & Co
Today’s guest post is by Blackhall & Co. Blackhall & Co helps buyers find businesses worth owning. Opinions expressed by guest authors are their own and do not necessarily reflect the views of Fairlane Finance.

A sound systems handover gives authorised people secure, tested access to the records and applications they need, with clear responsibility for correcting gaps and ending temporary access.
Transferring client records during an accounting practice handover is about more than moving folders. A file can arrive intact while the team still cannot find the latest correspondence, open an attachment or see which assignment needs attention first.
Those gaps become visible when a client calls expecting an answer.
For an Australian buyer, the aim is usable continuity: the right people, with appropriate authority, can perform the work as ownership changes. Your transfer plan should connect legal permissions, supplier arrangements and technical checks with the way staff actually serve clients.
Establishing access is the beginning of that process, rather than its completion.
Transferring client records during an accounting practice handover: the short answer
Map the systems, records, subscriptions and administrator arrangements supporting current work.
Confirm the lawful and contractual basis for access and transfer with qualified advisers.
Plan secure access changes and supplier processes around the agreed handover timetable.
Protect backups and test representative records, permissions and workflows.
Record incomplete items and allocate responsibility for resolving them.
Limit vendor and external-provider access to what remains authorised and necessary.
Start with the work the practice must keep doing
Your technology due-diligence review should already have identified important applications and dependencies. Turn that information into a practical map covering practice management, tax preparation, document storage, workflow, billing, email, client portals and any local servers. Include paper files and records held outside the main system.
For each area, identify the subscription holder, administrator, support provider and person who understands how staff use it. An application that appears straightforward in a demonstration may depend on an integration, shared folder or vendor-controlled email address. Those connections need their own place in the transfer plan.
Then connect the map to upcoming work.
Which files support an imminent lodgement? Which system issues payroll or invoices? Which portal carries client approvals? This helps you distinguish essential continuity from improvements that can wait, and gives the technology provider a practical basis for prioritising checks.
What can be accessed or transferred?
The answer depends partly on what the acquisition actually includes. Buying shares in an existing entity and acquiring selected practice assets can involve different arrangements.
Have your solicitor and relevant professional advisers assess engagement terms, confidentiality, privacy, ownership of records and the agreed treatment of access before the technical work begins.
Registered tax practitioners have specific confidentiality obligations. The Tax Practitioners Board’s client-information guidance explains that disclosure of information about a client’s affairs to a third party requires the client’s permission unless there is a legal duty to disclose. Ask advisers how this applies to the proposed transfer and whether existing permissions cover the actual recipients and arrangements.
A buyer-vendor confidentiality agreement should not be treated as client permission. Equally, avoid assuming every ownership change involves the same disclosure or requires the same document. Establish the applicable process, explain any action required from clients and keep evidence of the permissions and authorities on which the transfer relies.
Who controls subscriptions, accounts and recovery details?
Contact software and service providers early enough to understand their requirements. A subscription may need a change of contracting entity, a new account or an approved migration rather than a simple change of administrator.
Agree who pays during any overlap and how continued access will be maintained while the provider completes its process.
Cloud services also deserve a review of their terms and information handling. The TPB’s cloud-computing guidance discusses considerations for practitioners entering cloud arrangements. Ask your technology and professional advisers about access, security, availability, storage arrangements and the ability to retrieve records, including when external providers support the practice.
Email domains, website accounts and account-recovery details can be particularly easy to overlook.
If an administrator reset still sends a code to the vendor’s personal phone, your apparent control may be incomplete. Arrange the appropriate transfer of business-controlled recovery channels and test them without interrupting active services.
Government and professional portals require separate attention. Confirm the acquiring entity’s registration and the applicable authority, linking or notification processes directly with the relevant body.
Do not assume a transferred software subscription also transfers tax-agent registration, ATO client links or permission to act for a client.
How should access change securely?
Your data and cybersecurity due-diligence findings should now become specific access actions.
Establish named user accounts and appropriate roles, review existing permissions and identify accounts that should remain, change or close. Avoid relying on shared vendor credentials to make the first week easier.
The Australian Signals Directorate’s small-business cyber security guide recommends measures including multi-factor authentication and backups. Ask your technology provider to apply suitable protections through the transition, including recovery arrangements and a controlled way to supply account information. A hurried email containing passwords and private files creates another problem while solving the first.
The OAIC’s guide to securing personal information explains reasonable security steps for entities covered by the Privacy Act. Use that guidance with your advisers to assess access controls, storage, secure transfer and incident handling. The appropriate measures depend on the information, systems and risks involved, and completing the purchase does not make unrestricted access appropriate.
How do you establish that the records are usable?
Before a migration or major access change, agree the backup, validation and recovery approach with the technology provider. Identify the authoritative source, the intended destination and how changes made during transfer will be captured.
Staff need to know which version to use so new correspondence and work do not split across two systems.
A successful upload count is useful, but insufficient.
Test representative client records, including related entities, archived material, attachments, current work, engagement information and correspondence. Check that authorised staff can find and open them and that people outside the relevant role cannot access restricted material.
Reconcile transferred records against an agreed inventory and report exceptions. Missing documents, broken links or unfamiliar folder structures should have named owners and follow-up dates.
Ask a staff member who performs the work to test an ordinary workflow, such as locating the current file, recording a note and passing it to the reviewer.
If you intend to operate the practice remotely, include that operating environment in the tests. Access that works on an office desktop may still depend on local storage or equipment. Verify the approved remote connection and support arrangements before relying on them to deliver client work.
When should vendor access end?
Your vendor handover plan should identify the information and systems the vendor needs for agreed support. Time-limited, role-appropriate access can help them answer questions without leaving permanent administrator rights in place. Review access as responsibilities move to you and the team.
Include external contractors, offshore providers and former employees in that review. Establish what remains authorised and necessary, how access will be monitored and who approves its removal.
You should ask your advisers to explain any record-retention responsibilities before deleting material, because removing access and destroying records are different decisions.
An illustrative transfer check
Suppose migrated files open correctly, but a reviewer discovers that recent client approvals remain in a separate portal. In this illustration, the handover team records the gap, confirms the appropriate access and retrieves the missing material through the agreed process. A workflow test catches what a folder count missed. Actual transfer methods and permissions depend on the systems and circumstances.
Frequently asked questions
Can the vendor simply give me their passwords?
Use the appropriate provider processes and named accounts. Shared credentials can obscure responsibility and leave recovery details with the vendor. Ask your technology adviser to establish secure, authorised access.
Should all systems be replaced immediately?
Not automatically. Prioritise reliable access and current work, then assess later changes. A planned migration may be appropriate, but the timing should reflect client deadlines, resources and tested continuity.
Does moving records transfer client authority?
No automatic assumption should be made. Check applicable engagement, confidentiality, privacy and government or professional processes. Technical access alone does not establish authority to provide services or make lodgements.
How do I know the transfer is complete?
Reconcile against an agreed inventory, test representative files and workflows, and document exceptions. Obtain confirmation from the responsible people that both technical checks and practical user checks are satisfactory.
Can the vendor keep access throughout the handover?
Only through arrangements that remain appropriate and authorised. Define the purpose, permissions and review date, then remove or reduce access as the agreed work concludes.
Give the team a dependable starting point
A useful handover ends with more than a set of credentials.
You should know which systems and records are available, who can use them, what has been tested and what remains unresolved. That clarity gives staff a dependable starting point while you take responsibility for the practice’s service delivery.
Sources and further reading
Contributor disclaimer: This article is contributed by Blackhall & Co and published on the Fairlane Finance website. The views, opinions and conclusions expressed are those of the contributor alone, not statements of Fairlane Finance’s position. Publication does not constitute Fairlane Finance’s endorsement of the contributor’s views, services or any proposed acquisition.
The material is general information only. It is not financial, credit, investment, legal, tax, accounting, compliance or valuation advice, and does not take account of your objectives, financial position or circumstances. Do not rely on it as a substitute for independent investigation and advice from appropriately qualified professionals. You are responsible for assessing its accuracy, currency and suitability. Any reliance on it or action taken is at your own risk. To the maximum extent permitted by law, Fairlane Finance disclaims liability for loss or damage arising from reliance on this contributor content. Nothing in this disclaimer excludes or limits rights or liabilities that cannot lawfully be excluded or limited.






