Calligra Sheets Compatibility and Migration Decisions

Begin with the evidence boundary

Do not plan a Calligra Sheets migration around an assumed Excel round trip. The existing file-compatibility investigation records two synthetic XLSX fixtures rejected by Calligra Sheets 25.04.2 on Debian 13 Linux on October 16, 2026. Neither loaded its control cells. The investigated installation also showed no XLSX option in the inspected export-format list; no export was performed.

Those are specific observations, not proof that all XLSX imports fail or that every release has identical capabilities. They also are not a successful import, ODS conversion or recipient-side test. Keep those steps unverified until a real test of the intended file and build succeeds.

This decision guide is for the free Calligra Sheets desktop application. Official documentation was checked on 2026-10-21; no new application execution or screenshot was produced. The online handbook identifies itself as revision 2.7, dated March 11, 2013. Its presence under a current documentation URL does not make its menus or format coverage current-release test evidence.

Match the route to the requirement

The historical saving handbook describes ODS as the normal spreadsheet format and choosing a filter for another output format. This is useful orientation, but it does not establish an XLSX exporter in your installation.

Before editing an incoming workbook, record the exact installed version, OS, input format and required output. Inspect the actual available formats without altering the original. If the needed output is absent, stop that migration route rather than merely changing the extension.

For an ODS-based workflow, preserve the source and test a separately named ODS working copy. If the recipient specifically requires XLSX, require a demonstrated export route and recipient-side acceptance before committing. If only a visual reference is needed, agree on that narrower deliverable separately; it does not replace an editable workbook requirement.

Classify the workbook before trying it

Write down the features essential to the task: sheets, formulas, dates, text identifiers, names, charts, validation, external data and printed layout. Add the source application’s expected values or a reference view where appropriate. Do not infer preservation of any feature just because the file appears in an Open dialog.

Use three independent questions:

1. Can this build load the file? If import fails, record the exact message and stop. Do not mark downstream checks as passed or begin cosmetic repairs to a workbook that never loaded.
2. Does the loaded workbook behave correctly? Check values and formulas before adjusting widths, fonts or number formats.
3. Can the agreed output be produced and accepted? Inspect the actual export choice, then test the resulting copy in the recipient’s application. A successful local save is not recipient acceptance.

The linked compatibility investigation contains the genuine failure screenshots and the detailed formatting checklist. This page organizes the go/no-go decision rather than repeating those repair instructions.

A conditional acceptance exercise

Only after a practice workbook can actually be opened or created in the chosen environment, enter A2 = 7, B2 = 6, A3 = 3 and B3 = 4. Enter =A2*B2 in C2, =A3*B3 in C3 and =C2+C3 in C4. Independent arithmetic gives 42, 12 and 54.

Use a separately named copy in the agreed output format. If that route is available and succeeds, reopen the copy, inspect the formulas and change A3 to 4. Expect C3 = 16 and C4 = 58. Restore A3 to 3 and confirm 54. Record the same checks in the recipient application where required.

These expectations are a proposed diagnostic exercise, not results observed in Calligra or an imported XLSX. If loading or exporting is blocked, mark the remaining stages Not tested: earlier stage blocked. Passing this arithmetic control would still leave the real workbook’s other essential features to be checked.

Keep a recoverable decision record

Record input/output filenames, application builds, selected filters, warnings, expected versus actual results and outstanding dependencies. Retain the original and any failed fixture unchanged. A changed extension or a screenshot from another application does not establish a successful Calligra conversion.

Accept a migration only for the tested route and required features. Otherwise keep the current workflow and use the troubleshooting reference to narrow a reproducible issue. The inherited XLSX import and export limitations remain unresolved by this page; no current-release compatibility matrix or universal support claim is supplied.