Migrating Tellspin to a New Slack Workspace
Overview
Tellspin schedules, user groups, and your subscription all belong to a specific Slack workspace. When your company moves to a new workspace (or merges into an Enterprise Grid), the schedules have to be recreated there and the subscription moved across. There is no self-service export/import yet, so plan for a short manual step with help from Tellspin support.
What Can and Can't Be Moved
| Item | How it moves |
|---|---|
| Schedules (participants, rotation, timezone, customization) | Recreated by you in the new workspace, using a configuration summary from support |
| Slack user groups / handles | Recreated in the new workspace when you create each schedule (Slack user groups don't transfer between workspaces) |
| Reminders and overrides | Recreated by you |
| PagerDuty / OpsGenie / Datadog links | Reconnected in the new workspace |
| Subscription and remaining credit | Transferred by support |
Step 1: Contact Support Early
As soon as you know the migration date, email support@tellspin.com with:
- the name and workspace ID of the old workspace,
- the name and workspace ID of the new workspace,
- the approximate migration date,
- a request for an export of your current schedule configurations.
Support replies with a list of your schedules: handles, participants, rotation frequency, timezone, customization options, and reminders.
Step 2: Recreate the Schedules in the New Workspace
- Install Tellspin in the new workspace from the Slack App Directory.
- Make sure the person doing the setup can create user groups there (see who can edit Tellspin schedules); Slack's user group permissions are set per workspace.
- Working from the export, create each schedule in the Tellspin App Home. Set the timezone and Customization (optional) options to match, then add reminders.
- Reconnect PagerDuty, OpsGenie, or Datadog and re-link any synced schedules. See Integrations, connecting Tellspin to PagerDuty, and connecting Tellspin to Datadog.
- Recreate any Schedule Triage handles after their source schedules exist.
Step 3: Transfer the Subscription
When the new workspace is ready, tell support. They cancel the old workspace's subscription and move the plan and any remaining credit to the new one, so you aren't billed twice.
Step 4: Tidy Up the Old Workspace
Once everyone has switched, delete or pause the old schedules so their reminders stop, and update any runbooks that reference the old handles.