Open-source status page, incident response and uptime monitoring
TypeScript alertingincident-managementmcpmcp-servermonitoringmonitoring-as-codeobservabilityon-callopen-sourcesrestatus-pagestatuspagesynthetic-monitoringterraformtinybirdtursouptimeuptime-checkeruptime-monitor
chore: status-page importer content (#2022)
Maximilian Kaskef517071b8bef
diff --git a/apps/docs/astro.config.mjs b/apps/docs/astro.config.mjsindex 3fd809c52..49241a21b 100644--- a/apps/docs/astro.config.mjs+++ b/apps/docs/astro.config.mjs@@ -119,6 +119,10 @@ export default defineConfig({label: "Manage Your Stack with Terraform and CLI",slug: "tutorial/how-to-manage-openstatus-with-terraform-cli",},+ {+ label: "Import a Status Page from Another Provider",+ slug: "tutorial/how-to-import-status-page",+ },],},diff --git a/apps/docs/src/content/docs/tutorial/how-to-import-status-page.mdx b/apps/docs/src/content/docs/tutorial/how-to-import-status-page.mdxnew file mode 100644index 000000000..bf868f350--- /dev/null+++ b/apps/docs/src/content/docs/tutorial/how-to-import-status-page.mdx@@ -0,0 +1,153 @@+---+title: Import a Status Page from Another Provider+description: "Import your existing status page setup from Atlassian Statuspage, Better Stack, or Instatus into openstatus"+---++import { Aside } from '@astrojs/starlight/components';++## What you'll learn++| | |+|---|---|+| **Time** | ~2 minutes |+| **Level** | Beginner |+| **Prerequisites** | openstatus account |++Migrating away from your current status page provider does not have to mean starting from scratch. Openstatus can import your existing status page configuration -- including components, incidents, maintenances, and subscribers -- directly from another provider. This tutorial walks through the provider-agnostic import flow step by step.++## Supported providers++Openstatus currently supports importing from three providers:++- **[Atlassian Statuspage](https://openstatus.dev/guides/migrate-from-atlassian-statuspage)** -- The most widely used hosted status page solution.+- **[Better Stack](https://openstatus.dev/guides/migrate-from-betterstack)** -- Monitoring and status page platform (formerly Better Uptime).+- **[Instatus](https://openstatus.dev/guides/migrate-from-instatus)** -- A modern status page service with component-level tracking.++Each link above points to a provider-specific migration guide with detailed instructions on API key generation and data mapping.++## Step-by-step import++### 1. Get your API key++You need a read-access API key from your current provider. The key is used only during the import and is not stored after the process completes.++<Aside>+Where to find your API key varies by provider. See the provider-specific guides linked above for exact instructions:+- **Statuspage:** Organization-level API key in your Atlassian account settings.+- **Better Stack:** API token from the Better Stack dashboard under Integrations.+- **Instatus:** API key from your Instatus workspace settings.+</Aside>++### 2. Open the import page++In the openstatus dashboard, navigate to **Status Pages** and select the status page you want to import into. If you have not yet created a status page, create one first -- see [Create a Status Page](/tutorial/how-to-create-status-page) for instructions.++Open the **Components** tab and scroll down to the **Import** section at the bottom of the page.++### 3. Select your provider and enter credentials++Choose your source provider from the dropdown and paste your API key. Depending on the provider, you may also need to supply additional identifiers (for example, a Page ID for Atlassian Statuspage).+++### 4. Preview the import++After submitting your credentials, the importer fetches your existing data and displays a preview summary. No data is written at this stage -- the preview is read-only.++The preview includes:++- **Resource counts** -- Number of components, component groups, incidents, maintenances, and subscribers that will be imported.+- **Warnings** -- Any resources that cannot be imported or require manual attention (for example, unsupported subscriber types or resources that exceed your plan limits).+- **Mapping details** -- How source resources map to openstatus equivalents.++Review the summary carefully before proceeding. If the counts do not match what you expect, verify that your API key has sufficient permissions to read all resources.+++### 5. Configure import options++Use the toggles to enable or disable import of each resource type. For example, you may want to import only components and skip historical incidents. Available toggles depend on what the selected provider supports.++<Aside type="caution">+Importing incidents and maintenances creates historical records in openstatus. These are imported as-is and cannot be bulk-deleted after import.+</Aside>++### 6. Run the import++Click **Import** to start the process. The import runs in phases:++1. **Components and groups** -- Structural elements are created first so that incidents and maintenances can reference them.+2. **Incidents** -- Historical and active incidents, including updates and component impact.+3. **Maintenances** -- Scheduled and completed maintenance windows.+4. **Subscribers** -- Email subscribers (where supported by the source provider).+5. **Monitors** -- Existing monitoring checks (Better Stack only).++A progress indicator shows the current phase and any errors encountered. When the import finishes, you are redirected to your status page configuration with all imported data in place.+++## What gets imported++Not every provider exposes the same data. The table below summarizes what openstatus imports from each source:++| Resource | Statuspage | Better Stack | Instatus |+|---|---|---|---|+| Status page | Yes | Yes | Yes |+| Components and groups | Yes | Yes | Yes |+| Incidents | Yes | Yes | Yes |+| Maintenances | Yes | Yes | Yes |+| Subscribers | Yes (email only) | No | Yes (email only) |+| Monitors | No | Yes | No |++<Aside type="tip">+For a detailed breakdown of how each resource type is mapped, see the provider-specific migration guides:+[Atlassian Statuspage](https://openstatus.dev/guides/migrate-from-atlassian-statuspage),+[Better Stack](https://openstatus.dev/guides/migrate-from-betterstack),+[Instatus](https://openstatus.dev/guides/migrate-from-instatus).+</Aside>++## After import++The import creates resources in openstatus but does not automatically make your status page live or redirect traffic. Complete the following steps to finalize your migration:++1. **Verify imported data.** Open your status page and confirm that components, incidents, and maintenances appear correctly. Check that component groups are structured as expected.++2. **Connect monitors to static components.** Imported components may not have monitors attached. Navigate to each component and link an existing openstatus monitor, or [create a new monitor](/tutorial/how-to-create-monitor) for it.++3. **Update DNS for your custom domain.** If you are migrating a custom domain (e.g., `status.yourdomain.com`), update your CNAME record to point to `status.openstatus.dev`. See the [Status Page Reference](/reference/status-page) for DNS configuration details.++4. **Invite subscribers.** If your provider does not support subscriber export (Better Stack) or you need to re-verify email subscribers, use the openstatus subscription system to notify your users of the new page.++## Troubleshooting++### Invalid API key++The import fails immediately with an authentication error. Double-check that you copied the full key and that it has read permissions. Some providers require organization-level keys rather than personal tokens. Regenerate the key if necessary.++### Plan limits exceeded++Openstatus plans have caps on the number of components and monitors. If your import would exceed these limits, the preview step displays a warning before any data is written. You can either upgrade your plan or disable import of certain resource types to stay within limits.++### Partial import++If the import succeeds for some phases but fails for others (for example, components import successfully but incidents fail due to a rate limit or timeout), the successfully imported resources remain in place. Fix the underlying issue and re-run the import. Only the failed phases will be retried; already-imported resources are not duplicated.++<Aside type="caution">+If a partial import leaves your status page in an inconsistent state, you can delete the imported resources manually and start the import again from scratch.+</Aside>++### Duplicate incidents on re-import++Running the import a second time does not deduplicate incidents or maintenances. If you need to re-import, delete the previously imported records first to avoid duplicate entries appearing on your status page.++## What's next?++Now that your data is in openstatus, explore these resources to get the most out of your new setup:++- **[Configure Your Status Page](/tutorial/how-to-configure-status-page)** -- Customize the appearance, add a logo, and configure notification preferences.+- **[Create Your First Monitor](/tutorial/how-to-create-monitor)** -- Set up synthetic monitoring for your imported components.+- **[Status Page Reference](/reference/status-page)** -- Full reference for all status page configuration options.+- **[Building Trust with Status Pages](/concept/best-practices-status-page)** -- Best practices for transparent incident communication.++### Provider-specific guides++- [Migrate from Atlassian Statuspage](https://openstatus.dev/guides/migrate-from-atlassian-statuspage)+- [Migrate from Better Stack](https://openstatus.dev/guides/migrate-from-betterstack)+- [Migrate from Instatus](https://openstatus.dev/guides/migrate-from-instatus)diff --git a/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/atlassian-statuspage-api-key.png b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/atlassian-statuspage-api-key.pngnew file mode 100644index 000000000..5b71d7efbBinary files /dev/null and b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/atlassian-statuspage-api-key.png differdiff --git a/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/atlassian-statuspage.png b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/atlassian-statuspage.pngnew file mode 100644index 000000000..96104d214Binary files /dev/null and b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/atlassian-statuspage.png differdiff --git a/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/betterstack-api-key.png b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/betterstack-api-key.pngnew file mode 100644index 000000000..8551e0782Binary files /dev/null and b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/betterstack-api-key.png differdiff --git a/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/betterstack.png b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/betterstack.pngnew file mode 100644index 000000000..2a450d6b0Binary files /dev/null and b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/betterstack.png differdiff --git a/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/import-from-statuspage-betterstack-instatus.png b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/import-from-statuspage-betterstack-instatus.pngnew file mode 100644index 000000000..93311ecc7Binary files /dev/null and b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/import-from-statuspage-betterstack-instatus.png differdiff --git a/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/importers.png b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/importers.pngnew file mode 100644index 000000000..fee5e0507Binary files /dev/null and b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/importers.png differdiff --git a/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/instatus-api-key.png b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/instatus-api-key.pngnew file mode 100644index 000000000..12e2fdff6Binary files /dev/null and b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/instatus-api-key.png differdiff --git a/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/instatus.png b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/instatus.pngnew file mode 100644index 000000000..d8e837c7aBinary files /dev/null and b/apps/web/public/assets/posts/import-from-statuspage-betterstack-instatus/instatus.png differdiff --git a/apps/web/src/content/pages/blog/import-from-statuspage-betterstack-instatus.mdx b/apps/web/src/content/pages/blog/import-from-statuspage-betterstack-instatus.mdxnew file mode 100644index 000000000..252e3c91c--- /dev/null+++ b/apps/web/src/content/pages/blog/import-from-statuspage-betterstack-instatus.mdx@@ -0,0 +1,81 @@+---+title: "Migrate to openstatus from Atlassian Statuspage, Better Stack, or Instatus in Minutes"+description: "Import your entire status page setup — components, incidents, maintenances, subscribers, and monitors — from Atlassian Statuspage, Better Stack, or Instatus with our new one-click importer."+author: "Maximilian Kaske"+publishedAt: "2026-03-27"+image: "/assets/posts/import-from-statuspage-betterstack-instatus/import-from-statuspage-betterstack-instatus.png"+category: "company"+---++Switching status page providers is the kind of task that sits on your backlog for months. You know you want to move, but the thought of recreating every component, re-entering every incident, and re-inviting every subscriber keeps you from pulling the trigger.++We built importers so you don't have to.++Today we're shipping one-click importers for three platforms: **Atlassian Statuspage**, **Better Stack**, and **Instatus**. Each one brings over your full status page setup in minutes, not days.++Shoutout to [aggmoulik](https://github.com/aggmoulik) for his relentless support on features like these lately.++## Three Steps. That's It.++The import flow is the same regardless of which provider you're migrating from.++**Step 1: Select your provider and authenticate.** Paste your API key and pick the status page you want to import.++**Step 2: Preview what will be imported.** We show you everything we found -- components, incidents, maintenances, subscribers, monitors -- before anything touches your account. Review it, adjust if needed.++**Step 3: Import.** Hit the button. We create your status page, map your components into groups, pull in your full incident and maintenance history, and subscribe your existing subscribers. Done.++<Image src="/assets/posts/import-from-statuspage-betterstack-instatus/importers.png" alt="Import tool showing provider selection for Atlassian Statuspage, Better Stack, and Instatus" />++## What Gets Imported++Not every provider exposes the same data through their API. Here is exactly what we can bring over from each one:++| | Statuspage | Better Stack | Instatus |+|---|---|---|---|+| Status page | Yes | Yes | Yes |+| Components & groups | Yes | Yes | Yes |+| Incidents | Yes | Yes | Yes |+| Maintenances | Yes | Yes | Yes |+| Subscribers | Yes (email only) | No (API limitation) | Yes (email only) |+| Monitors | No | Yes | No |++We are transparent about what we can and cannot import. If a provider's API does not expose certain data, we will not pretend otherwise.++## Atlassian Statuspage++Statuspage gives us the richest incident data of the three. We import your complete incident history including every update, with timestamps and status transitions preserved. Component groups come through cleanly, and we map Statuspage's operational states directly to openstatus equivalents. If you have email subscribers, those come along too.++For the full walkthrough, check out our [Statuspage migration guide](/guides/migrate-from-atlassian-statuspage).++## Better Stack++Better Stack is the only provider where we can import monitors alongside your status page. That means your check URLs, regions, and check frequency all carry over. You get a working monitoring setup on openstatus without reconfiguring a single endpoint. The trade-off: Better Stack's API does not expose subscriber data, so you will need to re-invite those separately.++For the full walkthrough, check out our [Better Stack migration guide](/guides/migrate-from-betterstack).++## Instatus++Instatus has the most straightforward status model of the three, which works in our favor. Their component statuses map 1:1 to ours, and we auto-detect component groups from their nested structure. Email subscribers are imported. If you are on Instatus today, the migration is about as seamless as it gets.++For the full walkthrough, check out our [Instatus migration guide](/guides/migrate-from-instatus).++## Built on a Shared Foundation++Under the hood, all three importers use the same architecture: a provider-specific adapter that normalizes data into a common schema, followed by a shared import pipeline that creates everything in the right order with proper relationships. This means the import behavior is consistent and predictable regardless of where you are coming from.++We plan to add more providers over time. If your current tool is not on the list yet, [let us know](https://github.com/openstatusHQ/openstatus/issues).++## Get Started++In your openstatus dashboard, go to **Status Pages**, select a status page (or create one first), open the **Components** tab, and scroll down to the **Import** section. Pick a provider. The whole process takes less than five minutes.++If you want more detail on the API setup or what each field maps to, we have a step-by-step tutorial in our docs: [How to Import a Status Page](https://docs.openstatus.dev/tutorial/how-to-import-status-page).++Migration guides:++- [Migrate from Atlassian Statuspage](/guides/migrate-from-atlassian-statuspage)+- [Migrate from Better Stack](/guides/migrate-from-betterstack)+- [Migrate from Instatus](/guides/migrate-from-instatus)++No more excuses to stay on a platform that does not fit. Your status page, your data, moved in minutes.diff --git a/apps/web/src/content/pages/guides/migrate-from-atlassian-statuspage.mdx b/apps/web/src/content/pages/guides/migrate-from-atlassian-statuspage.mdxnew file mode 100644index 000000000..74afd7746--- /dev/null+++ b/apps/web/src/content/pages/guides/migrate-from-atlassian-statuspage.mdx@@ -0,0 +1,139 @@+---+title: "How to Migrate from Atlassian Statuspage to openstatus"+description: "Step-by-step guide to import your Atlassian Statuspage components, incidents, maintenances, and subscribers into openstatus."+author: "openstatus"+publishedAt: "2026-03-27"+category: "alternative"+faq:+ - question: "How long does it take to migrate from Statuspage to openstatus?"+ answer: "The import itself takes under 2 minutes. You'll need your Statuspage API key and optionally your Page ID if you have multiple pages."+ - question: "Will I lose any data when migrating from Statuspage?"+ answer: "No. Openstatus imports your components, component groups, incidents (with all updates), maintenances, and email subscribers. SMS and Slack subscribers are not supported — you'll see a warning during preview."+ - question: "Can I preview the import before committing?"+ answer: "Yes. The importer shows a full preview of what will be imported — including counts per resource type and any warnings — before you confirm."+ - question: "Does openstatus import my Statuspage monitors?"+ answer: "Atlassian Statuspage doesn't expose monitor configurations via their API, so components are imported as static components. You can connect openstatus monitors to them after import."+ - question: "Can I run the import multiple times?"+ answer: "Components, component groups, and subscribers are deduplicated by name — the importer skips existing resources. However, incidents and maintenances are always created as new entries, so re-running the import will produce duplicates for those."+howto:+ totalTime: "PT2M"+ steps:+ - name: "Get your Statuspage API key"+ text: "Go to your Atlassian Statuspage account → Manage Account → API. Copy your API key."+ - name: "Preview the import"+ text: "In your openstatus dashboard, go to Status Pages, select a status page, open the Components tab, and scroll down to the Import section. Select Atlassian Statuspage, paste your API key, and click Preview."+ - name: "Run the import"+ text: "Review the preview summary. Toggle which resources to import (components, incidents, maintenances, subscribers). Click Import to start."+---++Atlassian Statuspage has been a reliable choice for communicating service status for years. But as teams grow, the pricing gets steep, monitoring remains a separate concern, and customization options stay limited. Openstatus offers a modern, open-source alternative with built-in synthetic monitoring, unlimited team members, and a one-click importer that brings your existing data along.++This guide walks through migrating your Statuspage account to openstatus, including what gets imported, what does not, and what to do after the migration is complete.++For background on why we built the importer, see the [announcement blog post](/blog/import-from-statuspage-betterstack-instatus).++## What Gets Imported++Openstatus reads from the [Statuspage REST API](https://developer.statuspage.io/) and maps your data as follows.++### Field Mapping++| Statuspage Resource | Statuspage Field | openstatus Resource | openstatus Field | Notes |+| --- | --- | --- | --- | --- |+| **Page** | `name` | Status Page | `title` | |+| Page | `page_description` | Status Page | `description` | |+| Page | `subdomain` | Status Page | `slug` | |+| Page | `domain` | Status Page | `customDomain` | |+| **Component** | `name` | Component | `name` | Imported as `static` type |+| Component | `description` | Component | `description` | |+| Component | `position` | Component | `order` | |+| **Component Group** | `name` | Component Group | `name` | Child components linked automatically |+| **Incident** | `name` | Status Report | `title` | |+| Incident | `incident_updates` | Status Report Updates | `message`, `status`, `date` | All updates preserved in chronological order |+| Incident | `postmortem_body` | Status Report Update | Appended to last update | Appended with a separator and "Postmortem" heading |+| Incident | `components` | Status Report | Component links | Linked by matching source component IDs |+| **Scheduled Incident** | `name` | Maintenance | `title` | Incidents with `scheduled_for` become maintenances |+| Scheduled Incident | `scheduled_for` | Maintenance | `from` | |+| Scheduled Incident | `scheduled_until` | Maintenance | `to` | Falls back to `scheduled_for` if absent |+| Scheduled Incident | `incident_updates` | Maintenance | `message` | All update bodies concatenated |+| **Subscriber** | `email` | Subscriber | `email` | Only `email` mode subscribers are imported |+| Subscriber | `components` | Subscriber | Component scope | Per-component subscriptions preserved |++### Incident Status Mapping++| Statuspage Status | openstatus Status |+| --- | --- |+| `investigating` | `investigating` |+| `identified` | `identified` |+| `monitoring` | `monitoring` |+| `resolved` | `resolved` |+| `scheduled` | `investigating` |+| `in_progress` | `investigating` |+| `verifying` | `monitoring` |+| `completed` | `resolved` |++### Caveats++- **Components are imported as "static" type.** Statuspage does not expose monitor configurations via its API. After import, you can connect an openstatus monitor to any component.+- **Component groups are preserved.** Groups and their child component relationships are maintained during import.+- **Incidents include all updates.** Every `incident_update` is imported chronologically. If a postmortem body exists, it is appended to the last update with a Markdown separator.+- **Scheduled incidents become maintenances.** Any incident with a `scheduled_for` timestamp is imported as a maintenance rather than a status report.+- **Only email subscribers are imported.** SMS, Slack, and webhook subscribers are skipped. The importer displays a warning with the count of skipped subscribers during preview.+- **Monitors are not imported.** The Statuspage API does not expose monitor configurations.+- **Multi-page accounts require a Page ID.** If your Statuspage account has multiple pages, provide the Page ID to target a specific page. You can find it in the Statuspage URL or via the API.++## Step-by-Step Walkthrough++### 1. Get Your Statuspage API Key++Log in to your Atlassian Statuspage account. Navigate to **Manage Account** and then **API**. Copy your API key.++If your account has multiple pages, also note the **Page ID** for the page you want to import. You can find it in the URL when viewing the page in the Statuspage dashboard (e.g., `manage.statuspage.io/pages/<page_id>`).++<Image src="/assets/posts/import-from-statuspage-betterstack-instatus/atlassian-statuspage-api-key.png" alt="Atlassian Statuspage API settings page showing organization API keys and Page IDs" />++### 2. Open the Import Tool++In your openstatus dashboard, navigate to **Status Pages** and select the target status page (or create one first). Open the **Components** tab and scroll down to the **Import** section.++Select **Atlassian Statuspage** as the provider. Paste your API key. If applicable, enter your Page ID.++Click **Preview**. The importer fetches your data from the Statuspage API and displays a summary:++- Number of components and component groups+- Number of incidents and maintenances+- Number of email subscribers+- Warnings for any skipped resources (e.g., SMS or Slack subscribers)++Review the summary before proceeding. Toggle which resource types you want to import: components, incidents, maintenances, and subscribers. Click **Import** to start.++<Image src="/assets/posts/import-from-statuspage-betterstack-instatus/atlassian-statuspage.png" alt="openstatus import form for Atlassian Statuspage with preview summary and import toggles" />++## After the Import++Once your data is in openstatus, there are a few steps to finish the migration.++### Connect Monitors to Components++Imported components have no monitor attached because Statuspage does not expose monitor configurations. For each component that should reflect live uptime data:++1. Create an openstatus monitor (HTTP, TCP, or other supported check type).+2. Link the monitor to the component in the component settings.++### Verify Subscriber Data++Imported email subscribers are marked as confirmed. Verify that your subscriber list is complete by comparing counts between Statuspage and openstatus.++### Update DNS for Your Custom Domain++If you use a custom domain for your status page, update your DNS records to point to openstatus instead of Statuspage. Refer to the [openstatus documentation on custom domains](https://docs.openstatus.dev) for the required DNS configuration.++### Decommission Statuspage++After verifying that everything is working correctly on openstatus, you can cancel your Atlassian Statuspage subscription. Consider keeping the old page in read-only mode for a transition period so that any bookmarked URLs still resolve.++## Further Reading++- [Blog: Import from Statuspage, Betterstack, and Instatus](/blog/import-from-statuspage-betterstack-instatus)+- [Docs: How to Import a Status Page](https://docs.openstatus.dev/tutorial/how-to-import-status-page)+- [Top Five Atlassian Statuspage Alternatives](/guides/top-five-atlassian-statuspage-alternatives)diff --git a/apps/web/src/content/pages/guides/migrate-from-betterstack.mdx b/apps/web/src/content/pages/guides/migrate-from-betterstack.mdxnew file mode 100644index 000000000..d1e0cd39e--- /dev/null+++ b/apps/web/src/content/pages/guides/migrate-from-betterstack.mdx@@ -0,0 +1,168 @@+---+title: "How to Migrate from Better Stack to openstatus"+description: "Step-by-step guide to import your Better Stack monitors, status page, components, incidents, and maintenances into openstatus."+author: "openstatus"+publishedAt: "2026-03-27"+category: "alternative"+faq:+ - question: "Can I import my Better Stack monitors into openstatus?"+ answer: "Yes. openstatus is the only provider that imports monitors from Better Stack — including URL, check frequency, HTTP method, headers, and regions."+ - question: "Does openstatus import Better Stack subscribers?"+ answer: "No. Better Stack doesn't expose subscribers via their API, so subscriber import is not available. You'll need to re-invite subscribers manually."+ - question: "What if I don't have a Better Stack status page?"+ answer: "You can still import. Without a status page ID, the importer will import your monitors, monitor groups, and incidents from the Better Stack Uptime API."+ - question: "How are Better Stack regions mapped to openstatus?"+ answer: "Better Stack regions are mapped to the nearest openstatus probe location: US → iad (Virginia), EU → fra (Frankfurt), AS → sin (Singapore), AU → syd (Sydney)."+ - question: "How are check frequencies mapped?"+ answer: "Better Stack intervals are snapped to the nearest supported openstatus frequency: 30s, 1m, 5m, 10m, 30m, or 1h."+ - question: "Can I run the import multiple times?"+ answer: "Monitors, components, and component groups are deduplicated — the importer checks for existing resources before creating new ones. However, incidents and maintenances are always created as new entries, so re-running will produce duplicates for those."+howto:+ totalTime: "PT2M"+ steps:+ - name: "Get your Better Stack API token"+ text: "Go to Better Stack → Settings → API tokens. Copy your Uptime API token (team-scoped, not the global API token)."+ - name: "Preview the import"+ text: "In your openstatus dashboard, go to Status Pages, select a status page, open the Components tab, and scroll down to the Import section. Select Better Stack, paste your API token, and click Preview."+ - name: "Run the import"+ text: "Review the preview summary showing monitors, components, incidents, and maintenances. Toggle what to include and click Import."+---++Openstatus provides a built-in importer that migrates your Better Stack monitors, status page, components, incidents, and maintenances in a single operation. The entire process takes under two minutes.++This guide covers what gets imported, how Better Stack fields map to openstatus, and the steps to run the import from the openstatus dashboard.++For the announcement and background on why openstatus built cross-provider import, see the [blog post](/blog/import-from-statuspage-betterstack-instatus).++## What gets imported++The Better Stack importer reads from the Better Stack Uptime API (v3) and maps resources to their openstatus equivalents. Below is a breakdown of every resource type, the fields that carry over, and known caveats.++### Monitors++Better Stack is the only provider where openstatus imports monitors directly. The importer supports HTTP, TCP, DNS, UDP, ICMP, SMTP, POP, and IMAP monitor types.++| Better Stack field | openstatus field | Notes |+| --- | --- | --- |+| `url` | `url` | Copied as-is |+| `pronounceable_name` | `name` | Display name for the monitor |+| `monitor_type` | `jobType` | Mapped: `status`, `keyword`, `expected_status_code`, `ping`, `ping_icmp`, `smtp`, `pop`, `imap` all become `http`; `tcp` stays `tcp`; `udp` stays `udp`; `dns` stays `dns` |+| `http_method` | `method` | Uppercased (e.g., `get` becomes `GET`) |+| `request_headers` | `headers` | Array of `{name, value}` converted to `{key, value}` JSON |+| `request_body` | `body` | Copied as-is |+| `request_timeout` | `timeout` | Converted from seconds to milliseconds |+| `check_frequency` | `periodicity` | Snapped to nearest supported value (see below) |+| `regions` | `regions` | Mapped to openstatus probe locations (see below) |+| `status` | `active` | `paused` maps to inactive; all others map to active |++#### Region mapping++| Better Stack region | openstatus region | Location |+| --- | --- | --- |+| `us` | `iad` | Virginia, US |+| `eu` | `fra` | Frankfurt, DE |+| `as` | `sin` | Singapore |+| `au` | `syd` | Sydney, AU |++If no regions match, the importer defaults to `iad`.++#### Frequency mapping++Better Stack allows arbitrary check intervals in seconds. Openstatus supports a fixed set. The importer snaps each interval to the nearest supported value:++| Better Stack interval | openstatus periodicity |+| --- | --- |+| 30s | `30s` |+| 60s, 120s, 180s | `1m` |+| 300s | `5m` |+| 600s | `10m` |+| 1800s | `30m` |+| 3600s | `1h` |++Intervals that fall between supported values are rounded to the nearest option.++### Status page++The importer reads your Better Stack status pages and imports the first one it finds. If you have multiple status pages, pass a specific `statusPageId` to target the one you want.++| Better Stack field | openstatus field |+| --- | --- |+| `company_name` | `title` |+| `subdomain` | `slug` |+| `custom_domain` | `customDomain` |++### Component groups++Component groups are assembled from two sources:++1. **Status page sections** -- sections defined on your Better Stack status page become component groups in openstatus.+2. **Monitor groups** -- monitor groups from the Better Stack Uptime API are also imported as component groups.++Both types are deduplicated on subsequent imports.++### Components++Status page resources become openstatus components. Each component is assigned one of two types:++| Resource type | openstatus type | Behavior |+| --- | --- | --- |+| Monitor-backed resource | `monitor` | Linked to the imported openstatus monitor. Status updates automatically from monitoring data. |+| Non-monitor resource | `static` | Manual status management. No linked monitor. |++Components preserve their `public_name`, `explanation` (mapped to description), `position` (mapped to order), and section assignment (mapped to component group).++### Incidents++Incidents are sourced differently depending on whether a status page is present:++- **With a status page**: the importer reads status page reports where `report_type` is not `maintenance`. Each report and its status updates are converted into an openstatus status report with individual update entries.+- **Without a status page**: the importer falls back to the Better Stack incidents API (`/v3/incidents`). Synthetic status report updates are created from the incident timestamps (`started_at` becomes "investigating", `acknowledged_at` becomes "identified", `resolved_at` becomes "resolved").++Incidents and their updates are always created as new entries. Re-running the import will produce duplicates.++### Maintenances++Status page reports with `report_type` set to `maintenance` are imported as openstatus maintenances. The `starts_at` and `ends_at` fields map to the maintenance window, and all status report update messages are concatenated into the maintenance message.++Maintenances are always created as new entries. Re-running the import will produce duplicates.++### Subscribers++Better Stack does not expose subscribers via their API. Subscriber import is **not available**. After completing the import, you will need to re-invite subscribers manually from the openstatus dashboard.++## Step-by-step walkthrough++### Step 1: Get your Better Stack API token++Log into Better Stack and navigate to **Settings > API tokens**. Copy your **Uptime API token**. This is the team-scoped token, not the global API token.++<Image src="/assets/posts/import-from-statuspage-betterstack-instatus/betterstack-api-key.png" alt="Better Stack API tokens page showing where to find the Uptime API token" />++### Step 2: Open the importer and preview++In the openstatus dashboard, go to **Status Pages** and select a status page (or create one first). Open the **Components** tab and scroll down to the **Import** section. Select **Better Stack** as the provider.++Paste your Better Stack API token into the token field. If you have multiple Better Stack status pages, enter the status page ID to target a specific one. Otherwise, the importer will use the first status page it finds.++Click **Preview**. The importer validates your token and fetches a summary of all resources that will be imported. The preview displays counts for monitors, components, component groups, incidents, and maintenances. Toggle individual resource types on or off as needed.++Click **Import** to start the migration. The import typically completes in under a minute.++<Image src="/assets/posts/import-from-statuspage-betterstack-instatus/betterstack.png" alt="openstatus import form for Better Stack with preview summary and import toggles" />++## After the import++Once the import finishes, there are a few things to verify:++- **Monitor regions and frequency.** Check that the mapped regions and periodicities match your expectations. Adjust any that were snapped to a different value than intended.+- **Component-monitor links.** Verify that monitor-backed components are correctly linked to their corresponding openstatus monitors. The importer resolves links by matching Better Stack resource IDs to imported monitor IDs.+- **Component groups.** Confirm that components are organized under the correct groups, especially if your Better Stack setup used both status page sections and monitor groups.+- **Incidents and maintenances.** Review a sample of imported incidents to ensure status update timelines look correct.+- **DNS and custom domain.** If your Better Stack status page used a custom domain, update your DNS records to point to openstatus. See the [docs tutorial](https://docs.openstatus.dev/tutorial/how-to-import-status-page) for instructions on configuring custom domains.+- **Subscribers.** Re-invite your subscribers from the openstatus dashboard. Better Stack does not expose subscriber data via their API, so this step must be done manually.++## Further reading++- [Import from Statuspage, Better Stack, and Instatus](/blog/import-from-statuspage-betterstack-instatus) -- blog announcement covering all three supported providers.+- [How to Import a Status Page](https://docs.openstatus.dev/tutorial/how-to-import-status-page) -- docs tutorial with detailed instructions and screenshots.+- [Top Five Atlassian Statuspage Alternatives](/guides/top-five-atlassian-statuspage-alternatives) -- comparison of status page providers including Better Stack and openstatus.diff --git a/apps/web/src/content/pages/guides/migrate-from-instatus.mdx b/apps/web/src/content/pages/guides/migrate-from-instatus.mdxnew file mode 100644index 000000000..bf71695a5--- /dev/null+++ b/apps/web/src/content/pages/guides/migrate-from-instatus.mdx@@ -0,0 +1,97 @@+---+title: "How to Migrate from Instatus to openstatus"+description: "Step-by-step guide to import your Instatus status page, components, incidents, maintenances, and subscribers into openstatus."+author: "openstatus"+publishedAt: "2026-03-27"+category: "alternative"+faq:+ - question: "How does the Instatus import handle component groups?"+ answer: "openstatus automatically detects which Instatus components are groups vs regular components based on the group references in your data, and creates the correct hierarchy."+ - question: "Are Instatus webhook and Slack subscribers imported?"+ answer: "No. Only email subscribers are imported. Webhook, Slack, Discord, Microsoft Teams, Google Chat, and phone subscribers are skipped — you'll see a warning showing how many were skipped."+ - question: "How are Instatus maintenance windows imported?"+ answer: "Instatus maintenances have a start time and duration. Openstatus calculates the end time as start + duration and imports them with the correct time range."+ - question: "Do incident statuses map correctly?"+ answer: "Yes. Instatus uses the same status names as openstatus (investigating, identified, monitoring, resolved), so the mapping is 1:1."+ - question: "Can I import from multiple Instatus pages?"+ answer: "You can specify a Page ID to import a specific page. Run the import once per page if you have multiple."+ - question: "Can I run the import multiple times?"+ answer: "Components, component groups, and subscribers are deduplicated — existing resources are skipped. However, incidents and maintenances are always inserted as new entries, so re-running will create duplicates for those."+howto:+ totalTime: "PT2M"+ steps:+ - name: "Get your Instatus API key"+ text: "Go to your Instatus dashboard → Settings → API. Copy your API key."+ - name: "Preview the import"+ text: "In your openstatus dashboard, go to Status Pages, select a status page, open the Components tab, and scroll down to the Import section. Select Instatus, paste your API key, and click Preview."+ - name: "Run the import"+ text: "Review the preview summary. Toggle which resources to import (components, incidents, maintenances, subscribers). Click Import."+---++## Why migrate from Instatus to openstatus++Instatus is a solid status page product. But if you need open-source transparency, built-in synthetic monitoring, or monitoring-as-code workflows, openstatus offers a more complete platform without stitching together separate tools.++Openstatus now supports a one-click import from Instatus, so switching does not mean starting from scratch. Your components, incidents, maintenances, and email subscribers carry over in minutes.++For background on the import feature, see [Importing from Statuspage, Betterstack, and Instatus](/blog/import-from-statuspage-betterstack-instatus).++## What gets imported++The table below shows how Instatus resources map to openstatus.++| Instatus resource | openstatus resource | Notes |+| --- | --- | --- |+| **Page** (name, subdomain, custom domain) | Status Page (title, slug, custom domain) | One status page created per Instatus page. |+| **Component with group references** | Component Group | Components referenced as a `group` by other components are automatically detected and created as groups. If a referenced group ID does not exist in the component list, a synthetic group is created using the ID as its name and a warning is shown. |+| **Component** | Component (type: static) | All regular components are imported with their name, description, and order. Imported as `static` type (not linked to a monitor). |+| **Incident** | Status Report + Status Report Updates | All incident updates are imported with their timestamps and messages. |+| **Incident status** | Status Report status | 1:1 mapping: `INVESTIGATING` to `investigating`, `IDENTIFIED` to `identified`, `MONITORING` to `monitoring`, `RESOLVED` to `resolved`. |+| **Incident affected components** | Status Report component links | Component associations are preserved using source ID matching. |+| **Maintenance** (start, duration) | Maintenance (from, to) | End time is calculated as `start + duration` (in minutes). If duration is zero or null, `from` and `to` are the same. Maintenance update messages are concatenated into a single message field. |+| **Maintenance affected components** | Maintenance component links | Component associations are preserved. |+| **Email subscriber** | Page Subscription | Confirmed status is preserved. Selective component preferences are mapped to the imported components. |+| **Webhook, Slack, Discord, Microsoft Teams, Google Chat, phone subscriber** | Not imported | A warning is shown with the count of skipped subscribers. |+| **Monitors** | Not imported | Instatus monitors are not part of the import. Set up monitors directly in openstatus after import. |++### Multi-page accounts++If your Instatus account has multiple pages, the importer fetches all of them by default. To import a specific page, provide the **Page ID** in the import form. You can find your Page ID in the Instatus API or in the URL when editing a page (`instatus.com/app/pages/<page-id>`).++## Step-by-step walkthrough++### 1. Get your Instatus API key++Go to your Instatus dashboard, then navigate to **Settings** and select **API**. Copy your API key.++<Image src="/assets/posts/import-from-statuspage-betterstack-instatus/instatus-api-key.png" alt="Instatus developer settings page showing where to find the API key" />++### 2. Open the import tool and preview++In your openstatus dashboard, go to **Status Pages** and select a page (or create one first). Open the **Components** tab and scroll down to the **Import** section.++Choose **Instatus** as the provider. Paste your API key. Optionally, enter a **Page ID** if you only want to import a specific page.++Click **Preview**. Openstatus fetches your Instatus data and shows a summary of what will be imported: pages, component groups, components, incidents, maintenances, and subscribers. Review the summary and any warnings (such as skipped non-email subscribers or missing group references).++Toggle which resource types to include. Click **Import**. The import runs in seconds for most accounts.++<Image src="/assets/posts/import-from-statuspage-betterstack-instatus/instatus.png" alt="openstatus import form for Instatus with preview summary and import toggles" />++## What to do after import++**Connect monitors.** Imported components are static by default. To get automated status updates, create monitors in openstatus and link them to the imported components. Openstatus supports HTTP, TCP, UDP, and DNS checks from multiple global locations.++**Verify component groups.** Check that the auto-detected group hierarchy matches your original Instatus layout. If a group reference was missing from the component list, a synthetic group was created with the ID as its name -- rename it as needed.++**Update DNS.** If you use a custom domain for your status page, update your DNS records to point to openstatus. The import carries over your custom domain value, but DNS propagation is on your side.++**Notify subscribers.** Your email subscribers are imported with their confirmed status preserved. Consider sending an update through openstatus to confirm the new status page URL if it has changed.++**Remove the old page.** Once you have verified everything works, you can deactivate or delete your Instatus page.++## Further reading++- [Blog: Importing from Statuspage, Betterstack, and Instatus](/blog/import-from-statuspage-betterstack-instatus)+- [Docs: How to import a status page](https://docs.openstatus.dev/tutorial/how-to-import-status-page)+- [Top five Atlassian Statuspage alternatives](/guides/top-five-atlassian-statuspage-alternatives)diff --git a/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx b/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdxindex 9434009da..efde91759 100644--- a/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx+++ b/apps/web/src/content/pages/guides/top-five-atlassian-statuspage-alternatives.mdx@@ -7,7 +7,7 @@ publishedAt: "2025-11-05"category: "alternative"faq:- question: "How do I migrate from Atlassian Statuspage to an alternative?"- answer: "Most alternatives offer import tools or APIs. Start by exporting your component list, subscriber data, and historical incidents. Set up your new status page in parallel, then coordinate a cutover date. Update all integrations and notify subscribers of the new status page URL before making the switch."+ answer: "openstatus offers a one-click importer that automatically transfers your components, component groups, incidents (with all updates), maintenances, and email subscribers from Atlassian Statuspage. Just paste your API key, preview what will be imported, and confirm. See our step-by-step migration guide for details."- question: "Which alternative is most cost-effective for small teams?"answer: "OpenStatus and Betterstack offer the most generous free tiers. OpenStatus provides unlimited team members at $30/month with monitoring included, while Betterstack has a powerful free tier for solo developers. Both are significantly more affordable than Atlassian Statuspage for small teams."- question: "Can I use these alternatives without built-in monitoring?"diff --git a/apps/web/src/content/pages/product/status-page.mdx b/apps/web/src/content/pages/product/status-page.mdxindex 1008251fc..3e2ca1ad1 100644--- a/apps/web/src/content/pages/product/status-page.mdx+++ b/apps/web/src/content/pages/product/status-page.mdx@@ -103,4 +103,10 @@ Manage incidents without leaving Slack. Install the **@openstatus** Slack agentThe agent reads the conversation, looks up your status pages and components, and drafts a status report. Before anything goes public it posts a confirmation card so you can review the title, status, and message. Choose to **Approve**, **Approve & Notify** (sends notifications to all subscribers), or **Cancel**.-The agent is **thread-aware**: when you follow up in the same thread (_"we found the root cause"_ or _"it's fixed"_), it picks up the context and drafts the next update automatically. The entire incident lifecycle - from creation to resolution - can happen in a single Slack thread.\ No newline at end of file+The agent is **thread-aware**: when you follow up in the same thread (_"we found the root cause"_ or _"it's fixed"_), it picks up the context and drafts the next update automatically. The entire incident lifecycle - from creation to resolution - can happen in a single Slack thread.++### Import from Another Provider++Already using Atlassian Statuspage, Better Stack, or Instatus? Import your entire setup -- components, component groups, incidents, maintenances, subscribers, and monitors -- in minutes. Open a status page, go to the **Components** tab, scroll down to the **Import** section, paste your API key, preview what will be imported, and confirm.++Read the [migration guides](/blog/import-from-statuspage-betterstack-instatus) for details on each provider.\ No newline at end of file