Classic Outlook vs New Outlook: What Businesses Need to Know Before the Switch
Microsoft is gradually moving Windows users from classic Outlook for Windows to the new Outlook for Windows.
That does not mean businesses need to switch everyone immediately.
It does mean they should start preparing.
For many employees, new Outlook already provides everything they need.
For others, the differences can affect:
add-ins
shared mailboxes
PST archives
public folders
offline working
macros
custom workflows
specialist line-of-business integrations
The right question is therefore not:
“Is new Outlook better?”
It is:
“Can our users complete every important business process in new Outlook without losing functionality?”
That is the test that matters.
What Are Classic Outlook and New Outlook?
Microsoft currently supports two Outlook applications on Windows.
Classic Outlook for Windows
This is the long-established desktop application used by businesses for decades.
It supports mature desktop technologies and workflows including:
COM/VSTO add-ins
PST files
VBA macros
advanced offline use
public folders
multiple profiles
complex customisation
New Outlook for Windows
This is Microsoft’s newer Outlook application.
It shares much of its experience and architecture with Outlook on the web and provides a cleaner, more cloud-focused interface.
Microsoft positions new Outlook as the experience receiving its latest Outlook features and Copilot-assisted functionality.
That does not mean it has reached complete feature parity with classic Outlook.
It has not.
Is Classic Outlook Being Retired?
Eventually, Microsoft intends new Outlook to become the primary Windows Outlook experience.
But there is no reason for businesses to panic.
Microsoft’s current migration model has three stages:
Opt-in
Users can choose to try new Outlook.
Opt-out
New Outlook becomes the default for affected users, but they can still return to classic Outlook.
Cutover
Users will eventually lose the ability to switch back.
Microsoft says organisations will receive at least 12 months’ notice before cutover, and existing classic Outlook installations remain supported until at least 2029.
That gives businesses time to test properly.
Use it.
Do Not Treat This as a Cosmetic Upgrade
New Outlook looks different.
That is the obvious part.
The more important differences are underneath.
A business may rely on Outlook for:
CRM integration
legal document filing
secure email
invoice workflows
archiving
phishing-reporting add-ins
shared finance mailboxes
custom forms
macros
If one of those stops working, the fact that the new interface looks cleaner is irrelevant.
Before migration, catalogue the workflows rather than focusing on appearance.
The Biggest Issue: Add-ins
Add-ins are still one of the most important compatibility checks.
Classic Outlook traditionally supports desktop technologies such as:
COM add-ins
VSTO add-ins
New Outlook is based around modern web add-ins.
Microsoft can automatically map some recognised classic add-ins to web equivalents when users move to new Outlook—for example, supported integrations from vendors such as Adobe, Zoom, HubSpot and others. But this does not mean every COM add-in has an equivalent or will work unchanged.
That means every business should ask:
Which Outlook add-ins do we actually use?
Then check each one.
Pay particular attention to integrations involving:
CRM
legal case management
document management
email archiving
encryption
finance
secure file transfer
signatures
phishing reporting
A missing add-in can break a real business process.
PST Support Is Still Partial
PST files remain common in older businesses.
They may contain:
historic mail
former employee mailboxes
project archives
exported messages
personal filing systems
Microsoft’s April 2026 feature comparison still marks PST support in new Outlook as partially available.
That means a business relying heavily on PST archives should not assume new Outlook behaves exactly like classic Outlook.
Use the migration as an opportunity to ask:
Should this data still be in PST files at all?
Where appropriate, historic mail may be better moved into:
Exchange Online Archive
managed mailboxes
another governed archive platform
rather than continuing to depend indefinitely on locally stored PST files.
Offline Working Has Improved — But Is Still Not Identical
One early criticism of new Outlook was weak offline capability.
That has improved considerably.
Microsoft now supports offline access to:
calendar
contacts/People
in new Outlook.
However, Microsoft’s current feature matrix still marks offline support as partially available in several Outlook areas compared with classic Outlook.
That matters for users who regularly work:
on trains
on aircraft
in poor connectivity areas
at customer sites
from remote locations
Test real offline workflows.
Do not simply disconnect Wi-Fi for thirty seconds and call that a successful pilot.
Public Folders Are Still a Caution Area
Businesses still using public folders should test particularly carefully.
Microsoft currently lists public-folder support in new Outlook as partially available and explicitly advises users who depend heavily on creating, modifying or deleting public folders to continue using classic Outlook for now.
That is a genuine migration blocker for some organisations.
It may also be a good opportunity to decide whether old public-folder workflows should eventually move to:
shared mailboxes
Teams
SharePoint
another modern collaboration platform
But do not redesign the business process in the middle of an Outlook rollout unless you have planned it properly.
VBA Macros Are Not Supported
This is a major difference for specialist users.
Microsoft’s current feature comparison lists:
VBA Macro
as:
Available in classic Outlook
and:
Not supported in new Outlook.
That can matter where users rely on Outlook VBA to:
manipulate messages
automate filing
generate templates
trigger business processes
connect Outlook to legacy applications
If you have Outlook macros, identify them before migration.
Do not discover them after the user has already switched.
Multiple Profiles Are Not Yet Fully There
Classic Outlook users may rely on multiple Outlook profiles for:
different organisations
test environments
separate Exchange configurations
specialist workflows
Microsoft currently lists multiple mail profiles as upcoming in new Outlook rather than generally available.
Again, that may affect only a small number of users.
Those small groups are exactly why a blanket migration can cause trouble.
Shared Mailboxes Are Much Better Than They Were
Shared mailbox support has improved substantially.
Microsoft currently lists shared mailboxes as available in new Outlook, including support for adding a shared mailbox as a full account.
Adding it as an account enables capabilities including:
notifications
unread counts
rules
categories
automatic replies
retention policies
Quick Steps
However, some shared-mailbox features still differ.
For example, Microsoft currently states that shared-mailbox contact lists are unavailable in new Outlook, and add-in behaviour can vary depending on how the shared mailbox is added.
So a finance or support team using one shared mailbox all day should still be included in the pilot.
New Outlook Also Has Genuine Advantages
This should not become an article saying:
“New Outlook is worse.”
It is not that simple.
For many users, new Outlook provides a cleaner and more consistent experience.
Advantages include:
closer alignment with Outlook on the web
improved Microsoft 365 consistency
simpler settings
modern search
newer cloud-first functionality
Copilot-assisted features
easier delivery of new features
Microsoft is actively developing new Outlook and updating its feature-comparison matrix as functionality changes.
Some things are already better.
Others remain less capable.
That is why readiness should be determined by role.
Copilot Is Another Reason Microsoft Is Moving Forward
Microsoft is investing heavily in Copilot experiences inside Microsoft 365.
New Outlook is designed around that modern cloud platform.
Eligible Microsoft 365 Copilot users can use functionality such as:
summarising email threads
drafting messages
coaching
meeting-related assistance
But AI deployment should not be confused with Outlook migration.
Before expanding Copilot, businesses should still review:
Microsoft 365 permissions
data governance
SharePoint oversharing
sensitive information
Copilot can only be as well governed as the information environment it operates within.
The Best Migration Strategy Is Role-Based
Do not create one pilot containing six generic office users.
Choose people representing different Outlook dependencies.
I would include:
ordinary Outlook user
executive assistant
shared-mailbox user
heavy calendar user
remote/offline user
employee using specialist add-ins
user with PST archives
public-folder user if applicable
Then ask them to perform real work.
Not:
“Does Outlook open?”
But:
“Can you complete everything you normally do during a working week?”
Build an Outlook Dependency List
Before switching users, record:
Add-ins
Which add-ins are installed and what processes depend on them?
PST files
Who uses them and why?
Shared mailboxes
Can users send as, receive notifications and work with the mailbox as expected?
Delegation
Can assistants manage executive calendars and mail correctly?
Public folders
Does the organisation still depend on them?
Offline work
Can travelling staff work properly without internet access?
Macros
Does any workflow depend on VBA?
Specialist integrations
CRM, document management, legal software, signatures and archiving.
This dependency list becomes your migration plan.
Categorise What You Find
During the pilot, classify every difference into one of three categories.
Blocker
The business process cannot currently operate.
Example:
critical COM add-in has no supported alternative.
Inconvenience
The same task can still be completed, but differently.
Example:
button has moved.
Training issue
The capability exists, but users need to know how to use it.
That distinction prevents every complaint from becoming a migration blocker while ensuring genuine operational problems are taken seriously.
Manage the Transition Centrally
Without central control, businesses can end up with:
half the company using classic Outlook
half using new Outlook
inconsistent support instructions
different add-ins
confused users
duplicate training material
Microsoft provides administrators with deployment controls and migration-planning guidance specifically so organisations can manage this transition rather than leaving it entirely to individual employees.
A mixed environment may be necessary temporarily.
It should still be intentional.
Should You Move Everyone Now?
Not necessarily.
I would move users where:
required workflows are supported
add-ins have been validated
PST reliance is low
shared-mailbox workflows work
offline requirements are satisfied
user training is ready
I would keep appropriate users on classic Outlook where:
unsupported macros remain
specialist COM/VSTO integrations are business-critical
public-folder requirements exceed current support
a workflow still depends on an unavailable feature
That is not resisting change.
It is managing risk.
Do Not Wait Until 2029 Either
The opposite mistake is:
“Classic Outlook is supported until 2029, so we'll think about this in 2029.”
That creates unnecessary pressure later.
The support window gives you time to:
replace incompatible add-ins
reduce PST dependence
modernise old workflows
test shared mailboxes
train users
plan deployment
Use that runway.
Microsoft is clear that new Outlook is the strategic direction even though classic Outlook remains supported for existing installations for several more years.
The Business Readiness Checklist
Before switching a department to new Outlook:
1. Inventory classic and new Outlook users.
2. Catalogue COM/VSTO and web add-ins.
3. Check PST and local archive usage.
4. Identify VBA macros.
5. Test shared mailboxes and delegation.
6. Test public folders if used.
7. Test real offline workflows.
8. Check specialist CRM/document-management integrations.
9. Run a role-based pilot.
10. Separate blockers from training issues.
11. Prepare short user guidance.
12. Keep a controlled rollback path while Microsoft still permits it.
13. Review the plan as Microsoft closes remaining feature gaps.
The key principle is:
Migrate workflows, not just Outlook installations.
How Hamilton Group Can Help
Hamilton Group can help businesses prepare for the transition from classic Outlook to new Outlook without forcing users into a workflow that is not ready.
We can assist with:
Outlook readiness assessments
Microsoft 365
Exchange Online
add-in compatibility
PST/archive reviews
shared mailboxes
delegation
Outlook policies
migration pilots
user training
Copilot readiness
Outlook troubleshooting
The right migration is not:
“Microsoft says new Outlook is the future, so everyone changes today.”
It is:
“We know what our users depend on, we have tested the important workflows and we move each group when the evidence says they are ready.”
Visit hgmssp.com or call 0330 043 0069 to discuss Outlook and Microsoft 365 support.