LibreOffice Calc Compatibility and Migration Planning
Decide what must keep working before converting files
A migration is a change to a working process, not merely a change of filename. Preserve the original workbook and identify who needs to edit the result, which application they use, and which outputs must remain correct. Use a separately named Calc working copy and an exchange copy; do not retire the original because a file opens successfully.
This planning reference uses LibreOffice 26.8 desktop Help, checked on 2026-10-21, for the free desktop application. It is not a new native test, an Excel edition comparison or a guarantee for every workbook. The detailed ODS-to-XLSX control-workbook tutorial supplies the conversion procedure; this page helps decide whether a migration is ready to attempt or accept.
Make a dependency inventory
For each workbook, record its owner, original format, location of the preserved original, intended recipient/build, and required behavior. Separate these categories:
- Calculations: important totals, less-common functions, named ranges, date assumptions and any external inputs.
- Interaction: validation, form controls, macros and buttons people use to complete their work.
- Presentation: charts, conditional formatting, printed pages and embedded objects.
- Dependencies: other files, linked data, fonts and any automation outside the workbook.
LibreOffice’s conversion limitations identify formulas, pivot tables, some controls, newer chart types, conditional formatting and embedded objects as potential conversion challenges. That is a risk list, not a claim that every instance fails. Prioritize the features that your workbook actually uses.
Treat VBA and other automation as a separate acceptance item. The help describes only partial Excel-script behavior with configuration requirements, not full equivalence. Do not enable unfamiliar macros or lower security to make a trial appear successful. If essential automation has not been independently reviewed and tested in the intended environment, mark the migration Blocked: automation unverified rather than silently replacing its output with fixed values.
Choose the pilot before the batch
Start with one representative, non-sensitive workbook copy containing a real dependency from each relevant category. A small arithmetic-only file cannot establish that a macro-driven reporting workbook is ready.
For continuing work in Calc, an ODS working copy is often useful, but do not assume it preserves every reference type. Check the structured-reference exception below before choosing the master format, and always keep the preserved source. If another application needs an editable file, agree on the exchange format and test the receiving application. For importing flat data, use the separate CSV import guide; a flat table is not a substitute for a complete workbook.
LibreOffice documents a Document Converter wizard that copies and converts a folder’s Office documents to OpenDocument formats. The availability of batch conversion does not establish fidelity. Do not point it at the only originals or begin a bulk rollout before the pilot’s acceptance criteria pass.
A small acceptance-record exercise
Use this as an independently calculated control, not as evidence that conversion passed. In a practice workbook enter B2 = 4, C2 = 12, B3 = 3 and C3 = 15. Put =B2*C2 in D2, =B3*C3 in D3 and =D2+D3 in D4. The expected results are 48, 45 and 93.
Record the expected and actual D4 value in three stages: original application, converted working copy, and intended recipient. At each performed stage change B3 to 4: D3 must become 60 and D4 108. Restore B3 to 3 and confirm 93 again. Inspect the formulas themselves, then save, close and reopen the test copy. Mark an unperformed stage Not tested, not Pass.
Add a separate row to the acceptance record for each essential feature from your inventory. A correct 93 does not prove that a named range, external link, chart or macro survived. Use the linked conversion tutorial for a richer control workbook instead of treating this small exercise as exhaustive.
Check structured references before choosing ODS
This exception follows Calc Guide 26.2, published February 2026, and desktop Help labeled 26.8, checked on 2026-10-22. It applies to the free LibreOffice desktop application; it is documentation-based, not a tested conversion result.
The Database Table Reference help warns that saving to ODS converts structured references into direct references. Do not confuse the same displayed total with retention of the table/column expression. The Calc Guide’s database chapter describes Excel tables loading as Calc database ranges, but its XLSX retention statement specifically describes saving in Excel. That sentence alone is not proof that this workbook survives a Calc-to-XLSX round trip unchanged. Keep that result Not tested until checked in the intended builds.
A reference-sensitive control
Use a fresh, disposable workbook with a sheet named Orders. Enter this original fixture in A1:B4:
| Item | Units |
|---|---|
| Clips | 8 |
| Folders | 13 |
| Labels | 6 |
Following the database-range definition procedure, select A1:B4 and choose Data → Define Range. Name it OrderCheck, enable Contains column labels, and leave Contains totals row off. Add/confirm the definition. This is a vertical database range, not merely a formatted rectangle or an ordinary named expression.
In D2 enter =SUM(OrderCheck[Units]); in D3 enter =SUM(B2:B4). Both should total 27. The field-name reference excludes the header. Retain the full database name in the Calc formula. These syntax rules are described in the Database Table Reference help linked above.
Record both formula texts and results before saving. The formulas deliberately have the same answer, so their displayed values cannot tell you which reference representation survived.
Save, reopen, and challenge the result
- Preserve the original input file, if any, untouched. Record the exact Calc version, operating system, source extension and destination format. Save separately named ODS and XLSX test copies from the same pre-conversion starting state, not one converted copy from the other. If recreating this fixture, enter the two formulas afresh before each format test.
- Read format warnings. If the available choices or consequences are unclear, cancel and retain the original. Close and reopen each saved copy. Copy D2/D3’s actual formula text into your acceptance record, then record their values. Do not prescribe an exact serialized address spelling: record what your build actually produces.
- Change B3 from 13 to 18. A working sum over B2:B4 must now show 32; restoring 13 must restore 27. This distinguishes a live calculation from a result that only happened to look right on opening. It does not prove table-reference retention.
- On another disposable copy, put Tabs and 4 in A5:B5. Explicitly extend the database definition to A1:B5. Inspect D2’s formula and references again. A sum that actually includes B2:B5 should show 31; one still limited to B2:B4 should show 27. Classify the observed behavior from the actual reference, rather than assuming automatic expansion. Save/reopen and repeat the check.
- If another application must edit the file, repeat the relevant checks there using an already available, permitted free version. Otherwise mark recipient-side behavior Not tested. Do not infer paid-desktop parity from a web or mobile result.
Accept current-value correctness and reference preservation as separate criteria. If your workflow requires readable table formulas or range-growth behavior and those are lost or untested, hold the migration even when 27 is correct. For an intentional direct-reference conversion, document the new maintenance procedure and retest future range changes. No Calc serialization, XLSX round-trip, recipient execution or screenshot is claimed for this exercise.
Accept, repair, or hold
Accept only the specific files, features and application builds actually checked. Record each discrepancy with its cell/object, expected behavior, actual behavior and owner. If a display changes but values remain correct, assess it against the agreed presentation requirements. If a required calculation or dependency is unverified, retain the original process and investigate a copy through the troubleshooting reference.
No new screenshot, native conversion, macro execution or recipient-side test was performed for this planning page. Existing tutorial limitations remain in force; an accepted pilot is not universal format compatibility.