Gnumeric Compatibility and Migration Decisions

Check the installed route, then test the workbook

An import format and an export format are separate capabilities. Before moving a workbook into the free Gnumeric desktop application, record the installed version, operating system, incoming format and required outgoing format. Preserve the original file and plan a separately named native working copy.

This reference uses the official Gnumeric manual checked on 2026-10-21. Its general instructions are not a release-specific compatibility certification. Our existing XLSX export and reopen tutorial reports a bounded Gnumeric 1.12.57 on Debian 13.6 test. Its separately reviewed 1.12.62 source definitions do not turn that test into a 1.12.62 runtime result, nor do they establish success in Excel.

Inventory availability without guessing from an extension

The Opening Files manual explains that active plugins contribute the formats shown in the File Open dialog. If a documented format is absent, inspect the installed plugin list rather than renaming the file or assuming the manual describes your exact package. Record the missing capability as a blocker until the authorized installation can provide it; do not install an unknown plugin to force a conversion.

For a command-line inventory, the official ssconvert documentation provides:

ssconvert --list-importers
ssconvert --list-exporters

Keep both outputs with the installed version and test date. An importer appearing in the first list does not prove that the corresponding exporter appears in the second. Neither list proves that formulas, formatting or embedded objects will survive a particular conversion. If the command itself is absent, use the installed application’s dialogs to inspect availability and mark command-line conversion untested.

The manual describes PDF and PostScript as printing-system outputs rather than ssconvert conversion formats. Do not design a batch export around an assumed ssconvert PDF writer.

Select a reversible pilot

Choose a workbook copy with the features you actually depend on: multiple sheets, dates, text identifiers, names, charts, validation, external links or specialized calculations. Record required outputs and the recipient’s exact application/build before trying a conversion.

The manual’s simple command example is ssconvert myfile.xls myfile.gnumeric. For a pilot, use distinct input and output paths in a writable test location, keep the source unchanged, and inspect the resulting file in Gnumeric. This command is a documented example, not a command executed for this page. A command finishing without an error is not the acceptance test.

Use the existing XLSX tutorial for its exact saver choice, genuine historical screenshots, benchmark downloads and documented test limits. Do not use its simple arithmetic result as evidence for untested macros or advanced features in another file.

Practice recording a decision

Create a small practice sheet with A2 = 6, B2 = 8, A3 = 2 and B3 = 11. Enter =A2*B2 in C2, =A3*B3 in C3 and =C2+C3 in C4. Independently calculated expectations are 48, 22 and 70.

After any pilot conversion, inspect those formulas and values, then change A3 from 2 to 3. C3 should become 33 and C4 81. Restore A3 to 2; expect 70 again. Save and reopen the pilot copy and repeat the check. If delivery to another application is required, repeat there too. Record actual results separately; these expectations are not newly observed native results.

A useful decision record contains the original and output filenames, both versions/platforms, importer/exporter labels, warnings, control results and outstanding feature checks. Mark Not tested for anything not performed, and Blocked for a required format or feature that has not been shown to work.

When not to migrate yet

Keep the source workflow if the recipient cannot accept the available output, a required plugin is unavailable, formula behavior changes, or essential dependencies remain untested. Investigate a copy with the troubleshooting reference, retaining warnings and the smallest reproducible example. Do not overwrite a source just because the new copy looks plausible.

No new Gnumeric execution, conversion or screenshot was produced for this decision guide. Compatibility remains specific to the files, features and builds actually tested.