Skip to main content
The importer reads your page through the Statuspage API and copies it into an existing Observer status page. You review everything before anything is written, and nothing is published or sent while it runs.
The importer is being rolled out. Until it is enabled for your organization, Import does not appear under Pages.
The importer is available on every plan, Free included. Imported metrics and subscribers count toward your plan’s limits, and the review step tells you when an import would not fit. For the wider migration (choosing measured signals, cutting over DNS), see Migrate from Statuspage.

​
Before you start

  • Create the Observer status page that should receive the import. The importer does not create pages.
  • In Statuspage, open your avatar menu, then API info. Copy an API key and the Page ID of the page you are moving.

​
Run the import

1

Connect Statuspage

In the console, open Pages and select Import. Paste the API key and the page ID, then select Preview import. Observer reads the page but writes nothing yet.
2

Review the import

The review shows how many components, incidents, maintenances and active email subscribers Observer found, and what was imported before if you have run the import already. Then choose:
  • Incidents and maintenances: turn Import incident and maintenance history on or off.
  • Destination: the Observer page that receives the components and history.
  • Subscribers: optional. See Subscribers.
3

Import

Select Import into your page. When it finishes, the summary lists what was created.Lists of more than 500 subscribers continue in the background. See Large subscriber lists.
4

Send the confirmation email

If you imported subscribers with Ask subscribers to confirm again on, the last step shows Send N confirmation emails. Set your page’s name and logo first: the email uses them. See Confirmation email.

​
What is imported

Imported incidents and maintenances carry an Imported tag in the updates list. Imported components start with no data. Observer writes no status for them, so the import causes no status change on the page. Set each one’s status afterwards, or replace it with a measured metric. Nothing is notified: imported incidents and maintenances send no emails, webhooks or alerts, and past maintenances never trigger reminders. Large accounts have limits. An import with more than 1,000 components or 50,000 subscribers stops with an error. Past 5,000 incidents, only the newest 5,000 are imported, and the review says so.

​
Subscribers

Email subscribers move only if you confirm that these subscribers agreed to receive status notifications from you. Without that confirmation, no subscriber is imported. SMS, webhook and Slack subscribers are not imported.
  • Quarantined subscribers are skipped.
  • Addresses already on the page are never added again, including addresses that unsubscribed.
  • Ask subscribers to confirm again is on by default. Imported subscribers are then added as pending and receive no updates until they confirm through the confirmation email. Turn it off to add them as confirmed, so they receive your next update.
The import itself sends no email to subscribers. The only email they get is the confirmation email, and only when you send it.

​
Confirmation email

When the import finishes, select Send N confirmation emails in the last step. Each pending subscriber gets one email asking them to confirm their subscription, with a link that is valid for 30 days.
  • It is sent once. There are no reminders, and selecting the button again sends nothing to subscribers who already got the email.
  • Emails go out gradually alongside your other subscriber emails, at most 60 a minute.
  • A subscriber who confirms becomes a regular confirmed subscriber.
  • Pending subscribers who have not confirmed 30 days after the email are removed. If you never send the email, they are removed 30 days after the import. A removed subscriber is not added again by a later run of the import.

​
Large subscriber lists

Imports with more than 500 subscribers run in the background, with progress shown as Read from Statuspage and Imported.
  1. Observer first reads the subscriber list from Statuspage. Keep the tab open while it reads (about one second per 100 subscribers). If the page reloads, paste the API key again to continue from where it stopped, or cancel the import.
  2. Observer then adds the subscribers in batches of 500. You can leave the page. If anything restarts, the import picks up where it stopped and never adds anyone twice.
Plan limits are checked for each batch. If a batch would go over your plan’s subscriber limit, the import stops there and keeps the subscribers already added.

​
Your API key

The Statuspage API key is never stored. It is used for this import only and sent only to the Statuspage API. It is never written to Observer’s database, logs or audit log, including for background imports, and the form clears it when the import ends. Paste it again to run another import or to continue reading a large subscriber list. The importer reads the Statuspage API at about one request per second and waits when Statuspage asks it to slow down, so a page with many subscribers takes a few minutes.

​
Run it again

Re-running the import is safe. Observer remembers what each Statuspage object became, so a second run updates those items instead of creating duplicates:
  • New components, incidents and maintenances are added.
  • Components keep their Statuspage names. A rename made in Observer is overwritten on the next run.
  • An incident resolved in Observer is never reopened, and nothing that is published is unpublished.
  • An imported incident or maintenance you deleted in Observer is not brought back. A component metric you deleted is created again.
  • Deleted subscribers are never re-added.