Migrate a Benchling project

Prepare the export

Create the export through Benchling's current supported export flow.

Start the migration

1. Select the + button next to a project name.
2. Select Migrate from Benchling.
3. Choose the local ZIP or folder.
4. Keep the source export until review and backup are complete.

Choose a Benchling ZIP or folder

In the local export intake, add the downloaded Benchling ZIP or its unzipped export folder:

1. Drop the export onto Drop your Benchling export here, or select Choose file or folder….
2. If you selected Choose file or folder…, select the ZIP or folder in the Choose a Benchling export dialog.
3. Wait for the intake to show Reading your export. When you use the dialog, the intake first shows Opening file picker….
4. Before you confirm the destination, review the number of entities found and the export name.

Choose an eligible destination

Choose Create a new project when the migration must stand alone, or select an existing workspace to add the imported records there. An existing workspace can use Git or ordinary local files.

Create a new project

1. Select Create a new project.
2. Enter a project name.
3. Confirm the destination and complete any conflict decisions.
4. When Open project is available, select it.

DNAForge creates native sequence files, notebooks, attachments, and Registry records. The exact Files layout depends on the export and destination.

Migrate into an existing workspace

DNAForge places incoming native files in their source folders. If two incoming items need the same filename, DNAForge can add a stable source identifier to one name so that both items remain available.

Resolve exact matches and version changes

When an incoming item exactly matches a native item, choose one action:

• Link existing item keeps the native item and records the source identity.
• Import separate copy creates another native item.

When the source has versions that differ from native records, choose Keep existing versions or Use incoming versions. One version decision can apply to all records listed in that decision. Review the affected count before you continue.

DNAForge records completed decisions for the migration. Reimporting the same unchanged export into the same workspace does not create another set of copies or ask you to repeat settled decisions.

Resolve file and folder conflicts

A file can block a source folder that needs the same path. Choose the action shown by the migration:

• Rename incoming keeps the existing file and places the incoming folder at a distinct name.
• Replace existing replaces the conflicting file so the source folder can use that path.
• Cancel import leaves the conflict and imported records unchanged.

Use Replace existing only after you inspect the existing item. If the destination changes while replacement is in progress, DNAForge stops instead of overwriting the newer content.

Protect local edits

If the native file changes before you select Use incoming versions, DNAForge rejects that incoming replacement and preserves the local edit. Start a fresh migration if you still want the incoming version.

Resume after an interruption

If DNAForge or the computer stops during file installation, DNAForge uses its migration journal to finish or reconcile the interrupted work.

Watch the export tutorial

The Benchling export walkthrough starts open the first time you use the local export intake. Select Close video to hide it and save that choice.

When the video is hidden, select Watch how to export to open it again. DNAForge saves the latest open or closed state for the next time you open the intake.

Review the result

Imported with warnings means the migration completed but some source items are kept as ordinary files or could not become editable records. Review the imported, kept as files, and failed counts and every listed item. A file kept as a file is preserved for review; it is not an editable native record.