Hi folks, this is chapter one of my New Outlook online “book” called Technicians Guide For Mastering New Outlook
You can click on that link to read the full online book or you can read this chapter for just this information. I also decided to do something new for this book. I decided to copy it all into CoPilot chapter by chapter to see how AI changes everything. Honestly, I like the version CoPilot created. It’s more of a technical guide than a storytelling book. I’m hoping this helps some of you learn everything you need to know about the technical side of New Outlook. If you need my help, feel free to contact me using the form below.
Chapter One – Outlook Email Accounts and Data
Outlook has evolved significantly over the past three decades, but one thing has remained constant: technicians must understand how each account type stores, syncs, and manages data before attempting any migration. New Outlook introduces a cloud‑first architecture that behaves very differently from Outlook Classic, especially for users with legacy configurations. This chapter provides a technical foundation for identifying account types, understanding their data structures, and preparing for a successful transition.
I have supported Outlook since the late 1990s and email systems since 1996. The guidance in this chapter—and throughout this book—is based entirely on real‑world experience, not AI‑generated content. After writing eight previous “how‑to” guides, I chose a digital format for this one so it can evolve alongside New Outlook, which is still maturing and will continue to change over the coming years. Supporting Outlook users is my day‑to‑day work, and adapting to New Outlook became essential long before Microsoft made it the default.
Most technicians—especially those in break/fix, consulting, or small repair shops—encounter more complex Outlook environments than any MSP or corporate IT department. These environments often include multiple account types, PST archives, custom rules, and years of accumulated configuration changes. This chapter prepares you to recognize those scenarios and understand how each behaves in both Outlook Classic and New Outlook.
Preparing for the Transition
If you haven’t received calls about New Outlook yet, you will. Windows 10 and Windows 11 home users are increasingly being prompted to switch, and many are doing so without understanding the implications. MSPs may have delayed the rollout for managed clients, but the shift is inevitable. Even Exchange‑based environments will encounter missing features, relocated options, and new behaviors that require technician guidance.
Throughout this book, I speak to multiple audiences:
Even if a section doesn’t seem to apply to your environment, reading it will deepen your understanding of Outlook Classic’s internal behavior—knowledge that becomes invaluable when troubleshooting unexpected issues.
Understanding Outlook User Types
Outlook supports a wide range of account types, and in break/fix or consulting environments, it’s common to see several of them configured within a single profile. Each behaves differently, stores data differently, and migrates differently. Before moving a user to New Outlook, you must identify:
Below is a technical breakdown of each major account type and how it behaves in Outlook Classic versus New Outlook.
Email Hosting Types and Their Behaviors
POP Accounts
Common providers: Network Solutions, HostGator, BlueHost, cable companies, AOL, Yahoo, Gmail (legacy POP setups)
How POP behaves in Outlook Classic:
Migration considerations:
IMAP Accounts
Common providers: Network Solutions, HostGator, BlueHost, cable companies, AOL, Yahoo, Gmail
How IMAP behaves in Outlook Classic:
Migration considerations:
Outlook.com / Hotmail / MSN / Live Accounts
Server type: Microsoft’s consumer Exchange platform (converted from POP/IMAP to Exchange in 2017)
How these accounts behave:
Migration considerations:
Microsoft Exchange (Business)
How Exchange behaves:
Migration considerations:
Hosted Exchange (Third‑Party Providers)
Common issues:
Migration considerations:
Google Workspace / GWSMO
How it behaves:
Migration considerations:
iCloud Accounts
Two possible configurations in Outlook Classic:
Migration considerations:
Summary
Understanding the account type is the foundation of every successful New Outlook migration. POP and IMAP users require the most manual work, while Exchange, Outlook.com, and Google Workspace users transition more smoothly. iCloud users benefit from improved native sync in New Outlook, but legacy setups require careful handling.
This chapter sets the stage for the onboarding and migration workflows covered in later chapters.
Read Chapter Two:
Hi folks, I’m Lisa Hendrickson and I wrote up this article just for technicians and “tech savvy” users to learn about New Outlook. This is not your ordinary read, it’s more of a “How-To” on all the technical requirements of New Outlook. What I cover is mostly everything you need to know on how to transition data and information from Outlook Classic, to New Outlook. I also include some sales information and “things you should know”, the tough stufff about migration work.
I also decided to do something new for this book. I decided to copy it all into CoPilot chapter by chapter to see how AI changes everything. Honestly, I like the version CoPilot created. It’s more of a technical guide than a storytelling book. I’m hoping this helps some of you learn everything you need to know about the technical side of New Outlook.
Before you begin
More about me:
I’m a Microsoft Outlook Expert with 29 years working in tech, focused on email programs, Outlook and email delivery. I also work with Microsoft 365 more with Exchange and Admin. I started my business in 2007 and in 2013, went remote only focused on Outlook and Office 365. I spent the last few years learning the back end of New Outlook so I can prepare for all the migrations coming up. I felt I needed to know everything possible so my clients could call for support from me. I’m so glad I did this! Not only are many of my clients now calling in for New Outlook help, I also earned a Microsoft MVP award for Outlook. Now this book is the chef’s kiss of my work. Now I continue to write blog posts about fixes and update daily on my LinkedIn account. Follow me if you want to see the daily fun I have. LinkedIn https://www.linkedin.com/in/callthatgirl
Now on to the book! Remember this was re-written by Copilot, so if it doesn’t sound like my normal writing style, it’s not. Those emdashses were left it as well.
Outlook Classic has been the backbone of email productivity for decades. For many technicians—including myself—it has been a daily companion, a troubleshooting playground, and sometimes a battlefield. As Microsoft shifts toward a cloud‑first ecosystem, New Outlook is becoming the default experience for millions of users. Yet the transition is far from simple.
Most documentation focuses on Exchange‑based environments, leaving technicians unsupported when dealing with the messy, real‑world configurations we see every day:
multiple IMAP accounts, POP workflows, PST archives, custom rules, legacy add‑ins, and user‑invented systems that somehow “just work.”
This book exists because those scenarios matter.
Your clients rely on them.
And you deserve a guide that reflects the reality of the job—not the idealized version.
My goal is to give you a resource that is practical, technical, and grounded in decades of hands‑on experience. You’ll find clear explanations, migration strategies, and troubleshooting workflows that apply to real environments, not just Microsoft’s preferred ones.
If you support Outlook users in any capacity, this book is for you.
Lisa is a consultant specializing in Outlook, email systems, and client communications. She has worked in email support since 1996 and has supported Outlook Classic since the late 1990s. Over the course of her career, she has handled thousands of unique Outlook configurations—from simple home setups to complex multi‑account, multi‑protocol environments.
She is known for her ability to translate complex technical issues into clear, actionable steps, and for her commitment to helping technicians build confidence in their craft. Lisa has authored eight previous technical “how‑to” guides and contributes regularly to Microsoft Tech Community, Experts Exchange, and LinkedIn.
Her consulting practice focuses on helping individuals, businesses, and IT teams navigate Outlook migrations, troubleshoot advanced issues, and modernize their workflows.
This chapter provides a technical breakdown of how Outlook stores, syncs, and manages data across POP, IMAP, PST, Exchange, and GWSMO environments. Understanding these structures is essential before attempting any migration to New Outlook.
This chapter outlines the onboarding workflow for transitioning users from Outlook Classic to New Outlook. You’ll learn how to prepare the environment, evaluate compatibility, set expectations, and guide clients through the initial setup.
Before any migration, data protection is non‑negotiable. This chapter covers backup strategies for PST files, local archives, signatures, templates, rules, and other user‑specific assets that may not automatically migrate.
Not all data in Outlook Classic is stored in the same place—or even in a format New Outlook can use. This chapter helps you identify which data types must be manually migrated, which will sync automatically, and which require special handling.
New Outlook does not support every feature found in Outlook Classic. This chapter provides a detailed list of unsupported features, deprecated workflows, and legacy components that technicians must plan around.
This chapter provides step‑by‑step instructions for manually migrating data that New Outlook does not automatically import. Topics include PST handling, signature recreation, rules rebuilding, and custom configuration replication.
This chapter walks through the technical setup of New Outlook, including account configuration, authentication requirements, profile behavior, and best practices for ensuring a stable, predictable user experience.
Technicians will encounter errors, sync failures, missing features, and unexpected behavior during the transition. This chapter documents the most common issues and provides practical troubleshooting workflows.
Chapter 9 – Microsoft Home and Business Accounts
This chapter explains the unique behaviors of Microsoft personal accounts, Microsoft 365 Family/Personal subscriptions, and small business environments. These accounts often behave differently from enterprise tenants and require special handling during migration.
Outlook has evolved significantly over the past three decades, but one thing has remained constant: technicians must understand how each account type stores, syncs, and manages data before attempting any migration. New Outlook introduces a cloud‑first architecture that behaves very differently from Outlook Classic, especially for users with legacy configurations. This chapter provides a technical foundation for identifying account types, understanding their data structures, and preparing for a successful transition.
I have supported Outlook since the late 1990s and email systems since 1996. The guidance in this chapter—and throughout this book—is based entirely on real‑world experience, not AI‑generated content. After writing eight previous “how‑to” guides, I chose a digital format for this one so it can evolve alongside New Outlook, which is still maturing and will continue to change over the coming years. Supporting Outlook users is my day‑to‑day work, and adapting to New Outlook became essential long before Microsoft made it the default.
Most technicians—especially those in break/fix, consulting, or small repair shops—encounter more complex Outlook environments than any MSP or corporate IT department. These environments often include multiple account types, PST archives, custom rules, and years of accumulated configuration changes. This chapter prepares you to recognize those scenarios and understand how each behaves in both Outlook Classic and New Outlook.
Preparing for the Transition
If you haven’t received calls about New Outlook yet, you will. Windows 10 and Windows 11 home users are increasingly being prompted to switch, and many are doing so without understanding the implications. MSPs may have delayed the rollout for managed clients, but the shift is inevitable. Even Exchange‑based environments will encounter missing features, relocated options, and new behaviors that require technician guidance.
Throughout this book, I speak to multiple audiences:
Even if a section doesn’t seem to apply to your environment, reading it will deepen your understanding of Outlook Classic’s internal behavior—knowledge that becomes invaluable when troubleshooting unexpected issues.
Understanding Outlook User Types
Outlook supports a wide range of account types, and in break/fix or consulting environments, it’s common to see several of them configured within a single profile. Each behaves differently, stores data differently, and migrates differently. Before moving a user to New Outlook, you must identify:
Below is a technical breakdown of each major account type and how it behaves in Outlook Classic versus New Outlook.
Email Hosting Types and Their Behaviors
POP Accounts
Common providers: Network Solutions, HostGator, BlueHost, cable companies, AOL, Yahoo, Gmail (legacy POP setups)
How POP behaves in Outlook Classic:
Migration considerations:
IMAP Accounts
Common providers: Network Solutions, HostGator, BlueHost, cable companies, AOL, Yahoo, Gmail
How IMAP behaves in Outlook Classic:
Migration considerations:
Outlook.com / Hotmail / MSN / Live Accounts
Server type: Microsoft’s consumer Exchange platform (converted from POP/IMAP to Exchange in 2017)
How these accounts behave:
Migration considerations:
Microsoft Exchange (Business)
How Exchange behaves:
Migration considerations:
Hosted Exchange (Third‑Party Providers)
Common issues:
Migration considerations:
Google Workspace / GWSMO
How it behaves:
Migration considerations:
iCloud Accounts
Two possible configurations in Outlook Classic:
Migration considerations:
Summary
Understanding the account type is the foundation of every successful New Outlook migration. POP and IMAP users require the most manual work, while Exchange, Outlook.com, and Google Workspace users transition more smoothly. iCloud users benefit from improved native sync in New Outlook, but legacy setups require careful handling.
This chapter sets the stage for the onboarding and migration workflows covered in later chapters.
This chapter prepares you to understand how the account types described in Chapter One behave when configured in New Outlook. New Outlook is built on a cloud‑first architecture, and because of that, each account type interacts with it differently. Some accounts transition smoothly, while others require significant preparation, data migration, or a full server change before the user can adopt New Outlook successfully.
Break/fix technicians, independent consultants, and MSPs will see the widest variety of configurations. POP, IMAP, cable‑company email, and legacy accounts will generate the majority of your support calls. This chapter explains what to expect for each type and how to prepare your clients for the transition.
POP / PST Users
POP/PST users will be your #1 source of New Outlook support calls. These users rely heavily on local data, custom workflows, and PST‑based storage—none of which map cleanly into New Outlook.
How POP Works in Outlook Classic
Why PST Files Matter
For POP users, the PST is the heart of their Outlook experience. It contains:
The PST is often more important than the POP account itself. Creating a new POP profile with a new PST results in an empty Outlook environment, which is why these users panic when something breaks.
How POP/PST Sets Up in New Outlook
If a POP user sets up New Outlook on their own:
Current PST Limitations in New Outlook
What POP Users Will Do
Most POP users will:
I strongly recommend domain‑based POP clients migrate to Exchange now so they are ready for New Outlook long before 2029.
A full PST‑to‑Exchange migration guide will appear in a later chapter.
IMAP Users
IMAP users will see a partial but incomplete setup in New Outlook.
What IMAP Users Will See in New Outlook
What Will Be Missing
All of these live in the local OST under (This computer only) and must be exported and migrated to a server that supports full synchronization.
When IMAP Users Must Change Servers
IMAP does not support native calendar or contact sync. If your client needs:
…they must move to:
Most of my IMAP clients choose Exchange because they prefer Outlook’s full feature set.
Exchange Users
Exchange users have the smoothest experience.
What Works Well
Exchange maps cleanly into New Outlook.
What to Expect
Outlook.com Users
Outlook.com behaves similarly to Exchange, with one major difference: storage limits.
What Works Well
Storage Consideration
This matters during migrations—especially for users with large PST files.
Cable Company Email Users
Cable‑company email behaves like POP or IMAP depending on the provider.
Typical Behavior
Migration Considerations
AOL / Yahoo / Verizon / SBCGlobal / PacBell
These legacy providers are surprisingly better in New Outlook than in Outlook Classic.
What Works in New Outlook
This is because New Outlook uses a more modern connection model that acts as a “skin” over the provider’s server.
What Does Not Work in Outlook Classic
New Outlook is a major upgrade for these users.
iCloud Users
iCloud users benefit significantly from New Outlook—when everything is configured correctly.
What Works Well
This is one of the best surprises in New Outlook.
Common Issues
Once corrected, iCloud works beautifully.
Summary
Each account type behaves differently in New Outlook:
This chapter gives you the foundation you need to prepare clients for what they will see when they switch to New Outlook.
In Chapter One, I walked through the different email account types, how they behave in New Outlook, and which data must be migrated to avoid surprises later. Now it’s time to shift into the real‑world prep work—the onboarding steps I complete before touching a single profile, PST, or DNS record.
This chapter is the foundation of every successful migration. If you skip it, you will meet the consequences later. I’ve learned that the hard way more times than I care to admit. Even now, after decades of doing this, I still run into “I can’t believe I just saw that” moments. Outlook has a way of keeping us humble.
The simplest way to stay organized is to create a Notepad file on the client’s computer and document everything as you go. It becomes your working log for the project and your reference point the next time you support that client.
When I first started doing migrations, life was simpler. There were no Microsoft account tangles, no identity confusion, and Hosted Exchange was the only real option. I even wrote a book years ago on Exchange migrations—completely outdated now, yet the core steps still apply. Outlook Classic barely changed its configuration model for decades, and honestly, thank goodness for that stability.
New Outlook won’t stay still either. By 2029, it will look nothing like it does today. But the fundamentals of data migration don’t change. There are only so many ways to move data from Point A to Point B, and the workflows in this book will remain relevant for years. The “how‑to” video chapters will walk you through the hands‑on steps, but onboarding always starts here.
Step One: Gather Every Piece of Information
There’s no perfect order for this list—just make sure you collect it all. Missing even one item can derail a migration or force you to backtrack.
Windows Accounts (Personal or Business Login)
Current Office License
Antivirus
All Email Accounts in Outlook
PST Files
CRM Plug‑ins
Third‑Party Sync Tools
Local Rules
Forms
Templates
Special Configurations
Ask the client directly:
You’d be surprised how often this uncovers something important.
Website / Domain Information
DNS Login
Microsoft 365 Tenant Account
Other Microsoft 365 Accounts
Stream Autocomplete
If you gather all of this upfront, your migration will run smoother, faster, and with far fewer surprises. Every Outlook technician eventually develops their own rhythm, but the checklist above is the backbone of a clean, predictable onboarding process.
By the time you reach this chapter, you’ve seen the big picture: onboarding, account setup, backups, migration day, importing, MFA, phones, after‑care, and the inevitable chaos that comes with real‑world Outlook work. Now we’re going to zoom out and look at the workflow itself — the rhythm, the pacing, the order of operations that turns a messy, unpredictable migration into a controlled, repeatable process.
This chapter is about how technicians think, not just what they do. It’s the difference between following steps and running a migration like a seasoned pro.
Why Workflow Matters More Than Any Single Step
Anyone can follow a checklist. What separates a technician from a “button pusher” is the ability to:
A good workflow protects your time, your reputation, and your sanity. A great workflow makes clients think you’re a magician.
The Migration Workflow I Use for Every Client
This is the high‑level flow I’ve refined over thousands of migrations. You’ll notice it’s not just a list — it’s a strategy.
This is the part clients don’t see, but it’s where you prevent 80% of the disasters.
You’re confirming:
This is where you catch the “Oh, I forgot to tell you I have a second Gmail account feeding into Outlook” or “I didn’t realize my website guy controls my DNS.”
Every migration problem you prevent here is a problem you don’t have to fix later.
Before touching Outlook Classic, you make sure the future home for the data is ready.
This includes:
This is the “build the house before moving the furniture” stage.
This is where you protect yourself and the client.
You back up:
If something goes sideways — and it will, eventually — this is what saves you.
This is where you:
This is the moment where the “old world” and “new world” overlap. You’re building the bridge.
This is where your backups become your best friend.
You import:
You verify:
You watch OWA like a hawk. If it appears there, it’s on the server. If it’s on the server, New Outlook will eventually get it.
This is where you need the client present.
You:
This step is where clients often get confused, so patience is key.
This is where you:
This is also where you discover how many devices the client actually owns. Spoiler: it’s always more than they told you.
You’re not just a technician — you’re a guide.
After-care includes:
This is where your professionalism shines.
A quick 10‑minute walkthrough is usually enough for first‑timers.
You show them:
If they want deeper training, that’s a separate service — and a great revenue stream.
This is where you learn.
You ask yourself:
This is how you evolve from a technician into an expert.
Why This Workflow Works
Because it’s built on:
It’s not rigid — it’s adaptable. It’s not theoretical — it’s battle‑tested. And it’s not just for big migrations — it works for the one‑mailbox jobs too.
Closing Thoughts for This Chapter
A migration is never “just a migration.” It’s a combination of:
When you follow a workflow like this, you reduce the chaos and increase the success rate. You also protect your time, your business, and your reputation.
And most importantly: you give your clients a smooth, confident experience — even when the tech behind the scenes is anything but smooth.
If there’s one universal truth in Outlook migrations, it’s this: no migration is perfect. Some projects feel like a chef’s kiss — smooth, predictable, and deeply satisfying. Others… well, they become the stories you tell later, the ones that teach you something new even after decades in the trenches.
Even with the best onboarding, surprises still happen. Today’s example? A Gmail account that looked pristine in Outlook Classic — no “This computer only” folders anywhere. After migrating the data to Exchange, those hidden folders suddenly appeared. Easy enough to fix by renaming, but then the client casually mentioned a previous failed DIY migration attempt that never came up during onboarding. That explained everything.
I added a second Gmail account to Outlook Classic, downloaded a fresh copy, and had the client verify folder by folder. Thankfully, everything matched. My heart rate returned to normal. Fixing a hundred folders was not on my bingo card for the day.
These moments are exactly why onboarding matters — and why you should expect the unexpected. Below is a curated list of the most common issues you’ll encounter during migrations to New Outlook, along with the context you need to recognize and handle them quickly.
Common Issues During New Outlook Migrations
Microsoft Account Confusion
Most clients have a personal Microsoft account tied to their Windows login — especially if they bought the computer themselves. That single email address (often Gmail) may also be tied to:
Untangling this web is part of onboarding, and it’s where you’ll uncover mismatched accounts, duplicate identities, and login conflicts.
Windows Account Conflicts in New Outlook
Clients often accidentally add their work/school account under Windows “Accounts.” New Outlook may try to authenticate with that account instead of the one you’re actually migrating. Expect login loops, credential prompts, and general chaos until you sort it out.
Passwords
The simplest issue is also the most common.
If a password doesn’t work: reset it.
A bad password can derail an entire migration. I keep all necessary credentials in my notepad during the project — DNS, Microsoft personal/business, iCloud, hosting logins — so I can copy/paste through setup wizards without delay.
Antivirus Interference
McAfee, Norton, and others can block:
One client couldn’t download more than 10 Gmail messages until he replaced McAfee. Not ideal, but it worked.
VPN Problems
VPNs cause:
I now ask about VPNs during onboarding because they can absolutely tank a migration.
Firewall Blocks
On Macs especially, firewalls can block remote access entirely. Turning it off may be the only way in. PC migrations rarely hit this, but it’s worth keeping in mind.
Data Not Syncing
Possible causes:
If only some folders fail, you’ll need to manually copy them from your backup. With clients who have hundreds of folders, I often teach them how to do this themselves.
DNS Issues
DNS can stop a migration dead in its tracks.
If you can’t update DNS records, the project waits.
If a website admin controls DNS, schedule the migration for when they’re available. SPF, DKIM, and DMARC issues will also show up quickly after cutover.
Junk/Spam Problems After Migration
If test messages from the client land in your junk folder, DNS records need updating — usually SPF or DMARC.
MFA Setup Challenges
Authenticator setup can fail for many reasons:
I always have clients install Microsoft Authenticator during account setup so MFA is ready before we touch the phone.
Phone Setup Confusion
Android is usually simple: install Outlook and go.
iPhone users, however:
Merging Gmail → Exchange calendars is a very common request. It’s doable, but it adds about 30 minutes of work.
Missing Features from Outlook Classic
This is the #1 reason clients switch back.
Some users rely heavily on:
New Outlook simply isn’t ready to replace every Classic feature yet. Some clients love the simplicity; others aren’t ready.
PST Issues
Most PSTs import fine, but problems arise when they are:
New Outlook cannot repair PSTs. Without Outlook Classic, you’ll need third‑party tools or ScanPST (if installed locally).
Rules and Templates
Even backed-up rules may fail to import because folder paths change when moving to Exchange. Rebuilding rules in Outlook on the Web (OWA) is often the cleanest solution.
3rd‑Party CRM or App Integrations
If the CRM doesn’t support Microsoft 365 APIs or Graph, you’ll find out after the migration. Sometimes the fix is simple; sometimes it requires vendor support.
Offline Access Limitations
New Outlook currently supports limited offline access (typically 30 days, expandable to 180). This will evolve, but for now, it’s a constraint worth explaining to clients.
New Outlook Layout Differences
The interface is different. Some users love it; others don’t. Customization is limited for now, but more features will return over time. Clients can always revert to Outlook Classic — until Microsoft removes that option.
No OST Files
New Outlook doesn’t use OST files.
It connects directly to the server, so OST → PST conversions are becoming obsolete. This mostly affects legacy IMAP users.
Color Categories Not Matching
Eventually someone will run into mismatched categories. There’s no elegant fix yet besides manually adjusting colors or temporarily opening Outlook Classic to sync them.
OneDrive Confusion
Clients often assume email migration includes OneDrive migration. It doesn’t (at least not in my business). PSTs stored in OneDrive frequently:
I often move PSTs to the local C: drive before working with them.
Time and pricing are two of the most important pieces of any migration project, especially when you perform them manually as I do. Earlier in this book, I mentioned that I do not use automated mailbox‑migration tools like BitTitan. Manual migrations are a completely different service. You are hands‑on with the client from start to finish, working directly on their computer, configuring every setting, and ensuring every piece of data lands exactly where it belongs.
Most of my clients own their domains, manage their own DNS, and prefer to purchase their own Microsoft 365 subscriptions. Many are still on POP with PST files, or IMAP with (This Computer Only) folders and third‑party sync tools for contacts and calendars. These setups require more configuration, more cleanup, and more attention to detail. They also tend to come with extra requests—rules, templates, categories, signatures, and large distribution lists. More work means more time, and more time means higher billing.
This type of work requires someone who knows Outlook inside and out. You cannot “Google your way” through a migration. If you sell it, you must know how to complete it—fully, correctly, and efficiently. This is where I shine. Since 2009, I’ve completed thousands of manual migrations to Exchange and Outlook.com. It took years to get fast, confident, and consistent. I hit every bump in the road early on, and every so often something new still surprises me—but it’s rare. That’s why I felt ready to write this book. The fundamentals of migrating data into Exchange haven’t changed much, even as Microsoft 365 admin, security, MFA, and Outlook’s account‑adding experience continue to evolve.
How I Position the Project
When I identify a migration opportunity, I sell it as a one‑time project. Moving to Exchange should be something a client does once and then benefits from for many years. The quote may seem high to them at first, but the configuration time is real, and the value is long‑term.
If a client wants to shop around, I make sure they understand what my service includes:
Many IT providers only set up the Microsoft 365 account and add the mailbox to Outlook. They don’t migrate data, configure the environment, or provide aftercare. I know this because I get the aftercare calls.
Pricing
My pricing changes when my rates change, so quotes will vary over time. As of now, my hourly rate is $325 per hour for all services.
A typical estimate looks like this:
The first hour is always onboarding, account setup, and administrative work. The remaining time is the technical portion—backups, configuration, importing data, and verifying everything.
I bill by the minute, so some migrations finish faster. I’ve completed two‑mailbox migrations in a single hour when the clients had simple setups and minimal extras.
If You’re New to Migrations
If you’re confident in your skills but still learning the flow, pitch with kindness and transparency. Early in my career, I leaned on a vendor team who could step in if I hit a wall. That gave me the confidence to sell the work. Today, I don’t need that safety net—but you might, and that’s okay.
I’m happy to help you through your first few migrations. I call this a tech assist. If I’m helping you, price your work with some wiggle room. Don’t underquote, but be fair to yourself. You’ll learn more from the first few migrations than you’ll actually bill for.
Time Expectations
I structure every migration across three days. These are not full‑day appointments, especially Day 2, which involves many scattered calls and check‑ins. I avoid heavy appointments on migration days because the timing is unpredictable.
Day 1: Onboarding (10–60 minutes)
Day 2: Migration (1+ hour per computer/user)
This is the heavy lifting day. Tasks include:
For one user, one hour is typical to reach the “uploading to the cloud” stage—assuming no hiccups. Remember: Outlook Classic is still required as the vessel for data migration. New Outlook comes later.
Day 3: Follow‑Up / Aftercare (10–30 minutes)
If Day 2 went smoothly, aftercare is minimal:
Some clients may need a Day 4 follow‑up, especially if they want additional training.
After this appointment, I close the ticket and let them know future help will be a new ticket. This is also a great time to offer ongoing support packages. I sell 2‑hour blocks, though many clients decline right after a migration because they’ve just invested in the project. Still—always offer.
Why Migration Days Have Scattered Calls
These are normal and expected:
This is why migration days require flexibility. You’re not on the phone nonstop, but you’re on call throughout the day.
Before we get into the details, let’s set expectations. There are two very different types of “sales” in our world:
This chapter focuses only on Microsoft 365 sales and backup options for New Outlook. I’m assuming you already have clients coming in through your existing marketing, referrals, or reputation. What you need now is clarity on how to structure your Microsoft licensing approach and what backup options you can realistically support.
Why Microsoft 365 Sales Matter to Your Business
Whether you run a Break/Fix shop, operate as an independent consultant, or manage a full MSP, Microsoft 365 licensing plays a major role in your revenue model. You generally fall into one of two categories:
Both are valid. Both work. The key is choosing the model that fits your business style, workload, and long‑term goals.
Some consultants want full control over their clients’ Microsoft 365 environments—licensing, billing, security, and administration. These businesses typically partner with a vendor rather than going direct with Microsoft. Becoming a direct Microsoft partner is expensive and usually only feasible for large MSPs with significant volume. In practice, most MSPs use vendors such as Sherweb or PAX8. These two come up constantly in tech groups and MSP communities because they’re reliable, well‑supported, and widely adopted.
If you’re new to the partner ecosystem, spend time in tech forums and MSP groups. You’ll learn more from real technicians sharing their experiences than from any marketing page.
My Approach (And Why It Works for My Business)
I don’t run a traditional MSP. I chose a higher hourly rate and a non‑managed model, and it has served me well for years. I’m not interested in managing thousands of licenses or being on the hook for 24/7 support. My business is built around:
Rinse, repeat.
Many technicians prefer this model—hourly work, small projects, and no recurring administrative burden. If you’re unsure which direction to take, join tech groups and listen to how others run their businesses. That’s how I learned the MSP landscape and figured out what fit my personality and workload.
Your Sales Options
Based on my experience, there are three practical ways to handle Microsoft 365 sales. There may be others, but these are the ones most consultants and MSPs use.
This is my most popular option. The client purchases directly from Microsoft using their own information and owns the account outright. You assist with:
This model works beautifully for Break/Fix and independent consultants. I often offer next‑day migrations, remote into their computer, walk them through the purchase, set everything up, and they call me when they need help again.
Some vendors allow you to earn recurring revenue or one‑time commissions. I use a vendor for certain clients and have an affiliate link for those who are a good fit.
Not all clients want this. Many prefer to be self‑managed, and that’s perfectly fine. I may lose a small commission, (maybe $12 a year on a mailbox), but my hourly rate more than covers it. Plus, I know the Microsoft 365 Admin Center so well that I rarely need vendor support.
If you want recurring revenue, centralized management, and full control, this is the MSP route. You choose a vendor (Sherweb, PAX8, or others), and you handle:
The vendor steps in for escalations or Microsoft-level issues. This model requires more responsibility but offers predictable monthly income. If you enjoy managing environments and building long-term service contracts, this may be the right path.
Backup Options for New Outlook
Backup is another area where you need to decide what fits your business model.
Third-Party Backup Solutions
For my business, recommending off‑the‑shelf third‑party backup tools has always been the best option. Some companies offer affiliate programs, which can be a nice bonus if you find one. I used to rely on affiliate links until a large corporation shut down my program. Now I simply educate clients on their options and let them choose what works for them.
I do not manage backups for clients. I don’t want the liability or the ongoing workload. Many consultants feel the same way.
Local Backup: PST Export in New Outlook
New Outlook now supports PST export, which is a step in the right direction. At the time of writing, it’s still a bit rough around the edges, but it will improve over time.
If your clients want a local backup option, you’ll need to train them to:
This is a client‑managed solution, not something you should be responsible for unless you’re running a full MSP.
The one thing that will never stabilize—at least not fully—is the pace of development. New Outlook is still growing into itself, and the engineering teams continue to layer in features at a rapid clip. Because they rebuilt the app from the ground up, it’s not that they removed functionality; it’s that they haven’t added everything back yet. And there’s still a long road ahead before the experience matches the depth and flexibility of Outlook Classic.
Some features will return. Some won’t. And some will evolve into something entirely different. That’s the nature of Microsoft 365 now—constant iteration, constant modernization, constant rethinking of what productivity tools should be. By 2029, I expect New Outlook to be far more capable and far more aligned with what long‑time desktop users expect. And after that? Who knows. With Copilot reshaping the Microsoft ecosystem, we may be looking at a completely new era of how people interact with their inboxes, calendars, and data.
As we close this book, I want to leave you with a handful of practical, real‑world tips—things I’ve learned from thousands of migrations, countless surprises, and more “I can’t believe I just saw that” moments than I can count.
Final Tips for Successful Outlook Migrations
No migration is ever perfectly seamless. Something always pops up. The good news is that the more migrations you do, the fewer surprises you’ll encounter—and the faster you’ll recognize and resolve the ones that do appear. Experience is the real accelerator here.
When working remotely, assume the client will be with you for the entire migration. They’ll watch your screen, ask questions, and want to understand what’s happening. This is normal. You’ll need them for passwords, MFA prompts, approvals, and clarifications anyway. Occasionally you can work independently, but not often—so set that expectation early.
Admin portals change constantly. Buttons move. Settings relocate. Entire sections get renamed. If a client is watching—and they usually are—be honest. Tell them you need to locate the new position of the setting. Most of the time, it’s something in Entra/Identity, though mailbox and user settings shift too. Transparency builds trust.
About 75% of this job is explaining what’s happening. Many clients have already Googled their issue before calling you, and they’ll come in with partial information. Answer their questions clearly and simply. Overexplaining only creates confusion and makes it harder to pull them back to the essentials.
If something is a one‑time technical detail they don’t need to retain, say so gently. It helps them stay focused on what actually matters.
Before your first migration, have a checklist or outline based on the key concepts in this book. Move slowly and methodically. If a client pushes you to go faster, pause and review your progress out loud. This helps them understand the complexity and sets realistic expectations.
A simple “move my data” request can easily turn into a 3–4‑hour session—especially if the client forgot to mention something during onboarding.
A Final Word
I could list a hundred more tips, and by next year I’ll probably have a hundred new ones. That’s the nature of this work—we learn something new every day.
That’s it folks! If you need my help with New Outlook, please use the form below.
