Migration & import

Keep monitoring identities intact.

Back up the database and application key before an upgrade. Existing monitor IDs, incident history, credentials and timestamps must survive the owner-organization migration. Use a secured local copy for rehearsal.

For CSV imports, start with an exported template, validate all rows, and review interval and quota changes. Never put passwords or bearer tokens in a shared spreadsheet. Imports must not quietly duplicate monitors.

Cutover uses separate WordPress and application document roots. Keep the live environment file, prevent duplicate schedulers, verify a controlled monitor and use a compatible rollback that preserves new customer writes.