First file free. Use code FIRSTFILE to convert one Excel file at no cost. Redeem now →
Windows 11 broke your Access database?

Drop your legacy file. See what's broken.

LegacyLeaps scans .xls and .mdb files for compatibility issues with modern Office — in seconds. No signup. No email. Just results. First file free.

Drag & drop your .xls or .mdb file here

or — .xls, .xlsx, .mdb, .accdb — max 25 MB

No file handy? Try with a sample file to see what the report looks like.

Tip: Make a copy, remove sensitive data, and scan the copy. Same results, zero risk.

256-bit encrypted transfers
Zero data retention
Files deleted after delivery

Here's what a scan looks like

Real output from scanning a legacy Excel file with VBA macros.

7Total Issues
3Critical
2Warnings
5Auto-Fixable
IssueSeverityAuto-Fix
Missing PtrSafe on FindWindow declarationCritical✓
DAO 3.6 reference marked MISSINGCritical✓
Long → LongPtr needed for hWnd parameterCritical✓
Calendar Control 12.0 (ActiveX) — not available on 64-bitWarning✓
Deprecated FileSearch API call in Module3Warning✓
5 of 7 issues auto-fixable

Scan Your Files — Free

100%
Local processing — files never leave your machine
< 5 min
Average time to scan & fix a file
30 day
Money-back guarantee — no questions asked

Two ways to migrate

Both start with a free scan. Pick the path that fits.

💻

Do It Yourself

Download the app, buy tokens, run migrations on your machine. Files never leave your network.

From $29/file →
🤝

We Handle It

Send us your files securely. We migrate, review, and deliver clean output. Free consultation included.

Free quote →

Simple, transparent pricing

Standard handles format conversion. Pro adds VBA preservation, ActiveX mapping, and Jet SQL fixes. Start Standard, upgrade to Pro anytime — just pay the difference.

Excel (.xls → .xlsx)

Standard
$29
per file
  • Convert .xls to .xlsx
  • Full compatibility report
  • Upgrade to Pro anytime (+$68)
Buy Token — $29
Pro
$97
per file
  • Everything in Standard, plus:
  • VBA macro preservation
  • PtrSafe keyword insertion
  • Deprecated API replacements
  • ActiveX control mapping
Buy Token — $97
Pro Bulk
$689
$68.90/file — save 29%
Buy Pack

Access (.mdb → .accdb)

Standard
$99
per file
  • Convert .mdb to .accdb
  • Full compatibility report
  • Upgrade to Pro anytime (+$248)
Buy Token — $99
Pro
$347
per file
  • Everything in Standard, plus:
  • VBA preservation & Jet-to-ACE fixes
  • Form & report compatibility
  • Linked table reconnection
  • Jet SQL modernization (19 patterns)
  • Optional SQL Server migration scripts
Buy Token — $347
Pro Bulk
$2,463
$246.30/file — save 29%
Buy Pack

100% Money-Back Guarantee

If LegacyLeaps doesn't preserve your formulas, macros, and formatting, we'll refund every penny. No questions asked.

30-day money-back guarantee on token purchases. 14-day guarantee on done-for-you services.

How it works

1

Scan your files free

Drop your .xls or .mdb files into our free scanner — right here on this page, or on the full scan page. See exactly what's broken.

2

Buy a token or request a quote

Self-service tokens start at $29/file. Or request a free consultation and we handle everything.

3

Get clean, working files

Converted files, compatibility reports, and auto-fix scripts. 30-day money-back guarantee.

What will your migration cost?

Answer 3 questions. Get an instant estimate.

150100200

Not sure what needs fixing? Try the free scan.

Upload your .xls or .mdb files and get a compatibility report in seconds. No email, no signup, no download required.

Tip: Make a copy of your file, remove any proprietary data, and scan the copy. You'll get the same compatibility results without exposing sensitive info.

Scan Your Files Free

Legacy File Migration: What LegacyLeaps Fixes

Every scan produces a detailed report. Most issues are auto-fixed.

VBA Compatibility

Updates DAO 3.6 and ADODB 2.5 references to modern versions. Adds missing PtrSafe keywords to Win32 API declarations. Replaces deprecated APIs like FileSearch, Assistant, and CommandBars with working alternatives.

Access Database Migration

Converts .mdb to .accdb format. Updates Jet OLEDB 4.0 provider references to ACE 12.0. Fixes linked tables, form controls, and generates SQL Server migration scripts if you're ready to move off Access entirely.

ActiveX Control Mapping

Maps 24 legacy ActiveX controls to modern replacements. Calendar Controls, PivotTables, Data Access Pages, and other controls that Windows 11 no longer supports are flagged with specific replacement instructions.

Jet SQL Modernization

Detects and converts 18 Jet SQL patterns to T-SQL equivalents. IIf, Nz, DLookup, date literals, string concatenation, and more — all mapped to standards-compliant SQL for SQL Server migration.

Seeing one of these errors?

Click your error for a step-by-step fix guide.

"Compile error in hidden module" "ActiveX component can't create object" "Unrecognized database format" "Can't find project or library" "Expected: PtrSafe" "Macros have been disabled"

See all fix guides →

Frequently asked questions

Why did my Access database stop working after upgrading to Windows 11?

Windows 11 dropped support for several legacy components that older Access databases depend on, including the Jet 4.0 OLEDB provider, certain ActiveX controls (like Calendar Control), and 32-bit Data Access Pages. LegacyLeaps detects all of these issues and either auto-fixes them or provides step-by-step repair instructions.

Can I migrate my .mdb file to .accdb without losing data?

Yes. LegacyLeaps converts .mdb to .accdb while preserving all tables, queries, forms, reports, and VBA code. It also generates a detailed compatibility report flagging anything that needs manual attention, and provides auto-fix scripts for common issues like Jet-to-ACE provider updates.

Is my data secure during the migration?

Absolutely. For self-service migrations, your files never leave your computer — everything runs locally. For our done-for-you service, all file transfers use 256-bit TLS encryption, we retain zero data after delivery, and all uploaded files are permanently deleted once your migrated files are returned.

How do I fix broken Excel macros after upgrading to Windows 11?

Windows 11 with 64-bit Office requires PtrSafe declarations on all Win32 API calls in VBA. LegacyLeaps is an xls to xlsx converter that automatically scans your Excel files, identifies all API declarations missing PtrSafe, inserts the keyword, updates deprecated API references, and converts your .xls to .xlsx or .xlsm. Most files are fixed in under a minute.

What is PtrSafe and why do my macros need it?

PtrSafe is a VBA keyword required for Declare statements (Win32 API calls) in 64-bit Microsoft Office. Without it, macros that worked in 32-bit Office throw compile errors in 64-bit Office on Windows 11. LegacyLeaps automatically adds PtrSafe to all API declarations during conversion, along with updating pointer types from Long to LongPtr where needed.

Can I bulk convert xls files to xlsx?

Yes. LegacyLeaps supports batch conversion — point it at a folder containing hundreds or thousands of .xls files and it converts all of them to .xlsx (or .xlsm for macro-enabled files). Bulk packs of 10, 25, or 50 tokens offer volume discounts up to 47% off. There is no per-batch file limit.

How do I fix VBA compatibility errors in 64-bit Office?

64-bit Office requires three key changes to legacy VBA code: adding PtrSafe to all Declare statements, changing Long pointer types to LongPtr, and replacing deprecated APIs like FileSearch and CommandBars. LegacyLeaps handles all three automatically during conversion, plus updates DAO 3.6 and ADODB 2.5 references to modern versions.

Don't let a Windows upgrade stop your business

Most migrations complete in minutes. Get your files working again today.

Try the Free Scan Free Consultation

Questions? I'm Gina — I built LegacyLeaps after years of wrestling with broken macros and legacy Access databases in manufacturing. I'm a real person, and I answer every email: gina@legacyleaps.com