LibreOffice Calc field guide
LibreOffice Calc Compatibility and Migration Guide
Choose an exchange route, identify fragile workbook features and prove the result with changed-input checks.
The short answer
Opening an Excel workbook in Calc is not proof of a successful migration. Preserve the original, test the features your workflow actually needs and verify the saved file in the intended recipient application.
Choose the file route
Protect table references
Set an acceptance gate
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, first checked on 2026-10-21 and rechecked on 2026-10-23, 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.
Choose a file route
Choose by what the next person must do. The route below is a planning aid; the format-conversion tutorial contains the detailed workbook checks.
| Intended task | Candidate route | Acceptance check that matters |
|---|---|---|
| Continue editing in Calc | Separate ODS working copy | Verify formulas and workbook objects, including the structured-reference exception below. |
| Send an editable workbook to an Excel user | Separate XLSX exchange copy | Open in the actual recipient build; test formulas, charts, links and required automation independently. |
| Import rows and columns from another system | CSV data, imported into a new sheet | Check delimiter, encoding, quoted fields, dates and identifiers. CSV is not a multi-sheet workbook backup. |
| Send a fixed report that does not need editing | PDF output | Check page breaks, repeated headings and clipped columns using the print/PDF guide. |
For a small, reusable import fixture, use the existing items and quoted commas CSV, not a new duplicate file. The starter-file guide explains its three records, numeric import checks and expected line total of 65.75. That CSV contains data only: it does not test formulas, formatting or macros surviving a workbook conversion.
CSV handoff: displayed amount or underlying value?
Choose what the recipient needs before exporting. Export text files Help, labelled LibreOffice 26.8 Help, checked October 26, 2026, documents Save cell content as shown as enabled by default: it exports the displayed content with number formatting. Turning it off exports raw content instead. Some formatted output may no longer import as a number. This is documentation for free desktop Calc, not an observed export or a guarantee for a particular installed build.
Reuse the existing number, date and currency formatting exercise, rather than creating another fixture. Its B6 formula =1234567/1000 has mathematical value 1234.567, while a two-decimal display represents 1234.57. The difference is 0.003. These are independent arithmetic expectations, not promised literal CSV strings.
Plan two separate, disposable export trials
- Retain the ODS practice master and its formula. From the same starting master, propose separately named raw-value and display-value CSV copies; never overwrite the master or derive one trial from the other. Record Calc build, operating system, cell and export locale, character set, field delimiter and text delimiter. CSV is a single-sheet exchange, not a workbook backup.
- For a value handoff, check that formulas are not being displayed for export. The formula/CSV Help documents the Formulas checkbox in Tools → Options → LibreOffice Calc → View (use LibreOffice → Preferences on macOS): enabled exports formula text; disabled exports calculation results. Raw-content export alone is not a promise of a numeric result if formula export is selected.
- In Save As, choose Text CSV and Edit filter settings to inspect export options. For the raw-value trial, clear Save cell content as shown; for the display-value trial, enable it. Keep other trial settings recorded and consistent. Inspect each resulting file’s literal text before importing it into the intended recipient.
- Check the recipient’s numeric interpretation, not just its appearance. For this controlled input, a raw numeric value multiplied by 1000 should be 1234567; the two-decimal numeric value multiplied by 1000 should be 1234570. A text field or formula string is not a passing numeric check. Record the actual decimal spelling, quoting and parsing; none is promised here. Mark every unperformed export/import Not tested.
Do not confuse export with calculation precision. Precision as shown controls whether calculations use displayed rounded values; it is not the CSV export checkbox. The practice arithmetic assumes that calculation option is off. Do not change production calculation settings to make an export pass. Raw export cannot recover precision already lost through rounding or earlier data loss. If the recipient needs 1234.567 but receives 1234.57, hold the handoff and investigate a copy; do not silently accept the displayed amount as equivalent.
Date handoff: verify the day-zero basis, not just the number
A numeric date can still mean the wrong calendar day. For mixed text and numeric inputs, use the existing text-to-date diagnosis and conversion lesson; this acceptance check addresses the date basis after type has been identified, not another conversion recipe.
Date & Time Help describes dates as offsets from day zero. The Calculate settings Help documents the default 1899-12-30 basis and a 1904-01-01 basis, among other choices. These two illustrated bases are not an exhaustive list. Both sources were checked in LibreOffice 26.8 Help on October 26, 2026; the label is a documentation scope, not proof of an installed build or a successful transfer.
Use 2026-10-01 as a modern, date-only acceptance control in a disposable copy. Independent calendar arithmetic gives:
| Interpretation | Expected mathematical result |
|---|---|
| Days from 1899-12-30 to 2026-10-01 | 46296 |
| Days from 1904-01-01 to the same intended date | 44834 |
| Raw number 46296 interpreted as days after 1904-01-01 | 2030-10-02, not the intended date |
| Next day, 2026-10-02, measured from 1899-12-30 | 46297 |
Before accepting a handoff, record the actual source and receiver date bases, application builds, source type (text, numeric value or formula), intended calendar date, transfer method and observed receiver result. Inspect the receiver’s calendar date and numeric value separately; numeric type alone does not establish meaning. Record an unperformed transfer as Not tested. These arithmetic controls do not claim how an actual paste, CSV export/import or recipient application behaves; CSV output is not assumed always to contain raw serial numbers.
Hold if either basis is unknown or the intended date does not match. Do not apply a blanket 1462-day adjustment or change production date settings to force agreement. Preserve the original, investigate a copy and verify the actual transfer before accepting it. This control does not establish early-1900 compatibility, time-zone conversion or equivalence across recipients. Existing native-test exclusions remain unchanged.
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
| Decision | Evidence needed | Next action |
|---|---|---|
| Accept this pilot | Required calculations, objects and recipient checks pass for the recorded builds. | Keep the original and acceptance record; expand only to similar files. |
| Repair and retest | A specific discrepancy has a documented fix. | Repeat the failing case and a changed-input test after save/reopen. |
| Hold the migration | Essential automation, reference behavior or recipient execution is unverified or fails. | Retain the existing process; do not relabel fixed values as working formulas. |
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.
Independent guidance, not affiliated with LibreOffice Calc. The guide illustrations and icons are original concept artwork, not application screenshots or official logos. Any application screenshot in the article has its own evidence note.