Skip to content

Open-source status page, incident response and uptime monitoring

chore: update alternative pages to include importer guide (#2043)

Maximilian Kaske2659c1379cb0
diff --git a/apps/dashboard/.env.example b/apps/dashboard/.env.example
index 9d4cd1c7c..21407096e 100644
--- a/apps/dashboard/.env.example
+++ b/apps/dashboard/.env.example
@@ -78,3 +78,7 @@ TURBO_ENV_MODE=loose
NEXT_PUBLIC_OPENPANEL_CLIENT_ID=something
OPENPANEL_CLIENT_SECRET=something
+
+# used to fix the SVG import issue on Vercel
+# https://github.com/ExodusOSS/bytes/issues/13#issuecomment-3965264022
+NODE_OPTIONS=--experimental-require-module
\ No newline at end of file
diff --git a/apps/web/src/content/pages/compare/atlassian-statuspage.mdx b/apps/web/src/content/pages/compare/atlassian-statuspage.mdx
index f087b5470..6f9a56726 100644
--- a/apps/web/src/content/pages/compare/atlassian-statuspage.mdx
+++ b/apps/web/src/content/pages/compare/atlassian-statuspage.mdx
@@ -73,16 +73,14 @@ The starting prices look similar, but Atlassian Statuspage's $29/month plan only
## Switching from Atlassian Statuspage to openstatus
-Atlassian Statuspage is one of the most common platforms teams switch from. Here's the migration path:
+Atlassian Statuspage is one of the most common platforms teams switch from. Use our **[Statuspage import tool](/guides/migrate-from-atlassian-statuspage)** to automatically migrate your components, incidents, and maintenance history in minutes.
1. **Sign up** for a free openstatus account — no credit card required
-2. **Recreate your components** — set up the same service components you had on Statuspage
+2. **Import your setup** — use the [step-by-step import guide](/guides/migrate-from-atlassian-statuspage) to bring over your components, incidents, and scheduled maintenance automatically
3. **Create monitors** — add HTTP, TCP, or DNS monitors for each component. Unlike Statuspage, openstatus detects incidents automatically from 28 regions — no need for a separate Datadog or Pingdom integration
-4. **Set up your status page** — configure custom domain, branding, maintenance windows, and subscriber notifications
-5. **Configure alerts** — openstatus supports Slack, Discord, Email, PagerDuty, OpsGenie, Grafana OnCall, and more
-6. **Update your DNS** — point your custom status page domain to openstatus
-7. **Notify subscribers** — let your status page subscribers know about any URL changes
-8. **Cancel Statuspage + monitoring tool** — since openstatus includes monitoring, you can cancel both your Statuspage subscription and the separate monitoring service
+4. **Configure alerts** — openstatus supports Slack, Discord, Email, PagerDuty, OpsGenie, Grafana OnCall, and more
+5. **Update your DNS** — point your custom status page domain to openstatus
+6. **Cancel Statuspage + monitoring tool** — since openstatus includes monitoring, you can cancel both your Statuspage subscription and the separate monitoring service
With OpsGenie shutting down in April 2027, this is also a good time to consolidate your incident detection and communication into a single tool.
diff --git a/apps/web/src/content/pages/compare/betterstack.mdx b/apps/web/src/content/pages/compare/betterstack.mdx
index e90840c3b..0263e8c23 100644
--- a/apps/web/src/content/pages/compare/betterstack.mdx
+++ b/apps/web/src/content/pages/compare/betterstack.mdx
@@ -70,11 +70,12 @@ BetterStack's base price looks competitive, but add-ons for private status pages
## Switching from BetterStack to openstatus
+Use our **[BetterStack import tool](/guides/migrate-from-betterstack)** to automatically migrate your monitors, status pages, and components in minutes — no manual recreation needed.
+
1. **Sign up** for a free openstatus account — no credit card required
-2. **Recreate your monitors** — use the dashboard or monitoring-as-code (YAML + CLI) to define them programmatically
-3. **Set up your status page** — openstatus includes branded status pages with custom domain support, password protection, and unlimited subscribers on paid plans
-4. **Configure alerts** — openstatus supports Slack, Discord, PagerDuty, OpsGenie, and more
-5. **Export telemetry** — if you use BetterStack for log management, openstatus supports OpenTelemetry export to push check results into your existing observability stack
+2. **Import your setup** — use the [step-by-step import guide](/guides/migrate-from-betterstack) to bring over your monitors, status pages, and components automatically
+3. **Configure alerts** — openstatus supports Slack, Discord, PagerDuty, OpsGenie, and more
+4. **Export telemetry** — if you use BetterStack for log management, openstatus supports OpenTelemetry export to push check results into your existing observability stack
---
diff --git a/apps/web/src/content/pages/compare/instatus.mdx b/apps/web/src/content/pages/compare/instatus.mdx
index 14a65f3ef..6f899b48a 100644
--- a/apps/web/src/content/pages/compare/instatus.mdx
+++ b/apps/web/src/content/pages/compare/instatus.mdx
@@ -68,12 +68,13 @@ Instatus is $10/month cheaper on the base plan, but it does not include the dept
## Switching from Instatus to openstatus
+Use our **[Instatus import tool](/guides/migrate-from-instatus)** to automatically migrate your status pages, components, and subscribers in minutes — no manual recreation needed.
+
1. **Sign up** for a free openstatus account — no credit card required
-2. **Set up your status page** — configure your custom domain, branding, and components to match your Instatus setup
+2. **Import your setup** — use the [step-by-step import guide](/guides/migrate-from-instatus) to bring over your status pages, components, and subscribers automatically
3. **Create monitors** — add HTTP, TCP, or DNS monitors for each component on your status page, with 28-region coverage
4. **Configure alerts** — openstatus supports Slack, Discord, Email, PagerDuty, OpsGenie, and more
5. **Update your DNS** — point your custom status page domain to openstatus
-6. **Notify subscribers** — let your status page subscribers know about the new URL if it changes
---