Know what the new APKG contains
For supported standard and Cloze note types, the bridge creates a real legacy-compatible APKG with a SQLite collection database and media map. It retains note fields, GUIDs, tags, standard template text, CSS, supported field settings and existing card ordinals. Every exported card is reset to a new-card state rather than copying its interval, due date, repetitions or review history.
The output is intended as a fresh study package. It does not migrate deck presets, filtered-deck state, collection preferences or synchronization state. Modern auxiliary settings and field/template merge identities are not fully represented in the older output schema. These limitations are recorded in the report; the package is not described as a lossless collection backup.
Use a temporary Anki profile for the first import
Import the new APKG into an empty temporary profile before mixing it with an active collection. Compare the number of notes and cards, inspect each note type and check media references. For a Cloze note with deletions c1 and c3, verify both corresponding cards rather than assuming consecutive deletion numbers. For reversed notes, inspect both directions.
Anki can merge matching notes when an APKG is imported into an existing profile. Preserved GUIDs and model identities make that relevant even when the filename says study copy. A fresh scheduling state in the package is not a promise that an existing collection will be overwritten or duplicated in a particular way; destination import options and existing records affect the result.
Keep unsupported cases explicit
Collection packages ending in COLPKG, and the historical collection.apkg naming convention, are read/extract only in this bridge. It does not produce a replacement collection. That distinction matters because importing a collection package can replace the current collection, unlike an ordinary deck import that merges content.
Unknown schemas, unsupported modern note-type settings and inconsistent card structures are not silently flattened into generic cards. When repackaging is unavailable, the result explains why and keeps supported fields/media exports available. Original card HTML and scripts remain in raw exports and supported APKG output, although this page never executes them. Review untrusted decks in an appropriate isolated workflow and keep the unchanged source package available for a full-fidelity Anki export.