Migrating Plasmid Files Between Design Tools: A Checklist

An implementation checklist for migrating plasmid map files between design tools is a file-identity job. Export an interchange copy, keep the native files, and refuse the cutover until topology, feature spans, and primer names survive a second-person open. A prettier empty circle is a failed migration, not a successful switch.

What Must Survive the Move

The object is the authoritative map: sequence, circular or linear topology, and the annotations the lab treats as true. Screenshots do not migrate. Native files stay until verification passes. Interchange formats are copies. No converter is documented here as lossless. Primer names, enzyme sets, and history notes are part of identity when the lab treats them as true. If those objects live only in the old software, write them down before the convert click, or they will not be there to verify.

This is not a rewrite of the shared-workspace definition or of the desktop-versus-cloud decision. Those pages already exist. This page moves files.

Steps: Inventory, Convert, Import

1. Inventory native files, owners, and which file is canonical for each construct. Record the source tool and the destination tool.
2. Choose a documented interchange. SnapGene’s convert list includes GenBank Standard, FASTA, and native SnapGene DNA. Other vendors need their own official converter page before you name their behavior.
3. Convert with a documented path. SnapGene’s batch convert is File → Batch Convert File Format. Their import article is File → Open, then export if needed. A Vector NTI database import exists on that page as one documented path, not as this checklist’s subject.
4. Import the interchange files into the destination tool.
5. Do not delete natives. A conversion that drops qualifiers is not a cutover. Keep the native folder read-only until the second-person audit signs the sample set.

Expected Result and Verification

Expected result: a second person opens a sample of maps — ten is a reasonable audit set for a small collection — and restates topology, feature count, and two named primers without the old software. Verification: circular stays circular; feature coordinates match the native file; dropped notes are listed as a known gap, not ignored. One pretty import is not a collection. If the sample set is only the newest plasmid, you have audited a screenshot, not a library. Include one linear fragment, one multi-insert map, and one file the lab still argues about.

Keep the Native Files Until Verification Passes

GenBank often carries features and can still drop history, enzyme sets, or tool-specific objects. FASTA drops almost everything except the letters. If features vanish, restore from natives, try another documented interchange, or re-annotate on purpose and record the gap. Silent re-annotation is a second migration failure. Version identity after the move is a version-control job, not a convert click. A gap list that names which qualifiers dropped is a finished migration. A folder of pretty circles with no gap list is an unfinished one.

This Is Not a SnapGene-Versus-Cloud Rematch

Desktop-versus-cloud and workspace pages stay where they are. After files import, a map such as ZettaGene is one destination for viewing ORF, primer, and restriction-site annotations. Official copy documents those views. It is not the reason to switch, and it is not a lossless converter. The takeaway is identity survival — not a prettier empty map. If the destination tool cannot show a primer that the native file still has, the migration is incomplete even if the circle looks cleaner.

Frequently Asked Questions

What must still be true after plasmid files are migrated?

Sequence, topology, and the feature spans the lab treats as true. A prettier empty map is a failed migration.

Is GenBank a lossless copy of a native map file?

No. It is a common interchange. Notes, history, and tool-specific objects can drop. Keep natives until verification passes.