What the service needs to cover
Check developer backup storage for application data, database dumps, configuration exports, build artifacts that truly need preservation, and restore tests that prove the copy is more than successful upload logs.
Developer backup storage
Keep recovery copies of application data, configuration and other irreplaceable work. Check encryption keys and restore access as part of deployment.
Hosting options
Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →02Tell us what you need to host and when it needs to be ready.
See Ask about your project →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →Your requirements
Check developer backup storage for application data, database dumps, configuration exports, build artifacts that truly need preservation, and restore tests that prove the copy is more than successful upload logs.
Record the account owner, administrator and recovery contact. Keep passwords and keys in an appropriate secret store, not in this worksheet.
For backups, define the data-loss window and retention period. Check physical and account separation from the source, then restore a sample before relying on the copy.
Keep current configuration and renewal details. Review the plan when the data, software or people responsible for the service change.
Field guide
Developer backups usually cover database dumps, application data, configuration exports, and uploaded files. Build artifacts and dependency folders rarely belong in long term storage, because they can be rebuilt from source and a lock file. Keep what cannot be regenerated, and document how the rest is rebuilt.
A green upload log proves only that bytes moved. Proof comes from loading a dump into a scratch database and running the application against the restored copy. Automate that check where you can, and keep at least one restore point from before each major release.
Take a database dump before every schema migration. A failed migration with a fresh dump is an inconvenience; without one it can be data loss.
Skip dependency folders, caches, and compiled output in backups. Smaller backups run faster and restore with fewer stale files.
Name dumps with the application version and date. Matching a data copy to a code release removes guesswork during a rollback.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.