Switching to OLTPRO: A Practical Migration Checklist for Tax Professionals

Switching tax software is a practice transition, not just an installation. Before moving to OLTPRO, decide what needs to transfer, what must remain accessible in your old system, and how you will prove the new workflow is ready for real clients.

Public preparer discussions repeatedly raise concerns about incomplete rollovers, carryovers, historical records and the time required to verify converted files. Those reports are individual experiences, not proof of a current OLTPRO defect. The useful lesson is to test your own data and workflow before committing.

Use the checklist below as a working plan. It does not promise compatibility with any source program or an error-free migration. Confirm the exact OLTPRO edition, tax year and conversion scope with OLTPRO support before transferring client files.

1. Confirm what can actually move

  • Record your source software, edition, tax years, return types, file formats and approximate client count.
  • Ask OLTPRO support which of those specific files can be converted, what source files are required, and what will not transfer. Request written instructions and an exclusions list.
  • Separate a client contact import, a cross-software conversion and a year-to-year rollover. Do not assume support for one means support for the others.
  • Inventory practice data separately: preparer settings, billing records, appointments, client notes, document attachments, signatures, workflow statuses and e-file acknowledgments. Decide whether each item will migrate, be rebuilt or remain in an archive.
  • Assign an owner and verification method to every category. A PDF copy is useful for reference, but do not assume it can replace a native data file for conversion.

OLTPRO describes prior-year import and multi-user features publicly. Those descriptions do not establish that your particular source software, tax year or complete practice database is supported.

2. Choose a cutover window you can defend

  • Work backward from your first planned production return. Allow time for support responses, trial conversion, reconciliation, staff practice and corrections.
  • Prefer a lower-volume period over a deadline week. If your pilot cannot pass review in time, postpone the full switch rather than compress testing.
  • Set a final export time and identify which system is the source of truth before and after cutover. Avoid uncontrolled edits in both systems.
  • List open returns, extensions, amendments and unresolved acknowledgments. Give each an owner and decide which system will finish the work.
  • Confirm how long you will retain access to the old software and its historical records before canceling or changing that access.

3. Back up first, and prove you can recover

  • Create a native backup using the source vendor's instructions before conversion. Preserve the original unchanged.
  • Save reference copies of filed returns, supporting schedules, carryforward worksheets, depreciation reports and relevant filing acknowledgments.
  • Store backups with restricted access and appropriate protection. Use only the vendor-approved secure transfer process for sensitive files; do not send taxpayer data through ordinary email or public discussion boards.
  • Test recovery using the vendor-supported method in a separate location. Record the backup date, tax years, file count and person responsible.
  • Write a rollback plan: what would stop launch, who decides, and how work resumes if the conversion needs correction.

4. Reconcile carryovers, not just client names

A client appearing in the new system does not mean the return is ready to prepare. Build a client-by-client reconciliation worksheet with the source amount, destination amount, difference, corrective action and reviewer sign-off.

  • Check identity, spouse and dependent details, filing status and contact information.
  • Review applicable capital-loss, net-operating-loss, credit and passive-activity carryforwards against source schedules.
  • Verify depreciation assets, acquisition dates, original costs, methods, accumulated depreciation and remaining information needed for future calculations.
  • Review basis records, elections and state-specific carryovers where relevant. Reconcile federal and state information separately.
  • Identify anything excluded from conversion and enter it through a documented, reviewed process. Keep the supporting records attached to your review trail.

These are verification categories, not claims that OLTPRO imports every listed item. A year-to-year rollover and a conversion from another vendor can have different limits.

5. Run a representative pilot before the full move

  • Select a small pilot, such as 5–10 clients, covering the work your office actually handles: a straightforward individual return, self-employment, depreciation, pass-through income, carryovers and multistate work as applicable.
  • Use vendor-supported test procedures. Where appropriate, use synthetic practice data for training and limit access to any real client data used for reconciliation.
  • Compare transferred inputs and supporting schedules with the source records. When comparing outputs, use the same tax year and facts; investigate differences rather than expecting different years to calculate identically.
  • Check diagnostics, print output, document handling, review handoffs and acknowledgment tracking. Test filing steps only through approved test or demonstration procedures; do not submit a live return merely to test the setup.
  • Keep an issue log with the affected field, expected result, actual result, software version, reproduction steps, support case and resolution. Retest recurring errors after a change and check whether other files share the same issue.

6. Test multi-user access and daily handoffs

  • Confirm the selected edition, licensing and deployment requirements with OLTPRO before assuming your planned office setup is supported.
  • Create individual staff accounts and review permissions for preparation, review, reports and filing responsibilities.
  • Have staff test access from their actual workstations. Verify how the system handles simultaneous access to a client file, saving, handoffs and recovery from an interrupted session.
  • Confirm who can change firm settings, restore backups and approve production filing. Do not use shared credentials as a shortcut.

7. Make launch a go/no-go decision

Before going live, require a verified backup, a reconciled pilot, documented treatment of excluded data, tested staff access, trained reviewers and no unresolved issue that could affect return accuracy or filing control. Reconcile the full migration's client counts and exceptions, then require client-level review before each first-year return is filed. A successful pilot does not validate every client.

Start with a manageable production workload and keep a support and correction log. If a critical check fails, pause the affected work and use your rollback plan instead of guessing.

Build software confidence alongside your migration plan

Once you have defined the conversion and review process, give your team time to practice. The OLTPRO Software Accelerator is a three-week, hands-on training experience with six live sessions and 12 hours of instruction. Its listed focus includes software navigation, practice returns, diagnostics, troubleshooting, review and the e-file workflow.

Use that practice to strengthen day-to-day readiness. The program is not presented as a data-conversion service, a compatibility guarantee or a substitute for vendor confirmation and client-by-client reconciliation.

Sources and further reading

Back to blog