Migrating workspaces between regions

Pre-Migration Planning

Understand Region Separation

Each Recall region is a completely separate deployment with different:

Login credentials and API keys
Base URLs
Data storage (no shared state across regions)

Migration Steps

1. Request New Region Account

Contact Recall support to provision a new account in your target region. You cannot migrate an existing recall workspace, new ones must be created

2. Update API Configuration

Base URL Changes:

US (Pay-as-you-go): https://us-west-2.recall.ai
US (Monthly plan): https://us-east-1.recall.ai
EU: https://eu-central-1.recall.ai
Japan: https://ap-northeast-1.recall.ai

Generate New API Keys:
Create new API keys:

Update Webhook URLs:

Reconfigure webhook endpoints in new region dashboard
Consider adding region identifiers to webhook URLs for multi-region setups
- e.g. https://yourapp.com/webhooks/recall?region=us-east-1
Update webhook verification secrets

If using the Calendar V2 integration

Using your current region's base URL/API key:

List all of your calendars & store these refresh tokens temporarily (along with oauth client ID/secret, although you probably already have those handy)
Using the new region's base URL + your new account's API key: Create the calendars in your new region
- Recall will send you calendar.sync_events webhook events for each newly created calendar and your existing webhook logic should reschedule events for these calendars
Delete the calendars from the US region. This will automatically unschedule bots for all future events for every deleted calendar

If using the Migrate Calendar V1 integration

Migrating Calendar V1 integrations requires user action, so when moving across regions we recommend upgrading to Calendar V2 which allows migration without user involvement.

If you choose to migrate calendar V1 integrations across regions anyways, your users must re-authenticate/re-connect their calendars in the new region

Migrating Calendar V1 -> V2 integration

Fetch all your calendar V1 users
For each valid connection in each user, fetch their refresh token using this endpoint by adding a query parameter for include_refresh_token set to true. Example: https://us-east-1.recall.ai/api/v2/calendar-accounts/CALENDAR_CONNECTION_ID/access_token/?include_refresh_token=true
Create the calendar V2 calendar using the refresh token
Check that connection is successful, events are synced correctly
Disconnect the calendar V1 user

Migrate Zoom OAuth

There isn't a way to migrate Zoom OAuth integrations across regions. You can setup the Zoom OAuth integration in the new region with the existing Zoom OAuth app

Migrating Slack Huddle integration

There isn't a way to migrate Slack Huddle integration across regions

Things to consider

There are several items to be aware of when performing a migration:

Every endpoint has a rate limit associated so you should plan to batch your migration requests
Data is isolated between regions and cannot be migrated
If completely decommissioning a region, export any recording data

Testing Strategy

Run the migration on staging before applying on your production server
Test all features on staging before merging to production
- Ensure all secrets have been applied to both regions
Validate webhook delivery and processing

Common Issues and Solutions

1. API Authentication Errors

Error: Invalid API token. The API token provided might be for another Recall region
Solution: Ensure you're using the correct API key for the target region and the correct base URL

2. Webhook Verification Failures

Problem: Webhook signatures don't match after region change
Solution: Update webhook secrets and verification logic for new region

Post-Migration Cleanup

Decommission Old Region:

Cancel old region subscriptions
Remove old API keys from code