Windows 11 broke your Access database?

Drop your legacy file. See what's broken.

LegacyLeaps scans .xls and .mdb files for modern Office risks, converts safe files into a separate output package, and stops before VBA could be stripped. No signup. No email. Just results. First scan 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

30-second walkthrough

See the safe conversion path.

The original stays untouched. The converted copy, preserved original, and validation report land in one reviewable package.

Scan one file free

Here's what a scan looks like

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

7Total Issues
3Critical
2Warnings
5Guided Fixes
IssueSeverityGuidance
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
Remediation guidance available for 5 of 7 issues

Scan Your Files — Free

100%
Local processing — files never leave your machine
< 5 min
Typical scan and compatibility report
30 day
Money-back guarantee — no questions asked

Simple, transparent pricing

Every tier runs the exact same conversion — no tier converts more of your file than another. Pro adds a 30-day re-do warranty, priority support, and volume packs. Certified adds a founder-reviewed validation report and signed certificate.

Excel (.xls → .xlsx)

Standard
$99
per file
  • Full-fidelity .xls to .xlsx (VBA, PtrSafe, ActiveX preserved)
  • Compatibility report
  • Upgrade to Pro anytime (+$100)
Buy Token — $99
Pro Most Popular
$199
per file
  • Same full-fidelity conversion as Standard
  • 30-day re-do warranty
  • Priority support
  • Volume packs — save up to 25%
Buy Token — $199
Certified
$599
per file
  • Everything in Pro, plus:
  • Founder-reviewed validation report
  • Signed certificate of successful conversion
  • Best for audits & compliance
Buy Token — $599
Pro Bulk
$1,690
$169/filesave 15%
Buy Pack

Access (.mdb → .accdb)

Standard
$199
per file
  • .mdb to .accdb — tables, queries, forms, reports & VBA carried over
  • Report flags Jet SQL, ActiveX & VBA fixes for 64-bit Office
  • Upgrade to Pro anytime (+$300)
Buy Token — $199
Pro Most Popular
$499
per file
  • Same conversion as Standard
  • 30-day re-do warranty
  • Priority support
  • Volume packs — save up to 25%
Buy Token — $499
Certified
$1,299
per file
  • Everything in Pro, plus:
  • Founder-reviewed validation report
  • Signed certificate of successful conversion
  • Best for audits & compliance
Buy Token — $1,299
Pro Bulk
$4,240
$424/filesave 15%
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 $99/file. Or request a free consultation and we handle everything.

3

Get clean, working files

Converted copies, preserved originals, and compatibility guidance. 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. Safe format conversions are automated; VBA remediation is guidance-only in this build.

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.

Frequently asked questions

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

Windows 11 and 64-bit Office expose incompatibilities in older Access databases, including Jet providers, ActiveX controls, and legacy Data Access Pages. LegacyLeaps reports these risks and provides step-by-step remediation guidance.

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

LegacyLeaps creates a separate output package and keeps the source database untouched. Conversion depends on the installed ACE engine; the report identifies tables, queries, forms, VBA, and provider issues that require validation.

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 Win32 API calls in VBA. LegacyLeaps converts the file to .xlsm and rewrites the VBA automatically — inserting PtrSafe, updating pointer types to LongPtr, and replacing deprecated APIs — then compiles and validates it. Most files are fixed in under a minute.

What is PtrSafe and why do my macros need it?

PtrSafe is required for Declare statements in 64-bit Microsoft Office. LegacyLeaps adds PtrSafe to your Declare statements automatically during conversion, updates Long pointer types to LongPtr where needed, and replaces deprecated APIs.

Can I bulk convert xls files to xlsx?

LegacyLeaps can scan and convert folders in batches — point it at a folder of .xls files and it converts each one to .xlsx, or .xlsm for macro-enabled files with the VBA rewritten for 64-bit Office. Bulk packs of 10, 25, or 50 tokens are available at volume discounts up to 25% off.

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

64-bit Office commonly requires PtrSafe, LongPtr, and replacements for deprecated APIs. LegacyLeaps handles all three automatically during conversion, then compiles the rewritten VBA to confirm it builds. Your original file is never modified.

Don't let a Windows upgrade stop your business

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

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@maniginam.dev