Cellwright

Excel VBA → LibreOffice

Move beyond Excel.
Keep what works.

Your workbooks have years of work in them. Cellwright helps you inspect the VBA, rebuild supported code and understand what comes next.

Local processing. Original source retained. Every unresolved item explained.

01 Your files stay on your machine

02 Rules you can inspect

03 Scan without running macros

One workbook. A clear next step.

Less guessing.
More progress.

Go from a workbook full of macros to an understandable migration plan. See the generated code, the original beside it, and a checklist of what still needs work.

Conversion and testing have separate statuses. Skipped parts remain clearly marked as unknown coverage.

Walk through your first migration
Cellwright local dashboard showing the sample workbook conversion, its checklist and disabled macro execution.
Actual dashboard · bundled sample workbook
Candidate generated. Macro execution disabled.

Understand the workbook.

Inventory VBA, forms, controls and Power Query. Find duplicates, blockers and unknown coverage before you begin.

Rebuild what’s supported.

Generate Basic or Python candidates and review the diff. Supported UserForms and ActiveX controls get editable layouts and source-matched event candidates.

Know what remains.

Each unresolved item has a location, a reason and a next action. Choose routines, inputs and cells for a comparison when you explicitly enable execution.

Getting started

Start with the sample.
Bring your own next.

The archive includes everything Cellwright supplies: the scanner, local dashboard, migration tools and a sample workbook. Setup checks tell you which dependencies to install.

Read the complete migration guide
  1. Extract the full archive.Python 3.11+ runs the dashboard. LibreOffice is needed for Basic/UNO conversion.
  2. Open the launcher.“Start Cellwright.cmd” on Windows. “start-cellwright.sh” on Linux. The dashboard opens in your browser.
  3. Scan the demonstration workbook.Create a candidate, inspect the checklist and compare its source. Scanning and conversion never run macros.
  4. Review, then verify deliberately.Execution requires a startup flag and consent for each comparison. A generated candidate is not a passed test.

Honest about the limits

A useful start.
A result you still review.

Custom ActiveX controls, complex or dynamic forms, lifecycle events and unsupported code stay on the manual checklist. Skipped workbook parts stay marked as unknown.

Form display and new Basic helper behavior are not runtime-verified. Effort ranges remain uncalibrated planning estimates.

Forms & controls guide Manual migration recipes Validation & limits