Backups and imports built for recovery, migration, and environment sync

Wodby supports on-demand backups for immediate safety and recurring schedules for ongoing coverage. That gives teams a practical way to protect data before risky changes and to keep regular recovery points available without manual intervention.

Backup creation follows the service definition instead of treating all data the same way. Each supported service exposes backup options for its own data shape, then Wodby runs the backup task and keeps the resulting archive tied to the application, instance, and service that produced it.

• Create an immediate backup before risky upgrades, migrations, or data-changing maintenance.
• Schedule recurring backups for services that need continuous recovery points.
• Restore from the backup history attached to the service that produced the archive.
• Apply shared backup presets across projects while retaining service-level overrides.

Wodby integrates with external storage providers so backup archives can live outside the runtime environment itself. This supports a cleaner disaster recovery model and gives teams more options for retention, compliance, and longer-term storage.

Wodby import workflows help teams move existing applications onto the platform or refresh lower environments with realistic data. Instead of building a one-off migration path for every project, imports become a supported operation inside the platform.

Imports can start from an uploaded archive, a remote URL, or an existing Wodby backup. Database services use database-aware import commands, while file-based services can import into volumes using the workflow defined by the service.

• Upload an archive directly when the data is available on your machine.
• Import from a remote URL when the source archive is already stored elsewhere.
• Use an existing Wodby backup as the source when cloning data between environments.

Restore a service from an existing backup after data loss or a bad change. To refresh development or staging with working data, select an existing backup or import source and apply it to the target service.

• Restore a service to a known-good state after data loss or a bad change.
• Refresh staging with newer production-like data for safer validation.
• Troubleshoot production issues in a separate environment with more confidence.

File imports also support two operating modes. A simple files import is useful for straightforward copy operations, while an init-volume import prepares data before the target service starts, giving teams a safer transactional path for services that need data in place at startup.

Environment sync becomes more practical when paired with application environments that can safely receive imported data.