Check a collection export before you need it
A small portability test for your card list, using a copy and a few deliberately awkward records.
An export button is the beginning
A collection file is useful only if you can understand what it contains. Before relying on a large export, test a small copy with records you know well. This is a proposed collection-management exercise, not a claim that CardFrame currently imports a particular app or file format.
Keep your original collection unchanged. Save the export date, source app and the options you selected. A filename such as collection-final does not explain which fields were included or whether the file represents all cards or only a filtered view.
Choose records that expose differences
Use a small sample with a repeated card name, two different printings, a non-English name and a quantity greater than one, if those cases exist in your collection. Check each record against the original app. The aim is to discover whether important distinctions survive, not to make the sample look tidy.
Write down the identifier, set, collector number, language, finish and quantity fields that matter to you. Do not assume that two rows with the same display name represent the same printing. Leave any uncertain mapping visible before combining records.
Inspect the file without overwriting it
Open a copy in a tool that lets you inspect both the header and values. CSV is a family of practical conventions: RFC 4180 documents a common format, including quoted fields containing commas. It does not define a universal trading-card collection schema.
Check that punctuation inside a name has not split a row into extra columns. Confirm that accented characters remain readable and that identifiers have not been silently reformatted. A spreadsheet can display a plausible table while changing a value you wanted to preserve exactly.
Test a destination only if it supports the file
Read the destination's current import instructions before attempting a transfer. Map fields explicitly and use a temporary collection or supported preview where available. Do not overwrite the only good copy merely to see whether an import works.
In a fictional test, two printings merge because the destination matches only on the card name. The useful result is a discovered mapping problem, not a successful migration. Keep the source export and resolve the identifier question before repeating the transfer at scale.
Keep a portability note
Record the source, date, selected fields, sample checks and unresolved limitations. A checked export is still a snapshot; it does not update itself when you trade or add cards. Choose a repeatable backup habit that fits how often your list changes.
See the scanning guide for the broader collection workflow. CardFrame remains a presale project; review its current product and reservation terms for the actual offer. This worksheet does not announce a shipped import feature. Format reference checked September 20, 2026.