Export & Import
ATStatus allows you to export your data for backups and import it to restore or migrate to a new installation.
Backup Your Data
Regular exports are recommended as part of your backup strategy. Export your data before making significant changes or upgrading ATStatus.
Accessing Export & Import
- Log in to the Admin Panel
- Navigate to Export in the sidebar
- Choose to export or import data
Exporting Data
Full Export
Export all your ATStatus data including:
- Status pages and settings
- Components and groups
- Incidents and maintenance windows
- Subscribers
- Users and roles
- Configuration settings
How to Export
- Go to Admin → Export
- Select what to include in the export
- Click Export Data
- Save the downloaded JSON file
Export Options
| Option | Description |
|---|---|
| Include Settings | Export all configuration settings |
| Include Incidents | Export incident history |
| Include Subscribers | Export subscriber list |
| Include Users | Export user accounts (passwords not included) |
Store Exports Securely
Export files may contain sensitive information like subscriber emails. Store them securely and don't share them publicly.
Importing Data
How to Import
- Go to Admin → Export
- Click the Import tab
- Select your export file
- Choose import options
- Click Import Data
Import Options
| Option | Description |
|---|---|
| Merge | Add imported data alongside existing data |
| Replace | Replace existing data with imported data |
| Skip Duplicates | Don't import items that already exist |
Warning: Replace Mode
Using "Replace" mode will delete existing data before importing. Always create a fresh export before using this option, in case you need to restore.
Migrating to a New Server
To migrate ATStatus to a new server:
- Export all data from your current installation
- Install ATStatus on the new server
- Run the setup process on the new server
- Import your exported data
- Update DNS or proxy settings to point to the new server
Export File Format
Exports are saved as JSON files. The file structure follows ATStatus's internal data model and is not intended for manual editing.
{
"version": "1.0",
"exportedAt": "2024-01-15T10:30:00Z",
"data": {
"statusPages": [...],
"components": [...],
"incidents": [...],
"settings": {...}
}
}Troubleshooting
Import Fails
- Ensure the file is a valid ATStatus export (not corrupted)
- Check that the export version is compatible
- Try importing smaller subsets of data
Missing Data After Import
- Verify all options were selected during import
- Check for import errors in the log
- Ensure the export file contained the expected data
Export Best Practices
- Create regular backups (weekly or before major changes)
- Test imports on a staging environment first
- Keep multiple backup versions
- Store backups in a secure, off-site location
- Document your backup schedule
