New client offer Your first month free. No long-term contract, cancel anytime. Get started
Desktop to cloud migrations

Moving off desktop software,
done once and done right.

Desktop accounting software costs more every year, and every version eventually loses its bank feeds, payroll updates, and support. I help you decide whether and when to move, then handle the conversion end to end, so your history reconciles on the other side and your team is working confidently by the first month-end close.

Why now

The ground is shifting under desktop

Desktop software still works. But the economics and the support picture have changed, and the question for most small businesses is now when to move, not whether.

  • ✓New desktop subscriptions have largely ended. The most widely used desktop accounting product stopped selling new subscriptions for most of its editions to new U.S. customers in September 2024. Existing subscribers can still renew.
  • ✓Renewals keep climbing. Single-user renewals for the entry desktop edition rose from $999 to $1,149 a year in February 2026, with another round of increases announced for renewals from October 2026.
  • ✓Every version has an end date. Desktop versions lose bank feeds, payroll tax updates, live support, and security patches on a published schedule, typically about three years after release.
  • ✓The cloud is not immune either. Cloud prices have risen each summer too. The right answer depends on what your business needs, not on a vendor's timeline.

Figures are from my decision guide, verified October 2026. Vendor pricing and support dates change, so confirm current terms before you plan around them.

Your options

Three paths, and only one has no end date

Every desktop user faces the same choice. Running desktop on a hosted server is a variation of the second option.

Option 1

Stay on your current version

Keep what you have installed and renew only if required to keep it running.

Usually fits: A supported version with a planned move within 12 months.

Main risk: Lost bank feeds, payroll, and security updates once your version sunsets, plus rising renewals.

Option 2

Renew or upgrade desktop

Renew to the current release or move up to the enterprise edition, optionally hosted for remote access.

Usually fits: Heavy inventory, units of measure, very large files, or desktop-only workflows.

Main risk: The highest annual cost, and it delays rather than removes the eventual move.

Option 3

Move to the cloud

Convert your company file to a cloud accounting platform and retire desktop.

Usually fits: Most service businesses, contractors, and small product sellers with up to 25 users.

Main risk: A learning curve, some features that work differently, and a migration that must be done carefully.

What it costs

Three-year software cost, two common scenarios

Software list prices only. Payroll is an add-on on both paths and is excluded.

ScenarioStay on desktopMove to the cloudDifference
Solo owner, 1 user, no inventory Entry edition: $3,447 Entry plan: $1,368
Small team plan if you need bill pay or time tracking: $3,060
Cloud saves $387 to $2,079
Small team, 3 users, job or project costing Mid edition with 2 added users: $6,897
Hosted for remote access: $14,349
Growing business plan, 5 users: $5,040 Cloud saves $1,857 to $9,309

Desktop totals use February 2026 renewal rates held flat for three years, so they are understated. Cloud totals use August 2026 list prices, also held flat. Neither path shows the costs that never appear on the invoice: hardware, backups, and IT time on desktop; add-on apps and one-time migration and training on the cloud. Through my practice, a cloud subscription can be bundled into your monthly bookkeeping fee at no markup.

Is it right for you?

Which option fits your business

Most day-to-day bookkeeping works the same on both. The differences show up at the edges, so compare these against how your business actually runs.

Moving to the cloud makes sense if

  • ✓You have 1 to 25 users and service, project, or light inventory operations.
  • ✓Owners, staff, or your bookkeeper need access outside the office.
  • ✓You want to stop managing versions, backups, and hardware.
  • ✓Your renewal is approaching and the cloud plan that fits costs less.
  • ✓You want bank feeds, receipt capture, and a mobile app working for you.

Staying on desktop (for now) makes sense if

  • ✓You depend on units of measure, average-cost inventory, or advanced pricing rules.
  • ✓Your file is too large to convert, or a key industry app works only with desktop.
  • ✓Everyone works in one office and remote access is not a priority.
  • ✓Your version is supported and you are mid-season, with a move planned in the next year.
How a migration works

Most of the work happens before and after the conversion tool runs

The conversion itself moves your chart of accounts, customers, vendors, items, and transaction history. What makes a migration succeed is the preparation around it.

Three decisions before you start

How much history

Full history, a recent period (often one or two years), or lists and opening balances only. Older years stay available in an archived desktop file or exported reports.

Your cutover date

The start of a month at minimum. The start of a quarter or a new year is best, especially with payroll, because it keeps quarterly and annual payroll filings in one system.

Which plan fits

Based on users, inventory, classes, and project tracking. Upgrading later is easy. Downgrading can be restricted by usage limits.

Eight phases, start to finish

  1. Assess. Inventory your version, users, add-ons, integrations, payroll setup, and inventory, and check the file size. Watch for: Very large files cannot be converted directly and need condensing or a third-party tool.
  2. Clean up the desktop file. Reconcile every bank and card account through the cutover date, clear stale items, fix negative inventory, and verify the data. Watch for: Problems in the desktop file convert with it. Clean books in means clean books out.
  3. Save what will not move. Export reconciliation reports, memorized reports, the audit trail, budgets, and custom templates. Watch for: None of these convert, so they are archived first.
  4. Set up the cloud company. Choose the plan, set users and permissions, review the chart of accounts, classes, and locations, and line up connected apps. Watch for: Permissions work differently than desktop roles. Set them deliberately.
  5. Test conversion. Convert into a test company and compare the trial balance, receivables and payables agings, and inventory valuation against desktop. Watch for: Average-cost inventory converts as a single cost layer, so cost of goods sold can shift.
  6. Cutover. Run the final conversion, connect bank feeds from the cutover date forward, and move payroll and payments. Watch for: Duplicate transactions if bank feeds pull history that already converted.
  7. Validate and stabilize. Reconcile the first full month in the cloud, rebuild key reports, and keep the desktop file as a read-only archive. Watch for: A lapsed desktop subscription can lock you out of the old file.
  8. Train and support. Role-based training on your own data, then hands-on support through the first month-end close. Watch for: Desktop habits creep back in during the first 60 days.
Timeline

How long it takes

From kickoff to a stable, reconciled first month-end close in the new system.

Solo business
Lists and opening balances only, one user, no payroll move.
2 to 4
weeks, kickoff to first close
Typical small business
Clean books, up to five users, history converted, bank feeds and payroll moved.
6 to 10
weeks, kickoff to first close
Complex file
Heavy inventory, a mid-year payroll move, or more than one company.
10 to 16
weeks, kickoff to first close
What I handle

End to end, with a reconciled first close as the finish line

I hold current advisor certifications on both major cloud accounting platforms, and I run the whole project so your team keeps working while it happens.

  • ✓Assessment and plan. Your file, users, apps, and payroll reviewed, with a recommendation on history, cutover date, and plan. Including a straight answer if staying on desktop is the better call for now.
  • ✓Cleanup before conversion. Every account reconciled through the cutover date and stale items cleared, so problems do not convert with the data.
  • ✓A protected archive. Reconciliation reports, memorized reports, the audit trail, and budgets exported before anything changes.
  • ✓Setup, test, and tie-out. The cloud company configured, a test conversion run, and the trial balance and agings tied out before anyone relies on it.
  • ✓Cutover and connections. Final conversion, bank feeds from the cutover date forward, and payroll, payments, and apps moved without duplicates.
  • ✓Training timed to real work. Short, role-based sessions on your own data, then support through the first month-end close.

Migrations are scoped and quoted up front as a one-time project, after a free assessment of your file. If you continue with monthly bookkeeping afterward, the cloud subscription can be bundled into your fee at no markup.

Desktop or cloud? The full decision guide.

Ten pages, free: where things stand today, your three options, a full cost comparison, expense versus depreciation, features side by side, support and remote access, learning curve and training cost, what users report, and a phase-by-phase migration plan with a week-by-week timeline.

Download the guide (PDF)

Tax questions go to your CPA. I am a bookkeeper, not a CPA or Enrolled Agent. I record software, hardware, migration, and training costs consistently and flag them for your tax preparer, but the treatment, elections, and timing are your CPA's decision.

Common questions

Migration questions

Do I have to move off desktop software right now?

Not necessarily. If your version is still supported and you plan to move within the next year, staying put while you plan is reasonable, and if you rely on units of measure, average-cost inventory, or a very large file, renewing desktop may be the right call for now. The risk is waiting until your version loses bank feeds, payroll updates, and security patches, then migrating in a rush.

Will my transaction history come over?

Most of it. The conversion moves your chart of accounts, customers, vendors, items, and transaction history. Reconciliation history, memorized reports, and the audit trail do not convert, so I export and archive them before cutover. You can also choose to bring a recent period, often one or two years, or lists and opening balances only, with older years kept in a read-only archive.

How long does a migration take?

A typical small business with clean books and up to five users moves in six to ten weeks from kickoff to a stable first close. A solo business converting lists and balances only can be done in two to four weeks. Inventory-heavy files, mid-year payroll moves, or multiple companies run ten to sixteen weeks.

Which cloud platform should we move to?

It depends on your users, inventory, project tracking, the apps you rely on, and your budget. I hold current advisor certifications on both major cloud accounting platforms, so the recommendation follows what your business needs rather than a default.

Does moving to the cloud change how software costs are taxed?

Usually less than people expect. Desktop editions are now sold as annual subscriptions, which are generally treated as ordinary operating expenses, the same as a cloud subscription. Hardware bought to run desktop software is a depreciable asset, and migration and training fees are generally ordinary business expenses. I record these costs consistently and flag them for your tax preparer, but the treatment, elections, and timing are your CPA's decision.

Can you keep doing my books after the migration?

Yes. Many clients start with a migration and continue with monthly bookkeeping in the new system, which is the easiest way to make sure the habits stick after the first close.

Find out where your file stands.

A free assessment of your desktop file, your options, and a realistic timeline. No pressure, no jargon.