Skip to main content
When a newer Digital Brain template is released, you do not need to manually re-enter notes or start from scratch. Using Tana’s native Merge feature, you can safely migrate all supertags, fields, and existing content into the new architecture. This guide walks you through the step-by-step migration process with zero data loss.

​
Preparation Before Upgrading

1

Install New Template into Workspace

Open the latest template link and install it directly into the same workspace containing your current notes.
2

Open Split Screen Views

Open the new template in the left pane and your old template in the right pane to easily inspect, compare, and move notes.
3

Temporarily Rename Old Nodes

Append - Old to legacy nodes and supertags (e.g., Channel - Old, Company - Old) to avoid selecting the wrong version during merge operations.

​
Merging Data into New Version

1

Merge Identical Fields First

Always merge Fields before merging Supertags to prevent duplicated field definitions:
  • Click on the legacy field in the old version (e.g., Channel Type, URL Link).
  • Press Ctrl + K (Cmd + K on macOS).
  • Type Merge node with… and select the corresponding field in the new version.
  • Confirm the merge. All field values automatically consolidate into the new field.
2

Merge Corresponding Supertags

Perform the merge operation for your core Supertags:
  • Open the legacy supertag configuration (e.g., #channel, #company, #contact).
  • Press Ctrl + K (Cmd + K on macOS) ➔ select Merge node with….
  • Select the new template’s supertag to unify both schemas.
  • All existing nodes tagged with the old supertag automatically inherit the new definition without losing data.
3

Inspect and Remove Duplicate Fields

After merging tags, open the newly merged supertag configuration:
  • If duplicate field lines appear from legacy overlapping schemas, delete the redundant fields.
  • Inspect child nodes to verify data alignment across live views.
4

Move Remaining Data and Archive Old Template

  • Move any custom project blocks or specific references to their designated locations on the new dashboard.
  • Once migration is verified, move the old template into Archive or delete it to keep your workspace clean.

​
Important Migration Guidelines

Fields Before Tags

Merging fields prior to tags prevents duplicate field rows from appearing inside supertag schemas.

Verify Target Versions

Double-check that the new version’s node is always selected as the merge destination when running the Merge node with… command.

Do Not Delete Early

Only archive or delete legacy templates after confirming all live search views on the new dashboard populate correctly.