QuickBooks Online Advanced Setup and Rollout: A 4-Phase Migration Plan
Setup Rollout: Why the Plus to Advanced Migration Needs a Real Plan
Here is the trap. QuickBooks Online Advanced looks, on the surface, like the same product as Plus with a few extra menu items. The chart of accounts is identical. The bank feed works the same. Invoicing, billing, reconciliation, payroll connection — all unchanged. So the natural reaction is to flip the switch and move on.
The problem is that Advanced is not a feature upgrade. It is a permissions and workflow upgrade. The new pieces — custom roles, custom fields, workflows, batch transactions, the report builder — only pay back if you wire them into how your team actually books transactions. For Setup Rollout, drop them in on top of an unclean Plus file and you will get the same mess, just with more buttons.
The four-week plan exists because the order of operations matters. You cannot build custom roles before you have decided who does what. You cannot build workflows before you have decided what gets approved by whom. You cannot configure custom fields before you have decided what the books should be tracking that they are not tracking today. Each phase depends on the one before it. Compress them and you skip the decisions.
We see the same migration mistake every month. A client upgrades on a Friday, the office manager spends the weekend clicking through every new menu, and Monday the controller is staring at three new custom roles, two unfinished workflows, and seven custom fields nobody can explain. By the end of the week we are unwinding it. The four-phase plan is what we wish those clients had used.
One uncomfortable point: if your Plus file is a mess, fix the mess first. The Advanced features that matter most (custom fields, workflows, role-based access) all assume the data underneath is clean. A bookkeeping cleanup before migration is cheaper than a cleanup after migration, because before migration you only have to fix Plus-tier mistakes. After migration you also have to fix the new mistakes Advanced let you make. See our QuickBooks Online bookkeeping guide for the cleanup checklist we run first.
The cost math is straightforward. Advanced sits at roughly $200 a month at list price versus about $100 for Plus. A well-rolled-out migration pays that delta back in the first month through reclaimed bookkeeper hours. A bad rollout costs you the delta plus the hours you spend untangling it. The difference between a good and bad rollout is almost entirely whether you followed the order.
Phase 1 — Subscription Switch and Initial Audit (Week 1)
Week 1 is the boring week. Nothing visible changes for the team. The work is all in the background: flip the subscription, audit the file, capture baselines, and write down what is broken so you know what to fix.
Day 1: The subscription switch. Sign in as the primary admin, go to the gear icon, click Account and Settings, then Billing and Subscription. Click Upgrade and pick Advanced. The change is immediate — New menu items appear within seconds, no logout required. Confirm the new billing cycle on the receipt screen. Intuit prorates the difference, so the first invoice is usually a partial month plus the full Advanced month from now on. Intuit’s upgrade documentation walks the exact click path if your menu looks different.
Day 2: File audit. Pull three reports and save PDFs of each. Trial Balance as of today. Profit and Loss for the trailing 12 months. Balance Sheet as of today. These are your baselines. If anything changes during migration, you compare against these. Also run the Audit Log (Reports menu, search “Audit Log”) and skim the last 30 days. Look for transactions made by users who should not have permission, deletions, or category changes that nobody owns. Note them in a one-page audit document.
Day 3: Chart of accounts review. Export the chart of accounts to Excel. Mark every account as keep, merge, or retire. Most Plus files we audit have between 15 and 40 percent dead accounts — old vendor reimbursement accounts, duplicate expense categories, accounts created for one transaction in 2019 and never closed. Retire dead accounts now, not later. After the chart is clean, you will know what custom fields you actually need in Phase 2.
Day 4: Class and location review. Same exercise. Export the class list and the location list. Mark each entry as keep, merge, or retire. Plus files often carry forward classes from a previous business model. If you have a class called “Retail”. And you stopped doing retail in 2022, retire it. Active classes only.
Day 5: User and access inventory. Open Manage Users (gear icon, Manage Users). Make a spreadsheet of every user, their current role, and what they actually do in the file. Mark users you would remove if you were starting fresh. This list feeds the Phase 2 custom role design directly. The IRS recordkeeping baseline at irs.gov/businesses/small-businesses-self-employed/recordkeeping requires you to know who touched the books and when, so this audit is also a compliance step.
End-of-week checkpoint. By Friday of week 1 you should have: subscription on Advanced, three baseline reports saved, a one-page audit doc, a cleaned chart of accounts, cleaned class and location lists, and a user inventory. If any of those are not done, do not start Phase 2 on Monday. Slip the schedule by a week. Phase 2 builds on Phase 1. Missing pieces here become problems there.
Phase 2 — Custom Roles, Custom Fields, Workflows (Weeks 2-3)
This is the heaviest phase. Two weeks of configuration work, done in a specific order: roles first, fields second, workflows third. The order matters because each feature uses the one before it.
Custom roles (early week 2). Open the gear icon, Manage Users, then Roles. Click Add Role. Build one role per real job, not one per person. Most clients need four to six custom roles: Owner (full access), Controller (full access except billing), Senior Bookkeeper (transactions and reports, no banking), Junior Bookkeeper (transactions only, no reports beyond their own work), AP Clerk (vendors and bills only), AR Clerk (customers and invoices only). For a deeper walkthrough see our QBO Advanced custom roles guide.
Permission granularity is the part people get wrong. Advanced lets you control access at the action level: view, create, edit, delete, print, send for each module. Use it. The default Plus roles bundle too much. A junior bookkeeper who can delete transactions is a risk. One who can only create and edit is not. Spend the time on the permission matrix during role design and you save a year of audit-log surprises.
Assign each existing user to the appropriate new role. Test by signing in as one user from a different browser session and walking the menus. If anything they should not see is visible, fix the role definition, not the user. The goal is that the role is correct for everyone who will ever fill it, not just for the person who happens to fill it today.
Custom fields (mid week 2). Open gear icon, Custom Fields. Advanced allows up to 48 custom fields across customers, vendors, items and projects. Use no more than 15 to start. The temptation is to add a field for every piece of data the team has ever wanted to track. Resist it. Each field is a maintenance liability — somebody has to fill it correctly on every transaction, or the field becomes noise.
Three custom fields earn their keep on most files. Customer segment (Enterprise, Mid-Market, SMB) on the customer record — powers segment-level reporting later. Project code on transactions — ties expenses to the work for clients doing project work. Vendor 1099 status on the vendor record — saves real time at January-end when you produce Form 1099-NEC. Anything beyond those three should fight for the slot. See our QBO Advanced custom fields guide for the full design pattern.
Workflows (week 3). Open gear icon, Manage Workflows, then Templates. Build five workflows in week 3, one a day. Day 1: overdue invoice reminders at 7 and 30 days for invoices above $250. Day 2: bill approval routing for bills above $1,500. Day 3: monthly customer statements on the first of the month. Day 4: internal alert on bank deposits above $10,000. Day 5: journal entry approval for entries above $500 not created by the controller. The detailed configuration for each lives in our QBO Advanced workflows guide.
Build them one at a time, not in a batch. Test each one before moving on. Send yourself a test trigger and confirm the email or notification arrives. Workflows do not retroactively apply, so a workflow built Monday only fires on events from Tuesday forward. That detail trips up first-time builders.
Reporting templates (end of week 3). Use the custom report builder to save three reports as templates: monthly P&L by class, AR aging by customer segment, and a bill aging report by vendor. These are the reports the team will use most often in week 4 and beyond. Building them now means they are ready when the cutover happens.
Phase 3 — Training the Team (Week 3)
Training happens in parallel with the back half of Phase 2, not after it. Run two sessions, split by role.
Session 1: Bookkeepers (90 minutes, midweek 3). Walk through the new role-based menus they will see post-cutover. Show them the custom fields they now need to fill on transactions. Demonstrate the workflows that affect their work — specifically, what happens when they create a bill above the routing threshold (it goes to the approver, they get a confirmation, they do not need to follow up manually). Walk through the new audit log view and explain that every action is logged with their name. End the session with five practice transactions in a sandbox copy of the file.
Session 2: Approvers and reviewers (60 minutes, end of week 3). Different audience, different content. Approvers care about the inbound notifications, the approval interface, and the audit trail. Show them what an approval request looks like in their email and in QBO. Show them the bill approval queue. Show them how to reject with a note, not just approve. Approvers also need to see the dashboard and report builder, so spend the last 20 minutes on the custom reports that were built in Phase 2.
What not to do. Do not train everyone in one giant session. The bookkeeper content bores the controller and the controller content overwhelms the junior bookkeeper. Splitting the sessions by role respects everyone’s time and produces better recall. Do not skip training because “the team will figure it out.” We have rolled out enough of these to know they will not figure it out. They will work around the new features instead of using them, and the migration will fail.
Documentation handoff. At the end of training, give every user a one-page reference: their role name, the modules they have access to, the workflows that affect their work, and the custom fields they are responsible for filling. Keep it short. A one-page reference gets read. A 30-page manual gets ignored.
The hidden training step. The owner usually needs the most training, not the least. Owners often have full access and a habit of clicking around. After migration, give the owner a brief specifically on what has changed for them: the new report builder, the workflow queue if they are an approver, and which custom fields they should be paying attention to on dashboards. Skipping this brief is how the owner ends up calling the controller at 9 p.m. asking where the old menu went.
Phase 4 — Production Cutover and First-Month Watch (Week 4)
Week 4 is the live week. The new configuration goes from “configured but quiet”. To “running every transaction.”
Monday: Enable workflows. Go through each workflow and flip the Enable toggle. Confirm each one shows status Enabled in the workflow list. Do this in the morning, not after hours — you want the team awake and watching for the first few hours of real-time firing. Most workflows do not fire on day 1 because the trigger conditions have not yet been met. That is expected. Do not assume something is broken just because nothing happened.
Tuesday: Switch users to new roles. Up to this point, users have been on their old Plus roles even though Advanced was active. On Tuesday, switch every user to their new custom role. Do this in Manage Users, one user at a time, and have each user sign in to confirm they can see what they need to see. If a user reports something missing, fix the role definition immediately. Do not let it sit overnight.
Wednesday and Thursday: Watch the audit log. Pull the audit log twice a day Wednesday and Thursday. Look for two patterns: workflow actions firing on records that should not have triggered them (an over-broad condition), and users hitting permission walls (a role that is too restrictive). The first fix is the workflow conditions. The second is the role definition. Both are easy adjustments if caught in week 4 and harder if they sit for a month.
Friday: First weekly review. Schedule a 30-minute team standup. Each user reports one thing that worked and one thing that did not. Capture the list. The “did not work”. Items are your week 5 cleanup list. By the end of this standup the migration is technically complete but the watch is not over.
The first-month watch (weeks 5 through 8). The migration is not actually done at the end of week 4. The first month-end close after cutover is the real test. Specifically watch: did the close take the expected number of days. Did any workflow fire on a journal entry the controller did not expect. Did the AP clerk’s new role allow them to do everything they needed to do without administrator intervention. Did the custom fields get filled on every transaction or were they left blank. Did the new reports tie to the trial balance.
If everything checks out at the first month-end, the migration is real. If something does not check out, fix it before the second month-end. The first month is the window where adjustments are cheap. After that, the team’s habits harden around the current configuration and changes start to feel like rework even when they are clearly needed.
The 60-day formal review. Sixty days post-cutover, sit down with the team for a one-hour retrospective. What workflows are firing more than expected. What custom fields are getting filled in less than 50 percent of transactions. What roles need tweaking. The 60-day review is the final calibration. After that, the configuration runs on autopilot until a business change forces another cycle. For ongoing operating practices once you are live, see our QBO Advanced operating manual.
What Breaks During Migration and How to Fix It Fast
Eight things break in roughly this order. Knowing the order means catching them earlier.
1. Bank feed authentication. The most common day-1 issue. The bank feed sometimes loses its OAuth handshake when the subscription tier changes. Symptom: bank feed shows “needs attention”. Or stops pulling new transactions. Fix: open Banking, click the affected account, re-authenticate. Takes 90 seconds. Catch it on day 1 by confirming each bank feed has pulled at least one transaction since the upgrade.
2. Custom report templates from Plus do not all migrate cleanly. A handful of saved custom reports built on Plus rely on field combinations that Advanced reshuffles in the report builder. Symptom: the report runs but a column is empty or misnamed. Fix: rebuild the report in the new Advanced builder, save it under the same name, and delete the old version. Plan to spend two hours on this in week 1.
3. Recurring transaction owners. Plus assigns recurring transactions to a user. If that user gets switched to a new custom role in week 4, some recurring transactions stop firing because the new role lacks the create permission for that transaction type. Symptom: an expected recurring bill does not post on its scheduled date. Fix: reassign the recurring transaction to a role that has the right permission, or add the permission to the role.
4. Integration API tokens. Third-party apps connected via API (a payroll provider, an e-commerce platform, a tax tool) sometimes lose their permission scope when the subscription tier changes. Symptom: the integration shows a connection error or stops syncing. Fix: disconnect and reconnect the integration. Pay attention to whether the integration needs to be reauthorized by an admin specifically.
5. Custom field defaults. Newly created custom fields are blank on existing records. Symptom: a report grouped by a custom field shows half the data in an “Unassigned”. Bucket. Fix: bulk edit historical records to fill the field, or accept that the field only works prospectively for new transactions. We usually pick the second option and tell the team to fill it from now on.
6. Workflow over-firing. A workflow built on a too-broad condition fires more than expected. Symptom: customers get reminder emails they should not have gotten, or the approver gets flooded. Fix: tighten the condition. Add a dollar threshold, a date filter, or a status filter. Workflows do not retroactively undo their actions, so any over-firing in the first week needs to be apologized for in person to affected customers.
7. Permission gaps for routine work. A new role is too tight and the user cannot do something routine. Symptom: a bookkeeper tries to record a journal entry and gets a permission denied error. Fix: add the permission to the role. Do not give the user a different role to work around it — the next person in that role will hit the same wall.
8. Audit log volume shock. Advanced logs more actions than Plus by default. Symptom: the audit log feels noisy and hard to scan. Fix: get used to it. The volume is a feature, not a bug. Build the habit of filtering the log by user or date when you are reviewing.
One more, less common but worth mentioning. If your business is bound by recordkeeping rules under IRS Publication 583, document the migration itself. A short memo describing the date of the cutover, the users affected, and the configuration changes is enough to defend the file in an audit. It also helps the next person to inherit the file understand what happened and why.
Related Services from The Reed Corporation
Helpful Guides You Might Also Like
Sources & References
Frequently Asked Questions
How long should a QBO Plus to Advanced migration actually take?
Four weeks is the right answer for almost every small and mid-sized business. We have run dozens of these migrations and the timeline has held remarkably steady across client sizes, from a $1M consulting firm with four QBO users up to a $30M product business with twenty.
Why four weeks and not two. The migration itself is not technically complex. You can run the subscription switch in under five minutes. You can configure a custom role in fifteen minutes. You can build a workflow in twenty. So a fast operator could, in theory, do the whole migration in a long weekend. We have watched several clients try. None of those weekend migrations have ended well.
The reason four weeks works and a weekend does not is not the configuration time. It is the decision time. Each configuration choice requires a decision the team has to live with. What permission does the AP clerk get? What is the bill approval threshold? Which custom fields earn their slot among the limited 48? Those decisions need conversation, not just keystrokes. Compress the timeline and you compress the conversations, and the result is decisions that look fine on paper but break in practice.
Week 1 is the audit and switch week. The subscription change takes minutes. The audit takes the rest of the week. You are pulling baseline reports, cleaning the chart of accounts, reviewing classes and locations, inventorying users, and capturing what is broken in the current Plus file. Skip this week and you migrate the mess instead of fixing it. We have seen exactly one client try to skip week 1 and they ended up spending six weeks cleaning up afterward instead of one week cleaning up before.
Weeks 2 and 3 are the configuration weeks. Custom roles take two to three days because the permission matrix needs real conversation across the team. Custom fields take a day if you stick to the discipline of 15 or fewer. Workflows take a day each because you build them one at a time and test each one before moving on. Report templates take half a day. That adds up to about ten working days, which is the back half of week 2 and all of week 3.
Week 3 is also training week. Training overlaps with configuration. The bookkeeper session happens midweek 3, after the custom roles and fields are configured but before workflows go live. The approver session happens end of week 3. Each session is 60 to 90 minutes. Training cannot be shorter because the team has to actually practice the new flows in a sandbox, not just watch a slide deck.
Week 4 is cutover and watch. The flip happens on Monday and Tuesday. The watch runs Wednesday through Friday. The first month-end close in week 8 or 9 is the real test, but the active hands-on watch is week 4.
When four weeks is too short. If your Plus file has serious cleanup debt (more than 25% of accounts to retire, more than 10 users to re-permission, multiple integrations to migrate), add a week to the front for cleanup. If your team is small and people are wearing multiple hats, add a week to the configuration phase to spread the load. If your business is going through a parallel event — an acquisition close, an audit, a financing round — do not start the migration until the event is past. We do not migrate clients in active audit windows. The risk-to-reward math is bad.
When four weeks is too long. Very rarely. A clean Plus file with two users, a single workflow, and no integrations can theoretically be migrated in two weeks. We still recommend the four-week plan because the training and watch phases do not shrink with the file size — they shrink with the team size, which is what costs the time.
The hidden time cost: the calendar. Four weeks of elapsed time does not mean four full weeks of work. The total work hours for a typical migration are 30 to 50 hours spread across the internal team and an external advisor. The reason it takes a month of calendar time is that the work has to fit around the team’s actual job. Bookkeepers do not have eight hours a day to spend on migration. They have one or two. Stretching it across four weeks respects that constraint.
What goes wrong when teams try a compressed timeline. The same thing every time. Roles get built without permission testing. Workflows get built with conditions that are too broad. Training gets crammed into one session that nobody remembers. The cutover happens with no audit-log watch. Two weeks later the team is reporting problems that should have been caught and fixed in week 4. By the time the problems get resolved, the elapsed clock is six or eight weeks — longer than the four-week plan would have been — and the team’s confidence in the new tool has taken a hit it does not need to take.
The dependency chain you cannot shortcut. Every phase produces an output that the next phase needs. Phase 1 produces a cleaned user inventory; Phase 2 needs that inventory to design custom roles. Phase 2 produces the role and field configuration; Phase 3 needs that configuration to train the team. Phase 3 produces a trained team; Phase 4 needs that trained team to staff the cutover and the watch. If you try to run phases in parallel, the upstream output is incomplete when the downstream phase needs it, and the downstream work has to be redone.
How the timeline shifts when more than one entity is migrating. If you have a parent and a subsidiary on QBO and both are migrating together, the timeline grows but not linearly. Two related files migrating in parallel run about 1.5x the duration of a single file, not 2x, because the audit and training work shares context. Five unrelated files migrating in parallel under one CFO run about 3x the duration of one file. The bottleneck is the human time on the team that owns the configurations, not the QBO product itself.
What signals a successful four-week landing. At the end of week 4, three things should be true. The first month-end close (which falls in week 7 or 8) goes through cleanly with the new workflows firing. The audit log shows no over-firing of workflows in the watch period. Every user reports they can do their job without permission errors. If those three are true, the migration is done. If any of the three is not true, you are still in the watch period and the migration is not yet finished, regardless of the calendar.
One last point. If you are not sure whether you can run the four-week plan internally, we run them as a fixed-fee engagement through our client accounting services practice. The deliverable is a configured, trained, cutover Advanced file at the end of week 4 and a checked-in clean first-month close in week 8. The full breakdown of what we touch in the migration is in our QuickBooks Online Advanced overview.
Do I need to pause my bookkeeping during migration?
No. And actively trying to pause it would create more problems than it solves. The team should keep booking transactions, reconciling bank feeds, sending invoices, and paying bills through the entire four-week rollout. What you pause is structural change to the configuration, not the day-to-day work.
Why pausing the bookkeeping would be wrong. The Plus-to-Advanced switch does not migrate data, change schemas, or take the file offline. It is a billing-tier change that exposes new menus and capabilities. Every transaction recorded before and after the switch lives in the same data model. So there is no maintenance window to honor. If you stop booking transactions for a week, you are creating a backlog that you will have to clean up later for no reason. The system did not need the rest. You just gave the team a week off.
The closest analogy is upgrading a Microsoft Office license from Standard to Pro. The new features show up immediately, the old features keep working, and there is no reason to stop writing documents while the upgrade processes. QBO Plus to Advanced is the same.
What you actually pause: structural changes. During the four-week migration window, freeze the following.
- No new accounts added to the chart of accounts (except for things you absolutely cannot defer)
- No changes to the class or location lists
- No new users added or removed (handle these as part of the week 1 audit and week 4 role assignment)
- No new third-party integrations connected
- No changes to bank feed connections (except to fix breakage)
- No major reconciliation campaigns or historical cleanup pushes
The reason to freeze these is that the migration plan assumes the file structure on day 1 is the same as the file structure on day 28. If somebody adds three new accounts in week 2, the chart of accounts review you did in week 1 is stale. If somebody changes a class definition in week 3, the custom field design you built around classes in week 2 is broken. The freeze is not about being precious. It is about not undoing your own work.
What you do not pause: routine bookkeeping. Keep booking. Bank feeds keep reconciling. Bills keep getting recorded. Invoices keep getting sent. Payroll keeps running. Customer payments keep applying. Vendor payments keep getting cut. All of that flows through Plus features that work identically under Advanced. The team’s habits do not need to change during the migration. They change at the week 4 cutover when the new features become real.
The exception: bulk operations. If you have a planned bulk cleanup project — reclassifying a thousand transactions, retroactively assigning classes to historical data, or running a big batch journal entry exercise — pause it. Pick it up after week 4. The reason is that those bulk operations create a flood of audit-log entries that drown out the new workflow events you need to be watching during the cutover. Run the bulk work in week 5 or later, after the first weekly review and after the audit log is being scanned for genuine migration issues, not background noise.
The other exception: a planned major event. If you have an acquisition closing, a financing due-diligence pull, or an audit fieldwork visit scheduled during the migration window, postpone the migration. The four-week plan needs the team’s focus, and an event with a deadline will win every time. We do not start migrations in active audit windows. We have done one and we regretted it.
What about month-end? Month-end falls inside the four-week window for most clients because four weeks usually crosses one. That is fine. Run month-end as you normally would using the Plus-tier workflow (manual approvals, manual reminders, the existing role structure). The first month-end on the new Advanced configuration is week 8 by design — that is the first-month watch period. Forcing the new configuration to handle a month-end during week 3 or 4 is asking for trouble. The workflows and roles are not yet tested in production.
What if a critical configuration change comes up mid-migration? Sometimes a real business need cannot wait. A new client onboards and needs a custom class. A new vendor relationship requires a new account. Handle these as one-offs. Document them in the audit log of changes (a one-line note in your migration tracking doc), make the change, and continue with the migration plan. The point of the freeze is to prevent unnecessary churn, not to block genuine business needs.
What if the team panics about working in the file while it is “in migration”? Reassure them. The file is not in a fragile state. Advanced is fully production-ready from the moment the subscription switches. The configuration work happening in the background does not threaten any transaction or data. The worst-case scenario from working in the file during migration is that you book a transaction that later gets routed through a workflow when the workflow goes live in week 4 — which is fine, because that is what the workflow is for.
The clearest sign you are doing it wrong. If your team is asking permission to record routine transactions during the migration, the project has communicated badly. The default should be: keep working, defer to the migration lead on structural changes only. If you find that the migration lead has become a bottleneck for every routine bookkeeping action, the team is over-pausing. Push back on the pause culture and clarify what is actually frozen versus what is business as usual.
What happens to month-end if it lands inside the four-week window. Month-end during weeks 1, 2, or 3 runs on Plus-tier configuration even though the subscription is Advanced. The team uses the same close checklist they have always used. No workflows fire because they have not been built yet. No custom roles apply because users are still on the old roles. The close is functionally a Plus-tier close. This is by design. The first close on real Advanced configuration is intentionally pushed to week 7 or 8 so that the cutover is not happening on top of close pressure.
What to communicate to the team on day 1. A two-sentence Slack or email at the start of week 1 prevents most of the confusion. Sentence one: we are upgrading to QBO Advanced and rolling out new features over the next four weeks. Sentence two: keep working exactly as you do today. You will be trained on the new features in week 3 and they go live in week 4. That message saves a lot of “what do I do differently?”. Questions in the first half of the migration. The answer is nothing, until week 4.
What pausing the bookkeeping would actually cost. If you took a week off in the middle of migration, you would have an extra 200 to 400 transactions piled up depending on your transaction volume. Those transactions would need to be booked under time pressure, which is exactly when bookkeeping mistakes happen. The cost of catching up on a week of skipped bookkeeping is materially higher than the cost of doing it as you go. The migration plan is designed to fit around routine work, not replace it.
For the underlying bookkeeping rhythm we recommend running alongside Advanced, see our QuickBooks Online bookkeeping guide.
What happens to my custom QBO Plus configurations during the upgrade?
Almost everything carries over without a touch. The Plus-to-Advanced upgrade is additive, not migratory. Your existing data, settings and saved templates all stay in place. Advanced adds new capabilities on top of what Plus already does. It does not replace any of it.
What carries over intact.
- Chart of accounts — every account, parent and sub, in the exact hierarchy you built
- Customer list, including all custom data, payment terms, default tax rates, and attached files
- Vendor list, including 1099 settings, account numbers, and default expense categories
- Product and service items, including pricing, SKUs, income and expense accounts
- Classes and locations, including parent-child relationships
- Recurring transactions, including their schedule and assigned user
- Bank feeds and their reconciliation history
- Bank rules built in Plus
- Invoice and estimate templates, including custom branding and field layouts
- Sales tax setup, including configured tax rates and jurisdictions
- Payroll setup (if connected through QuickBooks Payroll)
- All historical transactions, all attachments, all journal entries, all reconciliations
- Connected third-party apps via the app marketplace (with minor exceptions noted below)
- Audit log history
- Saved custom reports (with rare formatting exceptions noted below)
What is new and starts empty. The Advanced-only features are exposed in the menu but begin in a default-empty state. They do not auto-configure themselves based on your Plus setup.
- Custom roles. Until you build them, your users keep their Plus roles. The Plus roles continue to function in Advanced — Standard User, Limited User, Reports Only, Time Tracking Only — just with the same permission scope they had in Plus. Building custom roles is optional. You can run Advanced indefinitely on Plus-tier roles. We do not recommend it because the whole point of Advanced is the detailed role control, but it is technically supported.
- Custom fields. Plus has limited custom field support (typically three fields on sales forms). Advanced expands that to 48 fields across multiple modules. Your existing Plus custom fields carry over and continue to work. The new field slots are empty until you configure them.
- Workflows. Plus has a stripped-down workflow set (invoice reminders only). Advanced exposes the full engine. The Plus invoice reminders, if configured, carry over and keep firing. Everything else — bill approvals, deposit notifications, custom routing — starts empty.
- Batch transactions. Empty until used.
- Custom report builder. Available from day 1. Your Plus saved reports continue to work alongside the new builder.
- Revenue recognition. Available from day 1 but starts inactive. You configure it as a separate setup step.
- Performance Centre. Available from day 1 with default widgets. You customize what appears.
- Restore from backup. Advanced enables continuous backup and on-demand restore. The backup retention starts on the day you upgrade. You cannot restore to a point before the upgrade.
The rare exceptions where something needs attention.
1. Some saved custom reports show formatting drift. A small percentage of Plus saved reports rely on field combinations that Advanced rebuilds slightly differently in the new report engine. The report still runs but a column might be empty, a total might calculate slightly differently, or a grouping might collapse. The fix is to rebuild the report in the new Advanced builder. Plan to spend two to three hours in week 1 reviewing every saved custom report and confirming it still produces the expected output.
2. A small subset of third-party app integrations need to re-authenticate. Most apps in the marketplace handle the tier change without any user action. A few — usually older apps or apps with their own role-based access logic — will throw an authentication error after the tier change. The fix is to disconnect and reconnect the integration, which usually takes under five minutes per app.
3. The bank feed sometimes needs a quick re-authentication. One out of every three or four migrations sees at least one bank feed connection request a fresh OAuth handshake after the tier switch. Symptom: “needs attention”. Warning on a bank account in the Banking tab. Fix: click the account, click the re-authenticate prompt, sign in to the bank, done. Takes ninety seconds.
4. Recurring transactions assigned to a user whose role changes in week 4 can stall. This one bites because it does not surface until weeks after the upgrade. A recurring bill scheduled to post under user X stops posting because user X got moved to a custom role in week 4 that lacks the create permission for bills. The fix is to either update the recurring transaction owner or grant the permission to the new role. Catch it by running a recurring-transactions report at the end of week 4 and confirming each one fired on its scheduled date.
5. Recurring journal entries follow the same pattern. Same issue as recurring bills. Same fix.
What does not happen. You do not lose any data. You do not lose any settings. You do not lose any integrations except for the rare re-auth cases above. You do not have to re-enter customers, vendors, products, or transactions. You do not have to rebuild your bank rules or your sales tax setup. The Plus-to-Advanced upgrade is not a re-implementation. It is a tier bump.
What about downgrade? Covered in a separate FAQ below, but the short version: yes you can downgrade. The Advanced-only configurations stop functioning when you do. Your data stays.
The configuration audit checklist for week 1. To confirm nothing carried over wrong, run this list.
- Open the chart of accounts. Confirm count matches the pre-upgrade Plus export.
- Open customer list. Confirm count matches.
- Open vendor list. Confirm count matches.
- Open the products and services list. Confirm count matches.
- Open Banking. Confirm every bank account shows a green “linked”. Status.
- Open Apps. Confirm every connected app shows a healthy connection.
- Open Sales tax. Confirm the configured agencies and rates match.
- Open Payroll. Confirm the payroll dashboard loads without error.
- Run a trial balance for today. Confirm it matches the pre-upgrade trial balance you saved.
- Open every saved custom report. Confirm each runs and produces a result that looks correct.
If all ten check out, the upgrade carried everything over cleanly and you can move into Phase 2 with confidence. If any check fails, fix it in week 1 before adding Advanced-only configuration on top. For the per-feature implementation steps once the upgrade is clean, see our QBO Advanced operating manual.
Can I downgrade back to Plus if Advanced is not working out?
Yes. Intuit lets you downgrade through the same Billing and Subscription menu you used to upgrade. The change is usually immediate. Your data stays intact. What you lose is access to Advanced-only features, and the configurations you built on those features become either read-only or invisible. So technically the answer is “yes you can,”. But practically the answer requires understanding what gets stranded.
How the mechanical downgrade works. Sign in as the primary admin. Open the gear icon, click Account and Settings, then Billing and Subscription. Click the change-plan link and select Plus. Confirm the change. Intuit prorates the difference and credits the unused portion of your Advanced subscription. The next billing cycle hits at the Plus rate. The new menus disappear from the gear icon and from the main navigation almost immediately.
What you lose access to.
- Custom roles. Any custom role you built collapses back to a standard Plus role. The user is reassigned automatically to the nearest equivalent Plus role (Standard User, Limited User, etc.). The detailed permissions are gone. If you built custom roles around very specific permission combinations, those combinations are no longer expressible after downgrade.
- Workflows. Any workflow you built stops firing immediately. The configurations are saved server-side in case you re-upgrade, but they do not run. Plus retains only invoice reminders as a workflow type, so any workflow that handles bills, deposits, journal entries, statements, or any non-invoice trigger is dark.
- Custom fields. The custom fields you configured beyond the Plus limit (typically 3 on sales forms) become read-only. Data already entered in those fields persists in the database but cannot be edited or used as a report filter. New transactions cannot have those custom field values set. You essentially have ghost fields holding historical data with no path to update them.
- Batch transactions. The feature is gone. Existing transactions remain. You just cannot create new ones in batch.
- Custom report builder — partial loss. Plus has a more limited report builder. Reports you built that used Advanced-only columns (custom fields beyond the Plus limit, certain forecasting fields, certain audit-log integrations) will not run after downgrade. They show an error or hide the unavailable column. You can rebuild them in the Plus-tier builder if you need the underlying data, but you may not be able to reconstruct the exact view.
- Revenue recognition. Lost. Any rev rec schedules you built are dropped. Historical journal entries from prior periods stay. The engine that generated them is gone.
- Performance Centre. Lost. Widgets disappear. The dashboard reverts to the Plus default.
- Continuous backup and on-demand restore. Lost. Plus does not include the backup feature. Any backups taken while on Advanced remain accessible for a short retention window, but new backups stop.
- User seat count. Plus caps at five users (plus accountant seats). If you had more than five named users on Advanced and you downgrade, you are forced to remove the excess users at the time of downgrade. Intuit prompts you for which to remove. There is no grace period.
What you keep. Everything in the data layer. Chart of accounts, transactions, customers, vendors, products, classes, locations, attachments, recurring transactions (subject to user availability), invoice and estimate templates, bank feeds, bank rules, sales tax setup and audit log. All of it.
The 60-day window. Most clients who downgrade do so within the first 60 days. That is for two reasons. First, the immediate frustration of new tools is highest in the first month, and if the team has not bought in by week 8, downgrade feels like the cleanest reset. Second, after 60 days the team starts to build real dependencies on Advanced features — workflows that route a meaningful share of bills, custom fields that drive reporting, custom roles that segregate duties — and unwinding those dependencies starts to feel like an active loss.
If you are seriously considering downgrade in month 1 or 2, run the four-phase plan honestly first. Most failed migrations we see are not Advanced-the-product failures. They are rollout failures. The product is doing what it advertises. The team has not been brought along. A second pass at training and a re-design of the workflows often fixes what looked like a downgrade-worthy situation.
When downgrade is genuinely right. A few situations call for it.
- The business has shrunk and the user seat count, transaction volume, and complexity no longer justify the Advanced delta. We see this with seasonal businesses, businesses going through a wind-down, or businesses that have offloaded a division.
- The features you needed Advanced for (workflows, custom roles) have been replaced by a dedicated tool (Bill.com, Ramp, Workato). Once the dedicated tool is doing the heavy lifting, the Advanced subscription is a duplicate spend.
- The team genuinely cannot adopt the new product despite a real training effort. This is rare but it happens, usually in firms where the bookkeeper has been doing things the same way for fifteen years and is closer to retirement than to learning a new permission model.
The hidden re-upgrade cost. If you downgrade and then re-upgrade later, you do not get your configurations back automatically. Intuit retains them server-side for a window (the documentation says 90 days. In practice we have seen them retained longer in some cases). After that window, custom roles and custom fields beyond the Plus limit need to be rebuilt from scratch. So a “let’s try Plus for a few months and see how it goes”. Approach has a hidden re-implementation cost on the way back up.
The decision framework. Before downgrading, ask three questions. Have we genuinely run the four-phase plan with full training and a real first-month watch? If no, do that first. Have we measured the impact of the Advanced features (hours saved, DSO change, reporting accuracy)? If no, measure it before deciding. Have we considered offloading the Advanced-only features to a dedicated tool instead of downgrading wholesale? If no, evaluate.
If the answer to all three is yes and the math still says downgrade, do it. The mechanic is clean, the data is safe, and the path back up is open. For ongoing strategy questions like this we cover the broader product decision in our QuickBooks Online Advanced pillar.
When should I bring in a CPA firm versus handle migration internally?
The honest answer: most internal teams can run the migration themselves if they have a clean Plus file, a knowledgeable internal owner, and time on the calendar. The reason to bring in a CPA firm is usually not that the migration is technically beyond the team. It is that the migration coincides with a business event the team cannot absorb on top of their day jobs.
Signal 1: The Plus file has real accumulated debt. Look at the chart of accounts. If more than 25 percent of the accounts are dead, duplicated, or miscoded, the migration starts with a cleanup project. Cleanup projects are best done by someone who is not also closing the month. They are tedious and slow. An internal team trying to do cleanup while also booking transactions usually compromises one or the other — either the cleanup drags out for months or the close gets late. Bringing in a firm to handle cleanup as a discrete two-week engagement, then handing back to the internal team for the rest of the migration, is often the right hybrid.
Signal 2: The migration has a deadline tied to a business event. The most common ones we see: an acquisition close where the new parent requires Advanced for consolidated reporting. A financing round where due diligence pulls require detailed reports the team cannot produce on Plus. An audit where the auditor has asked for role-based access controls. A tax compliance change where the firm needs to track new fields for a state nexus situation. When the migration has a deadline, internal teams underestimate it almost every time. Outside help reduces the deadline risk because the firm is doing this every month and knows where the time goes.
Signal 3: The internal QBO owner is also the controller. This is the most common reason we get brought in. The person who knows QBO best is also the person closing the month, reviewing journals, signing off on bills, and handling the auditor. They have eight hours a week to spend on the migration, in theory, but in practice those hours get eaten by close work. The migration drags out across three months, the team loses interest, and the new features never really get adopted. A firm taking the migration off the controller’s plate, with the controller staying in the loop as the approver and decision-maker, runs faster and lands more cleanly.
Signal 4: The team has never done a migration before and the file has more than 10 users. Migrations get exponentially harder with user count. Two users is a half-day conversation about roles. Ten users is a multi-day conversation about role boundaries, training schedules, and edge cases. Twenty users is a project. If your team has not done a migration of this size before, the cost of getting it wrong is high enough that outside experience pays for itself.
Signal 5: There are integrations or third-party tools in play. A clean QBO file with no integrations migrates easily. A QBO file connected to Bill.com, Ramp, Stripe, Shopify and a custom CRM is a multi-system migration with auth handshakes, permission scopes, and data flow changes to think through. Each integration has its own quirks at the tier-change moment. A firm that has migrated dozens of these knows which integrations break and how to fix them quickly. An internal team is rediscovering each one in real time.
When to keep it internal. If none of the five signals apply — the file is clean, there is no deadline, the QBO owner has dedicated time, the team is small, the integrations are minimal — an internal team can run the four-phase plan as a guide and land it cleanly. We have walked many small clients through this without billing for the migration itself, just doing a free 60-minute kickoff call and a free 30-minute check-in at week 2. For some firms that is the right level of help.
What a CPA firm engagement looks like. A typical migration engagement is fixed fee, four weeks, with three the work. Week 1: audit report and cleanup plan, signed off by the client. Weeks 2-3: configured Advanced file with custom roles, custom fields, and workflows, including a written record of every decision made and why. Week 4 and beyond: cutover execution, first-month watch, and a 60-day retrospective with adjustments. Most engagements bill in the $4,000 to $12,000 range depending on user count and complexity, which is comparable to roughly 60 to 150 hours of internal staff time at a loaded cost.
The hybrid model. The split many of our clients prefer is to bring in the firm for the audit (Phase 1) and the configuration (Phase 2), then run the training (Phase 3) and the cutover (Phase 4) internally with check-ins. The firm gets you to a configured file faster than the team could on its own. The team takes ownership of training and cutover so the knowledge stays in-house. This typically runs about 60 percent of the cost of a full engagement and produces a team that owns the new configuration rather than just inheriting it.
What we ask for before quoting a migration engagement. Five things, in this order.
- Read-only access to the Plus file to run our own audit
- The user list with current roles and the team’s view of who should access what
- The integration list and the admin-level access to confirm each one
- The current month-end close timeline (so we know what to work around)
- A 30-minute conversation with the QBO owner and the controller about problems
That hour of pre-quote work usually surfaces 90 percent of what we need to know to scope the engagement properly. If a firm quotes you a migration without doing this homework, they are guessing.
The “we can figure it out”. Trap. Many internal teams say they can handle the migration and then halfway through realize they cannot. The reason is not lack of intelligence. It is lack of time. The migration looks like a side project at the start and like a real project by the middle. Setting the expectation upfront — “this is a real project, the QBO owner will spend 15 hours a week on it for four weeks” — is what separates internal migrations that succeed from internal migrations that stall.
How to decide in one question. If the migration stalled out for three months, what would the cost be to the business? If the answer is “nothing, we would just stay on Plus a little longer,”. Handle it internally. If the answer involves missed reporting commitments, a delayed audit, a frustrated investor, or a controller who quits, bring in a firm. The cost of a delayed migration is almost always higher than the cost of an outside firm running it on time.
If you want to talk through whether this is a project for your team or for ours, the conversation is free and confidential. The full scope of what we touch in a migration engagement, and how it ties into ongoing bookkeeping, is in our client accounting services overview. The pillar guide for the product overall lives at our QuickBooks Online Advanced page.