Your organization has thousands of .xls files. They've been accumulating since the early 2000s — in network shares, user desktops, archival drives, and SharePoint document libraries. Microsoft 365 is rolling out. Windows 11 is mandated by IT security policy. And now every department is discovering, one Monday morning at a time, that their critical files don't work the way they used to.
You've been tasked with finding a bulk Excel conversion solution. You've got three weeks and a skeptical finance director watching the budget. This guide cuts through the noise and gives you the evaluation framework that actually matters — the five criteria that separate tools that work for enterprise migrations from tools that look good in a demo and fail in production.
The market for Excel conversion tools is flooded with products that solve a different problem than yours. Most of them were designed to convert an .xls file you downloaded from somewhere into a format a modern application can open. That's a simple format conversion — fine for a single file with no macros.
Your problem is different. Your files:
A tool that converts an .xls file into an .xlsx file is easy to build. A tool that does it without stripping the macros, without corrupting the formulas, without breaking the ActiveX controls, across 5,000 files in a batch, with an audit log, on a machine that never connects to the internet — that's a different product entirely.
This is the gate criterion. If a tool strips macros, it fails — full stop. No amount of speed, price, or UI quality compensates for this.
Why do macros matter so much? Because in most organizations, the files that matter most are macro-enabled. The simple data files — pure data with formulas — would have been migrated by the person who created them the first time they opened them in Excel 2007. The files still in .xls format in 2026 are there because they're complex. They have macros. They have custom functions. They have automation that runs on file open, on button click, on cell change.
Ask any vendor: "Does your tool preserve VBA macros?" Then ask the follow-up: "Show me a conversion of a file with a macro that calls a Windows API function." That's the real test.
Here's how the major options perform:
| Tool | Macro Preservation | Notes |
|---|---|---|
| CloudConvert | Fails | Strips all VBA. No workaround. |
| Zamzar | Fails | Strips all VBA. No workaround. |
| PowerShell Open/Save | Partial | Preserves module code but breaks API declarations and broken references silently. |
| LegacyLeaps | Passes | Preserves VBA modules, class modules, forms, and API declarations. Flags broken references. |
Before any tool leaves your shortlist, answer this question: where do the files go during conversion?
Cloud converters upload your files to a third-party server. For .xls files containing financial models, customer data, or internal pricing, this is a data security problem in most regulated environments — and a GDPR issue if any of those spreadsheets contain EU personal data.
The practical questions to ask vendors:
For most enterprise IT teams, the answer is simple: the tool must run locally. Full stop. Your files never leave the machine.
LegacyLeaps is a Windows desktop application. It runs entirely on-premises. Files are processed in memory and written to disk on the local machine. There is no cloud component, no telemetry that includes file content, and no data residency concern. For regulated industries — healthcare, finance, government — this isn't a nice-to-have. It's a requirement.
Most consumer-grade tools advertise "batch conversion" but mean "convert multiple files one at a time." For a 5,000-file migration, you need to understand:
.xls with no macros might convert in under a second. A complex .xlsm with 20 VBA modules might take 30 seconds. Understand the expected throughput for your file profile.LegacyLeaps has no hard batch limit. It logs successes and failures at the file level. It processes files in parallel and produces a conversion report you can use for verification.
In an enterprise migration, "I think it worked" is not an acceptable completion state. You need to be able to answer:
A conversion tool without output logging is producing an unverifiable result. If your finance director asks "are you sure everything migrated correctly?" you need more than "it seemed fine in testing."
Minimum audit requirements for an enterprise migration:
LegacyLeaps generates a per-file conversion report after every batch run. The scan phase produces an inventory of macros, ActiveX controls, and potential issues before conversion begins — giving you a risk assessment you can review with stakeholders before committing to the migration.
Run LegacyLeaps's free scan on your file inventory. Get a full report: which files have macros, which have ActiveX controls, which are highest-risk. No conversion until you're ready.
Download Free ScannerFor enterprise migrations, the math on pricing models can diverge dramatically depending on your workload profile.
Works well if you have a steady, ongoing conversion need — for example, an organization that receives legacy files from clients regularly and converts them as part of a workflow. If you're paying $200/month to convert 50 files/month, that's $4/file — expensive but predictable.
Works poorly for a large one-time migration. Paying $200/month for 8 months to migrate 5,000 files costs $1,600 — before counting staff time.
Better for burst workloads. You buy tokens, convert your files, and stop paying. For a one-time migration of thousands of files, this model is almost always more cost-effective.
LegacyLeaps uses token-based pricing. You purchase Excel tokens, use them for your migration, and you're done. No ongoing monthly charges. No pressure to "get value" from a subscription you're no longer using.
For organizations that don't want to manage the migration themselves, LegacyLeaps offers a done-for-you service at a flat rate. You ship the files, LegacyLeaps's team handles the conversion, and you receive converted files plus a complete migration report.
This makes sense when: the migration scope is large, the files are complex, or internal IT bandwidth is constrained. The cost is fixed and predictable, and you're buying the outcome — not the tool.
| Criterion | CloudConvert | Zamzar | PowerShell | LegacyLeaps |
|---|---|---|---|---|
| VBA macro preservation | No | No | Partial | Yes |
| Local processing | No | No | Yes | Yes |
| No batch size limit | No | No (400/day) | Yes | Yes |
| Audit log / report | Basic | Basic | Manual | Full report |
| ActiveX preservation | No | No | Partial | Yes |
| Token/flat-rate pricing | Subscription | Subscription | Free | Token / DFY |
| Money-back guarantee | No | No | N/A | 30-day |
Every IT team asks about PowerShell. It's free, it's scriptable, it requires no procurement approval, and it seems like it should work. Here's the honest assessment:
PowerShell can automate Excel's SaveAs function to convert .xls to .xlsx. It works reasonably well for simple files — pure data with formulas. For those files, it's a legitimate option.
It falls apart in these scenarios:
.xls file with 32-bit Declare statements and re-saves it, the resulting .xlsx has VBA that will throw a compile error when the macro runs. PowerShell doesn't flag this — you only find out when a user tries to run the macro.The bottom line: PowerShell is appropriate for a small batch of simple files where you can manually verify every output. It's not appropriate for a production migration of complex macro-enabled workbooks at scale. See our detailed comparison: Batch Convert .xls Files — PowerShell vs LegacyLeaps.
If you need to justify the purchase to a budget holder, here's the framework:
Every month you don't migrate, the risk compounds. Windows 11 updates may change the Jet/COM subsystem. Excel updates may add new compatibility warnings. A macro that works today may stop working after a patch. And when it breaks, it breaks at the worst time — month-end, quarter-end, a client delivery deadline.
One broken report that costs 4 hours of staff time to diagnose and recover is worth more than LegacyLeaps's token cost for the entire file inventory.
The free scan produces a risk inventory that has value independent of the conversion purchase. You can use it to brief leadership on the scope of the legacy file problem — which files are at risk, how many macros are in play, what the exposure looks like. That's a governance deliverable you can produce before spending a dollar on conversion.
Once you've selected a tool, a successful enterprise migration follows this sequence:
.xls, .xlsm, and .xlsb files across all drives and shares. Use the PowerShell script from our pre-upgrade backup guide..xls files in a read-only archive for 90 days. They're your rollback if anything surfaces late.The five most important criteria: VBA macro preservation (most tools strip macros entirely), local processing (cloud converters create data security issues), batch size limits (some tools cap at hundreds of files), audit logging (you need a record of what was converted), and pricing model (per-file token pricing scales better than subscriptions for burst workloads).
No. CloudConvert, Zamzar, and similar online tools strip VBA macros during conversion. They are designed for simple format conversion, not for preserving the programmatic logic embedded in business Excel files. If your .xls files contain macros, you need a tool built specifically for legacy Office migration.
Yes, for most enterprise environments. .xls files often contain sensitive financial data, customer records, or internal pricing models. Uploading them to a third-party cloud service creates data residency, GDPR, and intellectual property risks. LegacyLeaps keeps files entirely on-premises.
LegacyLeaps has no hard batch size limit. Organizations have used it to convert thousands of files in a single operation. Throughput depends on file complexity and hardware, not an artificial cap.
For organizations with a large one-time migration backlog, token-based pricing is more cost-effective than a subscription. You pay for what you convert. LegacyLeaps uses token-based pricing for self-service and flat-rate pricing for done-for-you enterprise migrations.
Start with the free scan. Get a full inventory of your legacy files, macros, and risk profile — before you spend anything on conversion. 100% Money-Back Guarantee: if LegacyLeaps doesn't preserve your formulas, macros, and formatting, we'll refund every penny.
Download Free Scanner Talk to Us About Done-For-YouPractical fixes for legacy Excel and Access problems. No spam.