Choose an onboarding path
If you are evaluating a replacement for Atlassian Statuspage, read Status Page comparison.
Create a status page from scratch
Creating from scratch only establishes the status page entity and confirms its page title, URL, and type. Configure branding, domain, components, subscriptions, and event publishing in the follow-up docs.1
Choose the status page type
Sign in to the Flashduty console, open On-call → Status Pages from the left navigation, and click Create public page or Create internal page. Public status pages are for customers, partners, and external visitors. Internal status pages are for organization members and require Flashduty sign-in.
2
Fill in creation details
Fill in the following fields:
3
Complete creation
Click Create to finish. After creation, configure basic settings, components, subscriptions, templates, and event publishing as needed.
Migrate from Atlassian Statuspage
If you already use Atlassian Statuspage, you can use Flashduty CLI to migrate components, sections, historical events, and subscribers to Flashduty Status Page. Migration is split into two independent steps:- Migrate structure and history: import components, sections, historical events, maintenance records, and notification templates.
- Migrate subscribers: import email subscribers (and best-effort Microsoft Teams Workflows channel subscribers) along with their subscription preferences.
Prerequisites
Install Flashduty CLI
- macOS / Linux
- Windows (PowerShell)
- Manual download
Log in to Flashduty
Get your Atlassian Statuspage API key
- Log in to the Atlassian Statuspage management panel
- Go to User icon → API info and copy the API Key
- Set the environment variable:
Get your Atlassian Statuspage page ID
In the Atlassian Statuspage management panel, the Page ID is displayed in the page URL or page settings. It looks like0db0rq26tg1l.
Migration steps
Migrate structure and history first, then migrate subscribers, and switch the domain last.1
Migrate structure and history
Run the following command to import Atlassian Statuspage components, sections, historical events, maintenance records, and notification templates. This step creates or reuses the target Flashduty status page.
Format and uniqueness requirements for
--url-name:- Normalized automatically: lowercased, hyphen-separated, and capped at 255 characters. Pure-symbol input or anything that normalizes to an empty string is rejected.
- Globally unique across the account’s public status pages. Duplicates are rejected.
2
Check migration progress
Migration jobs run asynchronously, and the command returns immediately with a Job ID. Check progress with:The structure and history migration runs 5 steps in order:
- Create (or reuse) the target status page.
- Import sections.
- Import components.
- Import historical incidents, including maintenances.
- Import event templates.
target_page_id is the Flashduty status page ID. You need it to migrate subscribers.To cancel a running migration job, run:3
Verify imported content
Before proceeding, verify the imported data:You can also log in to the Flashduty console to visually inspect components, sections, and incident history.
4
Migrate subscribers
After confirming the structure and history are correctly imported, run the subscriber migration:
Subscriber migration behavior by channel:
- Email: imported directly and active immediately without email verification. Addresses marked as quarantined in Atlassian are skipped.
- Microsoft Teams (Workflows): subscribers with exportable modern Teams Workflows webhook URLs (
*.logic.azure.com/*.environment.api.powerplatform.com) are migrated on a best-effort basis, and Teams subscription is automatically enabled on the target public status page once imported. Subscribers using retired Office 365 Connector URLs (*.webhook.office.com) or missing webhook endpoints are skipped and listed inmigration-statuswarnings so you can recreate them with Teams Workflows webhooks. - Slack: Atlassian Statuspage does not expose Slack OAuth tokens or webhook URLs via API, so Slack subscribers are skipped and reported in
migration-statuswarnings. Enable Slack subscriptions on the target page and have users authorize via Subscribe → Slack. - SMS and other unsupported modes: skipped automatically.
5
Switch domain and RSS/Atom
If your original Atlassian Statuspage used a custom domain, point the CNAME record to the Flashduty-provided status page address. Flashduty is compatible with
history.rss and history.atom, so existing RSS/Atom subscriptions can keep working.See Configure status page basics for custom domain configuration. See Subscription management for RSS/Atom feed behavior.