All migration services
The migration hub — reverse moves, other-software switches, cross-platform conversions, and the 7-point Migration Integrity Protocol.
The engagementIndependent bookkeeping & advisory firm · Serving clients nationwide, remotely
Intuit’s migration tool copies your data — then Intuit asks you to review the result, find what didn’t transfer and prove the reports match. TechBrot runs the full migration: conversion, integrity verification against the Desktop baseline, reconciliation, app and workflow rebuild, and training — so the new file works on day one. Fixed fee, two to four weeks.
What you can check before you sign
If your file needs our paid diagnostic first, its fee is credited in full against the cleanup. Either way, you get a fixed fee in writing before any work starts.
A QuickBooks Desktop to Online migration converts your Desktop company file into QuickBooks Online, then proves it: trial balance and key reports checked against the Desktop baseline, opening balances tied to the conversion date, bank feeds and apps rebuilt, your team trained. Fixed fee $2,500–$10,000+; two to four weeks for a standard migration.
They took something that felt overwhelming to me as a first-year business owner and made it simple.
What stood out the most was TechBrot Inc’s attention to detail.


What Intuit's migration tool does, what it leaves to you, and when a do-it-yourself Desktop to Online move is genuinely enough — set out in full below.
All migration services · What doesn’t convert from Desktop to Online · Get the free file review · Send the details
TechBrot’s senior reviewer holds the Intuit QuickBooks Certification Level 2 and QuickBooks Workforce Certification, and TechBrot works in Desktop files — the two platforms a migration spans. Verification available on request.
TechBrot’s senior reviewer is a Certified QuickBooks ProAdvisor, and the certifications are held by that person, not by the firm.
Intuit’s tool does the data copy. Each of the six steps below answers a specific way that copy falls short — what doesn’t move, what it re-bases, what it turns into something else — and the sections below name the mechanism behind each and the validation that proves the result.
We review the Desktop file first — size, integrity, list count, inventory method, customizations — and flag anything that needs cleanup before conversion. Migrating a broken file just moves the problems.
The actual Desktop-to-Online conversion, run correctly — chart of accounts, customers, vendors, items, and transaction history moved into a properly prepared Online company.
Trial balance, account balances, and key reports compared between the documented Desktop baseline and the converted Online file. Every discrepancy investigated — not a hope that the copy worked.
Reconciled status verified and opening balances confirmed as of the conversion date, so your first Online reconciliation starts from a known-good baseline instead of inherited drift.
Bank feeds reconnected; payroll, payments, receipt-capture, e-commerce, and reporting apps reconnected and reconfigured for Online. Sales tax re-set up for QBO’s automated model. Intuit says bank connections don’t move with the data, so each connection and app is rebuilt and checked.
Online works differently — classes, locations, projects, recurring transactions, user roles all reconfigured to match how you operate, plus team training so the new file is usable from day one.
Chart of accounts, customers and vendors, most lists, item lists, and transaction history (invoices, bills, payments, journal entries). Reconciled status on transactions. Open balances. The core ledger comes across — it just has to be verified.
Past reconciliation reports, memorized reports, the audit trail, custom form templates, memorized transaction groups, bank connections, units of measure, price levels, and progress invoices — Intuit’s own list. Other records change shape: paychecks arrive as regular checks with current-year paycheck information as lump sums, inventory is imported as FIFO, and Desktop jobs become projects or sub-customers.
The essentials that don’t convert — key reports recreated, recurring transactions checked and memorized groups rebuilt, forms rebranded, classes/locations/projects reconfigured, payroll and sales tax re-set up, and integrations reconnected — so nothing critical is lost in the move, even where it doesn’t move on its own.
“Doesn’t transfer” is four different failures, and each needs a different fix. Knowing which is which is what turns a list of losses into a plan.
Online has no object to write it into. Intuit’s own transfer article (updated 2026-09-11) lists what doesn’t move: memorized reports, custom form templates (logos do move), memorized transaction groups (“Groups don’t exist in QuickBooks Online”), units of measure, price levels, custom fields on items and employees, and progress invoices based on estimates. Nothing breaks visibly; the item is simply absent when someone goes looking. The fix is manual and has to be planned before conversion: the memorized reports listed, the templates saved as PDFs, the transaction groups written down — then each rebuilt in Online as a custom report, a custom form style, or a set of recurring transactions. Budgets are the grey area: the same Intuit article lists Profit and Loss budgets among what moves and also says “Budgets aren’t recreated in QuickBooks Online due to mapping differences,” so we check them in the new file rather than assume either way.
Online stores it differently, so history is recomputed. Inventory is the clearest case: Intuit imports inventory “as First-In, First-Out method (FIFO)” from a FIFO start date you set, and its after-the-move article (updated 2026-08-05) says that because QuickBooks Online “may calculate inventory values and cost of goods sold (COGS) differently, your reports may not match exactly” — adding that you may need to notify the IRS of the change on Form 3115. The quantity on hand comes across; if the Desktop file valued inventory at average cost, the value can legitimately change, and it has to be documented as a known variance rather than hunted as an error. Sales tax works the same way — Intuit says “Some taxes move as journal entries. Sales tax won’t copy for all transactions,” so the agencies and rates are set up again in Online and the liability is verified against the Desktop figure rather than assumed. Desktop’s class-and-job structure maps onto Online’s class, location and project model — Intuit moves leaf-node jobs as projects and the remaining jobs as sub-customers — which is a different shape, so the mapping is a decision, not a copy.
It converts into a different kind of transaction. Payroll is where this bites. Intuit says paychecks move “as regular checks” and that “QuickBooks Online copies the current year’s paycheck information as lump sums.” Employees, payroll items and year-to-date balances are on Intuit’s list of what moves, and the paycheck-by-paycheck detail stays in the Desktop file, which the migration tool doesn’t delete or change — so before the first Online payroll run, every employee’s year-to-date is checked against the last Desktop payroll summary and tied to the returns already filed. Other records change shape too: memorized transactions convert into recurring transactions, sales orders (open and closed) move, and estimates move with active ones marked Closed and inactive ones marked Rejected — so each is checked, and any estimate still in play is reopened.
It is excluded by design. Intuit lists the Audit Trail among the reports that don’t move; Desktop’s history of who changed what is not part of the new file. Past reconciliation reports stay behind too — Intuit says reconciled transactions arrive with an R in the cleared column, which is why the first reconciliation in the new file has to be re-proven rather than trusted. Attachments move only if they are 30MB or smaller and stored on the computer’s hard drive; anything else is downloaded before the move.
And what “transfers” still has to be proved. We check the converted file for transactions that are missing or doubled, and we check open invoices and bills item by item, so the aging matches the control account in detail and not only in total. Anything that didn’t tie in Desktop — an unreconciled account, an open undeposited-funds balance — is carried across as it was and can surface as a shifted opening balance, for example in Opening Balance Equity. That account is worth reading before it is cleared: it is a summary of what didn’t convert cleanly.
Sales-tax agencies, rates and state payroll items are set up again in Online, and each state adds its own: a filing frequency, a local or county layer, a state unemployment account. The state pages list the balances and settings a migration has to carry for that state: California, Delaware, Florida, Illinois, Indiana, New York and Texas.
Every TechBrot Desktop-to-Online migration follows the same four-phase sequence — with verification built in, not bolted on.
30-minute call plus a review of your Desktop file. We identify file condition, what won’t transfer, integration scope, and any cleanup needed. We also confirm who should move now and who is genuinely better served staying on Desktop or Enterprise. Written fixed-fee scope within 3 business days.
Typical: 3 business daysPre-migration cleanup if needed, Online company prepared, conversion run. We document the Desktop baseline (trial balance, key reports, account balances) and set a defined conversion date before converting, so we have something exact to validate against.
Typical: 1–2 weeksIntegrity verification against the Desktop baseline, reconciliation validation, opening balances tied to the conversion date, app and integration reconnection, payroll and sales-tax re-setup, workflow and reporting rebuild. Every discrepancy resolved before sign-off.
Typical: 1–3 weeksTeam training on the new Online workflows, a written summary of what transferred and what was rebuilt, and optional transition to monthly bookkeeping in the new file.
Optional: ongoing engagementVerification is a comparison, so it starts before anything is converted. On the agreed conversion date we capture the Desktop baseline: the trial balance; the balance sheet and profit and loss for the open year; the accounts-receivable and accounts-payable agings; the inventory valuation summary; the sales-tax liability; the payroll liability balances and the last payroll summary; and, for every bank and credit-card account, its ending balance and the date it was last reconciled — all on the same basis, so the two files are compared on equal terms. The Migration Integrity Protocol is the seven checks the hub describes; on a Desktop-to-Online move, this is how each one is proved.
Sign-off is the written transfer summary: one row per check, with the Desktop figure, the Online figure, the difference, and what was done about it. A migration is not finished when the new file opens. It is finished when that table has no unexplained rows.
Intuit’s migration tool is real and it works for the technical data transfer. It’s what it doesn’t do that produces unusable files. Intuit also advertises that it manages migration from start to finish for QuickBooks Desktop customers (Intuit, read 2026-09-26), subject to its own terms — ask what that service checks before you rely on it.
| Capability | Professional migration | Intuit migration tool |
|---|---|---|
| Data conversion | Run correctly into a prepared Online company | Yes |
| Integrity verification | Trial balance & reports checked vs the Desktop baseline | Not performed |
| Reconciliation validation | Opening balances confirmed to the conversion date | Not performed |
| What doesn’t transfer | Reports, recurring, forms, inventory rebuilt in Online | Listed by Intuit; rebuilding is left to you |
| App & bank-feed rebuild | Feeds, payroll, payments, e-commerce reconnected | Not handled |
| Payroll & sales tax | Re-set up for Online’s different model | Not handled |
| Workflow & training | Classes/locations/projects rebuilt, team trained | None |
The first decision on an Enterprise move is how much history to move. The answer sets the scope, the verification work and the fee.
Intuit’s move article (updated 2026-09-01, read 2026-10-16) gives Enterprise files their own export steps and two choices: “Bring all your company data”, or “Bring only list and balances” if you only want to move your “customers, vendors, chart of accounts, employees, and items.” It also sets a size check first: “Confirm your Total Targets count is below 4,000,000,” and above it, “you need to condense your data before you proceed.”
Every year of transactions comes across, so reports in QuickBooks Online Advanced run back as far as the Desktop file did. It is also the most to prove: the trial balance at the conversion date, the agings item by item, inventory re-valued as FIFO, and current-year payroll that arrives as lump sums. On a large Enterprise file, condensing to get under Intuit’s limit changes the history before it moves, so that choice goes into the written scope before anything is converted.
Customers, vendors, the chart of accounts, employees and items move, and the transaction history stays in the Desktop file, which the move does not delete. There is less to convert, but the open invoices, unpaid bills and uncleared items at the conversion date are still entered in detail and tied to the Desktop baseline, so the agings in Online match it item by item.
Four questions settle it: how many years your CPA, lender or auditor expects to see in the live file; whether open invoices, bills and inventory need transaction-level history; how close the file sits to Intuit’s target limit; and whether payroll restarts mid-year. The answer is written into the scope as the conversion date and the history to move, priced inside the $2,500–$10,000+ migration band. Intuit’s Advanced migration page adds that “Some data may not be eligible for migration” and that “There’s no ongoing sync between the two,” so the Desktop file is kept as the record of everything before the conversion date.
Checked against Intuit’s transfer article and the Intuit support articles cited where each fact is used.
Migration is priced against a written scope before work begins. Each engagement is scoped as one of two tiers, as a fixed fee in writing; pre-migration cleanup, if needed, is scoped separately. Subscriptions pass through at Intuit list pricing.
A migration spans two products — the Desktop file you’re leaving and the Online company you’re building. Every TechBrot migration is delivered by a QuickBooks ProAdvisor working in Desktop files (TechBrot’s senior reviewer, a Certified QuickBooks ProAdvisor, holds the Intuit QuickBooks Certification Level 2 and QuickBooks Workforce Certification) — so nothing is lost in the gap between them. The work runs in both environments — the Desktop file is read, baselined and verified against, not just exported from. Every engagement is reviewed by a Certified QuickBooks ProAdvisor before delivery, and the preparer who runs it can continue with monthly bookkeeping in the new system if you want the relationship to continue.
The standard, every fileEvery engagement runs on three roles: a client advisor who scopes it and stays your point of contact, a senior bookkeeper who prepares your setup and monthly close in your software, and a Certified QuickBooks ProAdvisor who reviews every close before it reaches you. A U.S.-based bookkeeper is available on request; we can share their public directory profile with you.
Senior bookkeepers who specialize in rental portfolios and Xero, and specialist partner practices for trust accounting for law firms and CFO advisory. We bring the right one onto your engagement when your business calls for it, under the same standards and review.
The migration hub — reverse moves, other-software switches, cross-platform conversions, and the 7-point Migration Integrity Protocol.
The engagementIf a prior conversion left the numbers off, this is the focused post-migration fix.
The engagementWhere a broken Desktop file gets repaired before conversion. Often paired with migration.
The engagementOngoing close in your new Online file — the common next step after migration.
The engagementWhether your Desktop file is ready to convert, and the items to clean up first so balances survive the move.
The engagementThe data QuickBooks Desktop keeps and QuickBooks Online drops in a migration — and what to capture before you convert.
Read moreIntuit’s own transfer article lists what does not move: past reconciliation reports (reconciled transactions arrive with an R in the cleared column, but the reports stay behind), the audit trail, memorized reports, custom form templates (logos do move), memorized transaction groups, bank connections, units of measure, price levels, custom fields on items and employees, and progress invoices. Other records move but change shape: memorized transactions convert into recurring transactions; sales orders move; active estimates are marked Closed; paychecks arrive as regular checks and the current year’s paycheck information as lump sums; and attachments move only if they are 30MB or smaller and on the computer’s hard drive. Inventory is imported as FIFO from a start date you set, and Intuit says Online may calculate inventory values and cost of goods sold differently, so reports may not match exactly. Desktop’s class-and-job structure maps differently to Online’s class, location, and project model. A proper migration documents what won’t transfer in advance and rebuilds the essentials in Online — exactly the work the automated tool skips.
Transaction history transfers, but it must be verified rather than assumed — Intuit itself asks you to review your data after the move. We check the converted file for anything dropped, duplicated, or misclassified, and balances can shift if the original file had unreconciled accounts or data-integrity issues. Our migration includes a full integrity check — comparing trial balances, account balances, and key reports in Desktop against the converted Online file — and reconciling any differences before sign-off. The goal is a converted file you can actually trust, not just a file that opened.
Not as a whole. Intuit no longer offers non-subscription (lifetime or perpetual) versions of Desktop Pro, Premier, and Mac, and after September 30, 2024 it stopped selling new Desktop Pro Plus, Premier Plus, Mac Plus, and Enhanced Payroll subscriptions in the U.S. — existing subscribers can still renew. Older versions are discontinued: Intuit discontinued Desktop 2023 after May 31, 2026, after which payroll tax tables, bank feeds, and security updates stop for it. Desktop 2024 — Pro Plus, Premier Plus, and Enterprise Solutions — has continuous support: Intuit says it won’t be discontinued in May 2027, there’s no sunset deadline for the release, and it maintains version 24.0 through periodic in-product updates. Intuit still sells Enterprise subscriptions. For a small business, migrating is a business decision — remote access, integrations, or an accountant who works in QuickBooks Online — not a deadline, and staying on Desktop 2024 is a legitimate choice.
A standard single-entity migration with verification and reconciliation typically completes in two to four weeks. Larger files, multiple entities, heavy third-party integrations, or significant pre-migration cleanup extend that to four to eight weeks. The largest variable is file condition: a clean Desktop file converts faster than one that needs cleanup first. The timeline is fixed in the written scope before work begins.
ProAdvisor-led migration is priced by scope, not by hour. A standard single-entity migration with integrity verification and reconciliation sits toward the lower end of the $2,500 to $10,000+ range. Complex migrations — large files, multiple entities, extensive integrations, or workflow rebuild and team training — sit toward the upper end. If the Desktop file needs cleanup before conversion, that is scoped separately. Every engagement is fixed-fee against a written scope — for a quote, book a free call or dial (877) 751-5575.
Intuit’s tool handles the raw data conversion, and for a very simple, clean file it can be enough. Intuit also advertises that it manages migration from start to finish for QuickBooks Desktop customers, subject to its own terms — ask what that service checks. The risk is everything around the conversion: the tool does not verify the data landed correctly, does not reconcile balances, does not reconnect bank feeds and app integrations, does not reconfigure workflows for Online’s different structure, and does not train your team. The conversion is the easy 20 percent; the verification and rebuild are the 80 percent that determine whether the new file works. A ProAdvisor owns the whole outcome, not just the file copy.
Tell us what you’re moving from and how much history matters. We’ll tell you what the move involves and what has to be checked.
What happens when you call