Approve and run migrations

Move cold and hot objects based on audit recommendations — always explicit, never automatic.

BlobRouter v0.1 · Last updated: August 2026 · Architecture version: 2.0

After a free audit, BlobRouter ranks recommendations (for example migrate cold objects to B2, hot objects toward R2). Nothing moves until you approve.

Prerequisites

• Completed AWS audit with recommendations
• Paid plan that includes migration
• Destination provider credentials connected (R2 and/or B2)

Flow

1. Open Audit / recommendations in the dashboard
2. Review affected size, current cost, and projected savings
3. Choose a target provider allowed for that recommendation
4. Click Approve
5. BlobRouter queues a migration job and copies objects server-side using your router credentials
6. Track status on the migration detail view

What approval means

• You explicitly authorize each recommendation
• There is no auto-remediation in v1
• You can dismiss recommendations you do not want

After migration

• Savings appear on the dashboard as objects land on cheaper providers
• For new uploads going forward, install the SDK so routing stays optimized

Troubleshooting

Symptom	Fix
Approve returns upgrade / plan limit	Migration requires a paid plan
Credentials missing	Connect the target provider under Providers
Migration stuck / error	Check destination bucket permissions; retry after fixing keys

See How it works and Architecture for the migration pipeline.