top of page

Batch Migration Tool

Step 1 - Navigation

Screenshot 2025-01-28 at 11.16.37 AM.png

Step 2 - Welcome screen

Screenshot 2025-01-28 at 11.17.51 AM.png

Step 3 - After company files are uploaded

Screenshot 2025-01-28 at 11.18.05 AM.png

Step 4 - After uploading multiple files

Screenshot 2025-01-28 at 11.18.38 AM.png

Step 5 - Sign in to Intuit Account for the dashboard

Screenshot 2025-01-28 at 11.18.50 AM.png

Step 6 - Dashboard with uploaded files

Screenshot 2025-01-28 at 11.18.59 AM.png

Step 7 - Dahsboard with migration status

Screenshot 2025-01-28 at 11.19.06 AM.png

Step 8: Dashboard after company files have been migrated

Screenshot 2025-01-28 at 11.19.17 AM.png

Project overview

To help long-time QuickBooks Desktop users move to QuickBooks Online with confidence, we built a dedicated end-to-end migration tool. Designed to be simple, intuitive, and secure, the tool focused on meeting the needs of less tech-savvy customers who were often hesitant about switching platforms.

We also created a specialized experience for accountants — one that let them migrate multiple client files to QuickBooks Online in a single flow. Until then, accountants were using a tool built for individual users, forcing them to migrate one company file at a time — a slow and tedious process for firms managing dozens of clients. 

Customer problem

  • I am an accountant using the QuickBooks Desktop Accountant product to manage my QuickBooks Desktop clients. 

  • I want to migrate my QuickBooks Desktop clients to QuickBooks Online so that I can manage them all in one place. 

  • But I take far too long to do so. 

  • Because I have to migrate each client's company file, one at a time. 

  • Which makes me feel insufficient and under productive. 

Solution & implementation

Solution

Accountants managing multiple clients often struggle with moving client files from QuickBooks Desktop to QuickBooks Online — especially when dealing with high volumes. The existing flow required them to migrate each file individually, which was time-consuming, repetitive, and error-prone.

To solve this, we introduced the Accountant Batch Migration Tool — a guided experience that helps accountants move multiple client files from Desktop to Online in one go.

This tool reduces friction, saves time, and gives accountants more control and visibility throughout the process.

Implementation

As the content designer on this project, my goal was to design clear, empathetic, and action-oriented guidance within a highly technical and multi-step workflow.

Here’s how I approached it:

 

1. Shaping the content strategy

  • Partnered closely with PM, Design, Professional Services, and Marketing teams to define the voice for this tool → balancing technical accuracy with a reassuring, friendly tone.

  • Focused on making the migration feel easy and approachable for accountants who might be nervous about moving sensitive financial data.

 

2. Designing the end-to-end experience

  • Created a step-by-step guided flow — making sure every screen answered:

    • What is happening?

    • What do I need to do?

    • What happens next?

  • Key content moments I worked on:

    • Welcome screen → setting expectations

    • Migration checklist → prepping accountants before they start

    • Error handling → clear, actionable recovery paths

    • Success states → confirming completion and next steps

    • Tooltips & in-product help → reducing dependency on external support
       

 

3. Partnering for help & learn content

  • Extended the product guidance into Help articles (like the one you shared) — making sure language was consistent and instructions were scannable.

  • Collaborated with Tech Writers to align terminology across in-product and help content.
     

4. Testing & iterating with customers

  • Supported user testing sessions to see where accountants got stuck or confused.

  • Iterated content based on feedback — e.g., simplified error messages, clarified file size limits, refined confirmation screens.

Content design impact

  • Reduced accountant drop-off rates mid-migration.

  • Higher confidence and satisfaction with the migration experience.

 

Overall impact

  • 1.1K files were migrated within 6 months of the tool's launch. 

  • 2.5% of overall migration is happenning via this tool. 

Style Guide

Contentatintuit.png
unnamed.png

Content Design System

I have been an active member of Intuit's content style system.

 

As a member of the style council, I have participated in style guide-related discussions. I have contributed to the style guide by giving examples and expressing my opinion on improving/adding words to the existing style guide.

Exceptions To The Style Guide

Project Overview

As part of the Desktop Migration projects at Intuit, I identified a key challenge in adhering to the existing style guide while maintaining clarity and conciseness in customer-facing content. This led me to propose and implement an exception to the style guide to improve readability and usability.

Problem Statement

  • The existing style guide at Intuit did not allow the abbreviation of QuickBooks Desktop as "Desktop" to avoid potential user confusion.

  • However, in the Desktop Migration content, we frequently needed to reference both QuickBooks Desktop and QuickBooks Online in the same sentence.

  • Due to space constraints in UI elements and emails, using the full name repeatedly was affecting readability and user experience.

Solution & Implementation

  • Conducted a brief user research exercise to understand how customers perceive the abbreviation "Desktop."

  • Found that when capitalized (Desktop), users could distinguish it from the general meaning of "desktop" as a device.

  • Proposed an exception to the style guide allowing "Desktop" (with a capital D) as a valid abbreviation for QuickBooks Desktop in cases where:

    • Character limits restricted the use of the full name.

    • Both QuickBooks Online and QuickBooks Desktop appeared multiple times within a short span of text.

  • Aligned with cross-functional stakeholders (content designers, product managers, legal, and customer support) to ensure consistency and clarity.

  • Successfully implemented this exception across key UI elements, marketing emails, and help content.

Impact

  • Improved readability by reducing redundancy while maintaining clarity.

  • Ensured consistency across content while adhering to the core principles of the style guide.

  • Enhanced customer experience by making information easier to process in migration-related communications.

Desktop Migration

Desktopmigration1.png
Desktopmigration2.png

Project Overview

To help long-time QuickBooks Desktop users migrate their company files to QuickBooks Online, we built an end-to-end migration tool. The tool was designed to be simple, intuitive, and secure, addressing the needs of less tech-savvy customers while leveraging AWS capabilities for data transfer.

Problem Statement

  • QuickBooks Desktop has been around for nearly 30 years, and many customers were unfamiliar with modern migration processes.

  • The existing migration options were complex and difficult to follow, especially for those using older versions of QuickBooks Desktop.

  • The AWS-based file upload process added another layer of complexity, making it harder for customers to migrate seamlessly.

  • Our challenge was to design and communicate the migration process in a way that was clear, concise, and non-technical.

Solution & Implementation

To simplify the experience, we took a structured approach:

  1. Redesigned the Migration Tool

    • Moved away from the AWS-dependent upload system and built an in-house migration tool for a smoother experience.

    • Reduced unnecessary steps, allowing customers to simply upload their company file and follow guided instructions.

    • Aligned the UI design with existing migration tools to ensure familiarity for returning users.

  2. Refined the Content Experience

    • Removed excessive instructions from the home page and replaced them with a clear 3-step migration guide.

    • Focused on plain language and intuitive messaging, avoiding technical jargon.

    • Prioritized customer concerns about security, addressing what happens to their data during migration.

    • Conducted content testing and user research to ensure clarity and usability.

  3. Iterative Design Approach

    • Initial feedback on Design A indicated that the process felt complicated due to the AWS-based upload and overly detailed instructions.

    • Based on user feedback, we streamlined the experience in Design B, making migration simpler and more intuitive.

Results & Impact

  • Increased adoption: As of today, 60% of customers migrating from QuickBooks Desktop to QuickBooks Online use this tool

  • Simplified experience: Users found the migration process easier and more intuitive, with fewer roadblocks.

  • Clearer communication: Content refinements helped reduce confusion and made migration more accessible to all customers.

bottom of page