MSP Guide: Adding Legacy File Migration to Your Windows 11 Practice

Windows 11 rollouts have an underserved problem that most MSPs are handling reactively: legacy Office files that break after the upgrade. Every client running .xls workbooks with VBA macros or .mdb databases is at risk. Most of them don't know it yet.

This creates a clear service opportunity — one that integrates naturally with the Windows 11 work you're already doing, adds a defined deliverable, and is genuinely valuable to your clients rather than just a technical add-on.

Here's how to build it.

The Problem You're Solving

When a client moves to Windows 11 and Office 365, several things happen to their legacy Office files:

• 64-bit Office breaks VBA macros — Any code with Declare Function or Declare Sub calling Windows APIs throws a compile error on 64-bit Office. Macros stop running entirely.
• ActiveX controls fail — 32-bit ActiveX controls (calendar pickers, custom dropdowns, embedded objects) don't load in 64-bit Office. Buttons that did things no longer do anything.
• .mdb files stop opening — Modern Access can still open and edit .mdb files, but cannot create new ones and some legacy features (user-level security, replication) are unavailable. Any client still running departmental .mdb databases will lose access after the Office upgrade.
• Macro security defaults change — Office 365 blocks macros in files from network shares or email by default. Files that worked before now prompt errors or silently do nothing.

Your clients know they have "Excel spreadsheets" and "Access databases." They don't know which ones will break and which ones won't. That's where you add value.

The Service: Pre-Migration File Audit + Remediation

Phase 1: Discovery (Billable)

Before the Windows 11 rollout, run a file system scan to inventory all legacy Office files on the client's network:

• Identify all .xls, .mdb, .xlsb, .xlsm files on file servers and workstations
• Filter for active files (modified in last 90 days) vs dormant archives
• Flag which active files have VBA macros or .mdb format
• Deliver a report: file count by type, active vs archived, risk tier

This is 2–4 hours of work for a typical SMB client and gives them something concrete: a picture of their exposure. Bill it as a fixed-price "legacy file risk assessment" — $500–$1,500 depending on client size.

Phase 2: Remediation (Billable)

Armed with the audit report, execute the migrations. The scope depends on what you found:

Finding	Remediation Work	Complexity
.xls files, no macros	Convert to .xlsx	Low — batch automated
.xls files with macros, no API calls	Convert to .xlsm, test	Low-Medium
.xls files with PtrSafe issues	Fix API declarations, convert, test	Medium
.xls files with ActiveX controls	Convert + replace or re-register controls	Medium-High
.mdb files	Convert to .accdb, test all forms/queries	Medium
Shared .mdb with linked tables	Full split architecture migration	High

Pricing approaches:

• Per-file flat rate: $350–$600 per file for simple conversions; $800–$2,000 for complex VBA or Access migrations
• Project rate: Fixed quote based on the audit findings. Easier to sell, predictable for the client.
• T&M: Works but harder to justify. Clients resist open-ended billing on something they don't fully understand.

Phase 3: Post-Upgrade Monitoring (Optional Recurring)

After the Windows 11 rollout, include a "30-day file health check" — a follow-up scan and a meeting to resolve any macro issues that surfaced in production. This can be included in the project price or offered as a separate monthly check for the first quarter.

Tooling

For the Audit

PowerShell is sufficient for the initial inventory scan. A script that finds all legacy file types, filters by LastWriteTime, and exports to CSV gives you the raw data. For identifying which files have macros, you either open each file via Excel COM automation (slow) or use a tool that does it faster.

For macro-level auditing — what API calls exist, which ActiveX controls, what VBA complexity — a dedicated tool saves significant time compared to manual inspection.

For the Conversion

LegacyLeaps handles the conversion work: scanning each file for macros and controls, converting to the correct modern format (.xlsm for macro-enabled, .xlsx for clean files), and fixing systematic PtrSafe errors. This is what we built it for.

LegacyLeaps is a desktop app — files stay on your client's machine. That matters for clients who are sensitive about proprietary data leaving their network.

MSPs can use LegacyLeaps on client files directly or white-label the scanning process as part of your assessment workflow. We offer volume pricing for MSPs — see the MSP program page for details.

How to Talk to Clients About This

Most SMB clients don't know what a VBA macro is. They know they have "spreadsheets that run reports" and "databases for tracking inventory." Frame the conversation around the business outcome, not the technology:

"When we upgrade your machines to Windows 11 and move you to Microsoft 365, some of your older Excel spreadsheets — especially the ones with automated reports or buttons that do things — may stop working. We've seen this happen to clients who skipped the pre-work. We want to scan your network first, find out which files are at risk, and fix them before the upgrade rather than after."

This framing does three things:

1. Establishes the risk without being alarmist
2. Positions you as proactively protecting the client
3. Creates urgency without manufactured urgency — the Windows 11 rollout is the natural deadline

What You Won't Fix (and How to Handle It)

Not every broken macro is a migration problem. Some macros broke because the underlying business logic has a bug that happened to surface after the environment changed. Those require VBA development, not conversion. If you encounter that during remediation:

• Document what you found and what you attempted
• Offer a T&M quote for VBA development work (or refer to a VBA specialist if that's outside your practice)
• Don't absorb the cost of undocumented custom debugging within the fixed-price project

Being clear about scope upfront — "we'll fix the compatibility issues caused by the format change and the 64-bit upgrade; we don't rewrite custom business logic" — sets the right expectation.

Revenue Potential

A typical SMB client with 50–200 users might have 200–500 legacy Office files. After filtering to active files with macros, you're usually looking at 20–50 files that need actual work. At $500–$1,500 per project file, that's $10,000–$75,000 per client engagement — added onto a Windows 11 rollout that was already happening.

Across a portfolio of 20–30 SMB clients doing Windows 11 migrations, this is a significant recurring revenue line for the next 12–18 months while Windows 10 EOL drives upgrade activity.

Related: How to Audit an Organization for Legacy File Risk · IT Manager's Buyer's Guide to Bulk Excel Conversion · Windows Upgrade Survival Guide

← Back to all posts