How it works
Barehaul is in development. This is the migration flow we’re building.
What moves
Your app, its PostgreSQL databases and its S3 storage. Each is checked before cutover.
App
On AWS: Your app on AWS
Check: Planned: what moves and what needs manual work
Moves to: Your Kubernetes or VMs
PostgreSQL
On AWS: RDS PostgreSQL
Check: Row counts and checksums on both sides
Moves to: PostgreSQL on your servers
Object storage
On AWS: S3 buckets
Check: Compared on both sides
Moves to: Object storage on your servers
Cutover waits for you. Nothing is final until you approve it, and rollback is complete until then.
Plan the move
Review the AWS resources in scope, the proposed destinations and the steps that require manual work. Approve the plan before the transfer begins.
Gate: You approve the plan.
Verify the destination
Compare the source and destination and review the evidence for your database and object storage. Resolve mismatches before approving cutover.
Gate: Mismatches are resolved before cutover.
Approve cutover
Switch workloads after reviewing the checks. The planned workflow supports rollback until cutover. After cutover, returning to the source requires a separately configured fallback window.
Gate: You approve the switch.
Choose where the transfer runs
With the worker on your servers, your data never leaves your network. With hosted transfer, we move it, we never keep it.
Worker on your servers
With the worker on your servers, your data never leaves your network.
Hosted transfer
With hosted transfer, we move it, we never keep it.