Moving Your Data Sources to the New Setup
Disclaimer: This document will be updated as new Data Sources are added to the migration plan. Always refer back here for the latest deadlines and instructions.
We’re upgrading how Data Sources are connected in Super. This migration makes syncing more reliable and prepares for future improvements.
Your existing connections will keep working during the migration window, but you’ll need to re-connect using the new setup before the deadlines listed in this document.
Why We’re Making This Change
- Future-proofing: the new setup lets us release improvements and new features faster.
- Stability: cleaner connections reduce sync issues.
- Consistency: all workspaces will use the same setup, making support easier and faster.
What This Means for You
- Your current setup keeps working
- Old connections are hidden but still active.
- Assistants and Digests continue to run on the old connection.
- No disruption during the migration window.
- Re-connecting is required
- The same Data Source option you see is actually the new setup.
- Click Connect and re-select the items you want indexed (projects, repos, folders, etc).
- After the deadline
- Old connections are removed.
- If you didn’t migrate, you’ll need to connect from scratch
Migration Timeline
We’re rolling out migrations gradually, a few Data Sources at a time. Each source will be added to this table as soon as it enters the migration plan.
You’ll be notified by email or via our Slack connect channels when a Data Source you use is scheduled, and you can always return to this document to check the latest deadlines.
How to Migrate
Go to the Data Sources page in Super.
Find the Data Source (e.g. Asana, GitHub, Linear) — it looks the same as before, but this is the new setup.
Click Connect.
Follow the on-screen instructions to authenticate.
Select the items you want to index (projects, repos, folders, etc).
The Data Source will now appear as active in your list.
Who Should Do This
- Ideally, the same person who originally set up the Data Source.
- Best if that person is an admin of the tool (Asana, GitHub, Linear, etc).
- If a different person re-connects, the scope of access may differ depending on their permissions.
FAQs
Do I need to change anything in Assistants or Digests?
- No changes needed if you re-connect the same projects/repos/folders. Assistants and Digests will keep working as before, because they reference the items you re-select.
- You will need to update them if you change the scope (e.g. connect a different project, remove a repo, or don’t re-select the same items) or miss the deadline for re-connecting on the new setup.
Do Assistants and Digests stop if I don’t migrate right away?
No. They’ll keep using the old connection until the deadline.
Why does the Data Source option look the same as before?
It’s the new setup, but shown under the same name. The old connection is hidden, not visible in your Data Sources page.
What happens to the old connection once I re-connect?
It stays active in the background until the deadline. After the deadline, it’s permanently removed.
What if the “last update” label doesn’t change after migration?
This usually means nothing new happened in your external tool (e.g. no new tasks, issues, commits). It doesn’t mean the sync failed.
Who should do the migration?
Ideally, the same person who connected originally, preferably an admin. If someone else re-connects with different permissions, the scope of data may change.
What happens if I miss the deadline?
The old connection is removed. You’ll need to connect again from scratch. You'll also have to re-add those sources to your Assistants and Digests.
What if someone else connects the Data Source before I do?
- That connection becomes the active one for your workspace.
- If they have different permissions, the scope of data may not match what you expect.
- If you’re not happy with that setup, you (or an admin) can disconnect and re-connect the Data Source again to restore the correct access.