Why Migrate?
- New infrastructure, more modern and more secure
- Upstash Global is SOC-2 (included with Prod pack) and HIPAA (included with Enterprise) compatible
- Enhanced feature set: New features are only made available on Upstash Global
- Ability to add/remove read regions on the go
- Better performance as per our benchmarks
Prerequisites
Before starting the migration, make sure you have:- An existing regional Upstash Redis database (source)
- A new global Upstash Redis database (destination)
- Access to both databases’ credentials (connection strings, passwords)
Migration Process
There are several official ways to migrate your data:1. Using Backup/Restore (Recommended for AWS Regional Databases)
If your regional database is hosted in AWS, you can use Upstash’s backup/restore feature:-
Create a backup of your regional database:
- Go to your regional database details page
- Navigate to the
Backupstab - Click the
Backupbutton - Provide a unique name for your backup
- Wait for the backup process to complete
During backup creation, some database operations will be temporarily unavailable. -
Restore the backup to your global database:
- Go to your global database details page
- Navigate to the
Backupstab - Click
Restore... - Select your regional database as the source
- Select the backup you created
- Click
Start Restore
2. Using Upstash Console Migration Wizard
The easiest way to migrate your data is using the Upstash Console’s built-in migration wizard:- Go to Upstash Console
- In the database list page, click the
Importbutton - Select your source (regional) database
- Select your destination (global) database
- Follow the wizard instructions to complete the migration
Note: The destination database will be flushed before migration starts.
3. Using upstash-redis-dump
Another reliable method is using the official upstash-redis-dump tool:-
Install upstash-redis-dump:
-
Export data from regional database:
-
Import data to global database:
Verification
After migration, verify your data:- Compare key counts in both databases
- Sample test some keys to ensure data integrity
Post-Migration Steps
- Update your application configuration to use the new Global database URL
- Test your application thoroughly with the new database
- Monitor performance and consistency across regions
- Keep the regional database as backup for a few days
- Once verified, you can safely delete the regional database