CPA Software Migration Guide: How to Switch Tax & Accounting Software Safely

Quick Summary

A CPA software migration involves more than transferring client files from one tax or accounting application to another. Firms need to review their current data, confirm conversion support, protect original records, test representative files, rebuild important workflows, reconnect integrations, configure permissions, and train staff before the new system becomes the production environment. The migration plan should also account for tax-season deadlines, client communication, historical data, security controls, backups, and the possibility that some information will require manual review. A controlled transition gives the firm time to identify conversion problems before they affect live client work.

  • Inventory first: Document applications, client records, integrations, users, workflows, templates, reports, and historical data.
  • Protect original data: Create verified backups and keep the existing environment available until the migration has been validated.
  • Test real workloads: Convert representative individual, business, multistate, fiduciary, and other relevant files before the final migration.
  • Validate the result: Compare converted data, calculations, forms, diagnostics, attachments, reports, and connected workflows.
  • Plan the transition: Schedule training, user setup, integrations, client communication, support, and cutover around the firm’s busiest periods.

Introduction

Switching tax or accounting software is not simply a matter of buying a new license and importing client files. A CPA firm has to move client data, preserve prior-year information, rebuild workflows, reconnect integrations, train staff, and verify that the new system produces the expected results. The migration also has to protect taxpayer information throughout the process because tax professionals are required to maintain a Written Information Security Plan (WISP) for client data.

This CPA software migration guide explains how to plan a software transition, what data to check before moving, how tax return conversions work, when to migrate, how to test converted files, and what to do before shutting down the old system. The goal is not to make migration sound easier than it is, but to give a CPA firm a practical process that reduces surprises during the first filing season on the new platform.

Quick Migration Checklist

Migration stageWhat the firm should complete
1. Define the reasonDocument why the current software no longer fits
2. Select replacementCompare tax/accounting, workflow, cloud, integration, and support requirements
3. Inventory dataIdentify clients, returns, documents, users, reports, integrations, and historical records
4. Confirm conversionVerify exactly which return types and fields the new vendor can convert
5. Back upCreate and verify complete source-system backups
6. Create test groupSelect representative simple and complex clients
7. Convert dataRun the vendor’s conversion process
8. ReviewCompare converted data against the original
9. Rebuild workflowConfigure users, permissions, templates, integrations, and processes
10. Train staffTrain preparers, reviewers, administrators, and support personnel
11. Run parallel testingPrepare representative work in both environments where practical
12. Go liveMove production work only after validation
13. Retain recordsPreserve required historical records and access to old data

That sequence matters because conversion is only one part of migration. For example, Drake currently publishes conversion programs for several competing tax systems, including Lacerte, ProSeries, ProSystem fx, TaxWise, TaxAct, and UltraTax, but its documentation also identifies return types and data that are not converted.


1. Start With the Reason for the Migration

Before comparing replacement products, document exactly why the firm wants to leave its current software. A vague objective such as “we need better tax software” makes it difficult to measure whether the migration actually solved the problem. Instead, identify the operational issue, the people affected, and the result the firm expects after the transition.

Common reasons include:

  • Current software lacks required tax forms.
  • The firm wants browser-based access.
  • Remote work has become more important.
  • The existing workflow requires too much manual entry.
  • Reporting is insufficient.
  • Integration with accounting software is limited.
  • Client or document management is fragmented.
  • The firm’s return volume has increased.
  • The current product no longer fits the firm’s return complexity.
  • Licensing or total operating costs have become difficult to justify.
  • Vendor support or training no longer matches the firm’s needs.

Write these requirements down before looking at alternatives. Otherwise, the firm can easily choose a product because it has an impressive feature list without solving the original problem.


2. Decide What Actually Needs to Move

One of the most common migration mistakes is treating “client data” as one thing. Tax returns, accounting transactions, documents, depreciation schedules, user accounts, templates, client lists, historical reports, signatures, and workflow information may all follow different migration processes.

Create an inventory before requesting a conversion.

Tax software

Check:

  • 1040 returns
  • 1040-NR returns
  • 1065 returns
  • 1120 returns
  • 1120-S returns
  • 1041 returns
  • 706 returns
  • 709 returns
  • 990 returns
  • State returns
  • Local returns
  • Foreign reporting
  • Depreciation information
  • K-1 information
  • Prior-year carryforwards
  • Extension information

Do not assume that because a vendor converts 1040 data, every part of a 1040 return will transfer. Intuit’s current conversion documentation, for example, lists several return types that can be converted to Lacerte or ProSeries while specifically identifying items such as 1040-NR, state modules, 706, 709, 990, and 5500 as not converted in that process.

Accounting software

Also identify:

  • Chart of accounts
  • Customers
  • Vendors
  • Bank accounts
  • Transactions
  • Open invoices
  • Open bills
  • Recurring transactions
  • Attachments
  • Classes or locations
  • Projects
  • Inventory
  • Fixed assets
  • Tax settings
  • User permissions
  • Historical reports
  • Payroll connections
  • Third-party integrations

The migration plan should distinguish between data that can be converted, data that can be exported and retained, and data that must be recreated manually.


3. Check Conversion Support Before Signing

Never assume that two products can exchange data simply because they serve the same type of firm. Conversion support differs by vendor, tax year, return type, and source application.

For example, Drake currently lists conversion support for 1040, 1041, 1065, 1120, and 1120-S returns from several competing systems, including Lacerte, ProSeries, ProSystem fx, TaxWise, and UltraTax. Drake also states that it does not currently convert 706, 709, 990, or 1040-NR returns through those conversion programs.

Intuit similarly provides conversion paths into Lacerte and ProSeries from products including Drake, ProSeries, Lacerte, CCH Axcess, ProSystem fx, TaxWise, TaxAct, TaxSlayer, TurboTax, and UltraTax, with supported return types varying by source and target.

Ask the vendor these questions

QuestionWhy it matters
Which source programs are supported?Determines whether direct conversion is possible
Which tax years can move?Prevents unsupported historical conversions
Which return types convert?Identifies manual work
Which states convert?Federal conversion may not include state data
Which fields convert?Return-type support does not mean complete conversion
Are documents included?Tax data and documents may follow separate processes
Are depreciation records included?Asset information can require special handling
Are passwords or locks allowed?Some conversion systems require them removed
Is the old software required?Some conversion tools depend on the source installation
How long does conversion take?Helps establish the migration schedule

This is one of the most important parts of a tax software conversion guide because a vendor’s statement that it “supports conversion” does not mean every piece of the old return will appear in the new system.


4. Back Up the Old System Before Touching Anything

Create a verified backup before beginning the conversion process. Keep the original backup protected and do not overwrite it with converted files.

Vendor instructions demonstrate why this matters. Drake’s current conversion instructions require firms to calculate client files, remove locks and passwords where applicable, create a conversion folder, and back up client files before submitting them for conversion.

Thomson Reuters gives similar guidance for UltraTax CS migrations, including backing up client data and application settings before moving applications or data to another computer or server. Its documentation also warns that simply copying data folders can leave settings behind and may create performance or stability problems.

Keep at least three copies of important migration data

  • Working copy: used for the conversion.
  • Protected backup: untouched original data.
  • Recovery copy: stored separately from the primary environment.

The exact backup architecture should follow the firm’s security and business-continuity requirements. The important point is simple: never make the conversion itself your backup strategy.


5. Build a Representative Test Group

Do not test migration using only the easiest 1040 in the database. A clean 1040 can make a conversion look successful while hiding problems with partnerships, S corporations, trusts, depreciation, multi-state returns, or unusual elections.

Build a representative sample.

A useful test group can include:

  • Simple 1040
  • High-income 1040
  • Multi-state individual
  • S corporation
  • Partnership
  • C corporation
  • Trust or estate
  • Return with depreciation
  • Return with multiple K-1s
  • Return with foreign information
  • Return with state-specific adjustments
  • Return with prior-year carryforwards

The exact sample should match the firm’s actual client base. If 70% of the firm’s work involves complex business returns, testing ten simple 1040s does not tell you much about the migration risk.

Intuit explicitly notes that its conversion process is not designed to produce a complete or accurate prior-year return for side-by-side comparison. That is a useful warning for any firm planning a conversion: converted data still needs review.


6. Understand What “Converted” Actually Means

A converted return is not necessarily a perfect copy of the original return. Different tax applications use different databases, input screens, calculations, file structures, and ways of storing supporting information.

Drake’s documentation, for example, states that certain data does not convert and warns users to verify the resulting file. Its instructions also explain that only one return for each SSN/EIN is converted when the source software contains multiple returns for the same identifier, meaning firms need to verify that the intended return was carried over.

Thomson Reuters similarly tells firms to review converted data during its UltraTax conversion workflows.

That means a successful upload is not the finish line.

The real test is whether the converted information supports accurate preparation in the new system.


7. Review the Converted Returns

Once the conversion finishes, compare the new file against the original.

Do not review only whether the client name and Social Security number appear correctly. Compare the information that can materially affect the return.

Tax-return conversion review

Check:

  • Taxpayer and spouse information
  • Dependents
  • Filing status
  • Addresses
  • W-2 information
  • 1099 information
  • Schedule C data
  • Schedule E data
  • K-1 information
  • Capital gains
  • Depreciation
  • Carryforwards
  • Estimated payments
  • Credits
  • Foreign information
  • State adjustments
  • Prior-year amounts
  • Elections
  • Business ownership
  • Basis information
  • Supporting statements

Accounting migration review

Check:

  • Trial balance
  • Bank balances
  • Accounts receivable
  • Accounts payable
  • Retained earnings
  • Inventory
  • Fixed assets
  • Customer balances
  • Vendor balances
  • Open transactions
  • Sales tax
  • Reconciliations
  • Historical reports

A useful validation method is to compare several reports from the old and new systems using the same cutoff date. Differences should be investigated rather than dismissed as normal conversion behavior.


8. Pay Special Attention to State Data

Federal conversion does not automatically mean state conversion. Drake’s current documentation specifically says that its conversion process converts federal returns and that some state information may need to be entered after the federal data flows into the state program.

This can become a significant issue for firms handling multi-state clients. A return may appear complete because the federal information transferred successfully while state-specific information still requires manual work.

For firms with significant state-return volume, test several states separately. Include at least one client with state modifications, credits, depreciation differences, or other state-specific information that the firm routinely handles.


9. Plan the Migration Around the Tax Calendar

The best time to switch tax software depends on the firm’s workload and the type of migration. There is no universal month that works for every practice.

A firm with a large individual-return workload may prefer to complete major conversion work before the next filing season. A firm that handles many extensions may need a different schedule because unfinished returns can require different conversion treatment.

Thomson Reuters’ current UltraTax documentation illustrates this issue: the appropriate conversion year can depend on whether a return has not started, is on extension, or has already been completed.

A practical migration calendar

6–12 months before filing season

  • Define requirements.
  • Select replacement software.
  • Confirm conversion support.
  • Inventory data.
  • Plan training.
  • Identify integrations.

3–6 months before filing season

  • Back up data.
  • Run test conversions.
  • Review representative returns.
  • Identify missing fields.
  • Rebuild workflows.
  • Configure users.

1–3 months before filing season

  • Complete staff training.
  • Run additional conversion batches.
  • Test e-file processes.
  • Verify integrations.
  • Complete security checks.
  • Finalize the cutover plan.

During filing season

  • Avoid unnecessary system changes.
  • Maintain documented support procedures.
  • Keep the old system available where required.
  • Track conversion issues centrally.

The exact timing should follow the firm’s workload and the conversion schedule provided by the new vendor.


10. Rebuild the Workflow, Not Just the Data

A successful migration can still fail operationally if the firm transfers client records but ignores how staff actually work.

Document the old workflow before rebuilding it.

Map these processes

Client intake → document collection → preparation → review → corrections → e-file → signature → delivery → archive

Then identify where the new software handles each stage.

For example, determine:

  • Where client information enters the system.
  • Who prepares returns.
  • Who reviews them.
  • Where supporting documents are stored.
  • How staff communicate internally.
  • How e-file status is tracked.
  • How signatures are obtained.
  • How completed returns are archived.
  • How managers monitor unfinished work.

The software migration should improve or preserve these processes rather than simply replacing the application’s database.


11. Reconnect Integrations

Integrations are easy to overlook because they may sit outside the tax or accounting application itself. A firm can complete a technically successful migration and still discover that its document system, practice-management platform, payment service, accounting system, portal, or e-signature workflow no longer connects properly.

Create an integration inventory before the migration.

IntegrationCurrent systemNew systemAction
AccountingExisting platformNew platformTest connection
Document managementExisting DMSNew workflowReconfigure
Practice managementCurrent PMSNew tax/accounting systemVerify integration
E-signatureCurrent providerNew workflowTest
Client portalExisting portalNew portal/systemTest
PaymentsExisting processorNew processorVerify
Tax researchExisting serviceNew environmentConfirm access
BackupExisting providerNew environmentReconfigure

Do not wait until the first client return is ready to discover that an integration stopped working.


12. Recreate Users and Permissions

User migration deserves its own checklist. Staff members may have different access levels in the new system, and those permissions should match their actual responsibilities.

Review:

  • Administrators
  • Preparers
  • Reviewers
  • Partners
  • Managers
  • Billing staff
  • IT administrators
  • Temporary users
  • Former employees

Remove accounts that no longer need access. Confirm multi-factor authentication where available, and document who can access client data, export information, change settings, or administer users.

Thomson Reuters’ current onboarding materials specifically include account setup, tax data conversions, data migrations, and security tasks such as multi-factor authentication as part of its onboarding process.


13. Protect Client Data During Migration

Tax software migration creates a temporary data-handling risk because client information may move between systems, computers, servers, vendors, or conversion teams. The firm’s security controls therefore need to cover the migration process itself.

The IRS states that tax professionals must maintain a WISP and should identify risks, implement safeguards, monitor and test those safeguards, and address service providers that handle customer information.

Add migration to the firm’s security plan

Review:

  • Who can export client data?
  • Where are conversion files stored?
  • Who can upload them?
  • How are files transferred?
  • How long are conversion files retained?
  • Who receives converted files?
  • How are temporary files deleted?
  • Are former employees removed from access?
  • Are backups encrypted?
  • Is MFA enabled?
  • How will the firm respond if data is exposed?

The IRS also recommends core safeguards such as two-factor authentication, backups, drive encryption, firewalls, security software, and secure VPN use as part of its tax-security guidance.

A migration project should therefore be treated as both a technology project and a client-data protection project.


14. Train Staff Before the Cutover

Do not train everyone only after the new software becomes mandatory. Staff need enough time to understand the new workflow while the old system is still available for reference.

Training should cover:

  • Navigation
  • Client setup
  • Data entry
  • Conversion review
  • Diagnostics
  • E-file
  • Documents
  • Review procedures
  • User permissions
  • Reports
  • Common errors
  • Support procedures
  • Escalation process

Separate training by role where necessary. A preparer does not need exactly the same training as a firm administrator, and a reviewer needs to understand different controls from someone who handles client intake.


15. Run a Parallel Test Before Going Live

Parallel testing gives the firm an opportunity to compare actual work before committing completely to the new system. Select representative returns and perform the same preparation or review process in both environments where the firm’s workflow makes that practical.

Compare:

  • Data entry
  • Calculations
  • Diagnostics
  • Forms
  • State results
  • Reports
  • E-file output
  • Carryforward information
  • Review notes
  • Workflow time
  • Manual corrections

The goal is not necessarily to make every screen look identical. Different applications organize information differently. The important question is whether the new system produces the required work accurately and efficiently after the firm’s review process.


16. Keep a Migration Issue Log

Do not rely on staff members remembering conversion problems individually. Create one central issue log.

IssueClient/return typeImpactOwnerStatus
Missing depreciation1120-SHighTax managerOpen
State data missing1040MediumPreparerTesting
User permission errorFirm-wideHighAdminResolved
Document link missing1040MediumITOpen
Integration failureMultipleHighVendorEscalated

This creates a record of what went wrong and prevents the same issue from being discovered repeatedly by different staff members.


17. Do Not Shut Down the Old System Too Early

Keep the old environment available until the firm confirms that required historical data is accessible and the new workflow is operating correctly. The retention period should follow the firm’s legal, regulatory, contractual, and recordkeeping requirements rather than an arbitrary number of months.

Before decommissioning the old software, confirm:

  • Historical returns are accessible.
  • Required documents are preserved.
  • Reports are available.
  • Conversion issues are resolved.
  • Staff know where historical records live.
  • Required exports are complete.
  • Backups have been verified.
  • Vendor access is no longer needed.
  • Former-user access has been removed.

The old system should become a controlled historical reference, not an abandoned application sitting on an unsecured computer.


CPA Software Migration Checklist

Use this checklist before declaring a migration complete:

Before migration

  • Document why the firm is switching.
  • Define required features.
  • Inventory clients and return types.
  • Inventory integrations.
  • Confirm supported conversions.
  • Confirm supported tax years.
  • Identify data that will not convert.
  • Review vendor migration documentation.
  • Create a migration schedule.
  • Update the firm’s WISP where necessary.

During conversion

  • Create a verified backup.
  • Prepare source data according to vendor instructions.
  • Remove locks/passwords when required.
  • Convert representative test returns.
  • Check federal data.
  • Check state data.
  • Check depreciation.
  • Check carryforwards.
  • Check supporting information.
  • Record conversion problems.

Before going live

  • Configure users.
  • Configure permissions.
  • Enable MFA where available.
  • Reconnect integrations.
  • Test e-file.
  • Train staff.
  • Compare reports.
  • Run representative workflows.
  • Resolve critical conversion issues.
  • Establish support contacts.

After migration

  • Monitor the first production returns.
  • Track issues centrally.
  • Preserve required historical data.
  • Verify backups.
  • Remove unnecessary access.
  • Review the migration against the original objectives.

Final Takeaway

A successful CPA software migration is not measured by how quickly client files appear in the new application. It is measured by whether the firm can prepare, review, file, document, and manage client work accurately after the transition without losing important information or weakening its security controls.

The most important step is to understand exactly what the new vendor can convert before the firm commits to a cutover date. Official conversion documentation from Drake, Intuit, Thomson Reuters, and CCH shows that supported programs, return types, tax years, fields, and conversion procedures can differ substantially.

Treat the project as data migration + workflow redesign + staff training + security review, not simply software installation. Back up the original data, test representative returns, compare converted information, reconnect integrations, validate permissions, and keep the old environment available until the firm has verified its new process. That approach gives a CPA firm a much better basis for deciding when to switch tax software, how to migrate client data, and how to enter the next filing season without discovering migration problems at the worst possible time.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top