Appwrite Project Migrate
A cautious CLI for selectively copying Appwrite resources with dry-run and recovery behavior.
Read the build from several angles.
Authentic screens, terminal output, and architecture plates are kept together so the page shows the shape of the work without inflating the claim.
This record uses a procedural architecture view because no authentic public screenshot has been approved.
CLOUD
What exists.
A direct Appwrite project copier that inventories, plans, clears, copies, resumes, and verifies users, teams, databases, storage, functions, and sites between Appwrite projects.
Where it resisted.
Appwrite's native migration service doesn't cover all resource groups. A manual copier needs to handle partial failures, resume from checkpoints, and verify integrity.
What I changed.
Built a Bun CLI with dry-run planning, checkpoint-based resume, per-resource-group verification, and clear credential handling.
The obvious implementation was not the product.
Use checkpoints and verification rather than trusting a single pass to complete cleanly.
Current proof
03- Supports users, teams, databases, storage, functions, and sites.
- Dry-run, checkpoint, resume, and verify modes.
- Credentials never written into checkpoints or reports.
What this build changed.
Data migration tools earn trust through verifiable behavior, not through speed.
The implementation surface.
Proof should be inspectable.
A public repository or live build is not linked yet. The status above states exactly what has been verified.