Migrate Statuspage to use Atlassian accounts
Learn everything you need to know to migrate you and your team to Atlassian accounts.
Private and audience-specific page viewers are not affected by this migration. We only change the way how team members log in to manage your Statuspage.
If you would like to use a different email than the one you’ve been using to access Statuspage, you can:
Invite a new user with that email address
Complete the migration process with that account to migrate your organization’s accounts
Account owners become the equivalent of a site admin. Site admins administer the users and groups for the site’s products (in this case, Statuspage). They have access to the site's Administration and access to the products through this group.
Team members remain unchanged and will be listed as basic users in Atlassian Administration.
If you’re using a social log in (Google, Microsoft) to access Statuspage, make sure this is the same email shown on the Create and verify your Atlassian account screen. If the email is different than what you’d like to use, follow the steps above (see: What if I want to use a different email address to create my Atlassian account with?).
After migration, you can select to Continue with Google/Microsoft on the log in screen.
Atlassian accounts can’t be made for distribution list emails. Before you migrate, any users currently accessing Statuspage with a distribution email need to be invited as new users with unique email addresses. Then they will need to log in with that email for their account to be migrated along with the rest of their organization.
If the account owner is using a distribution list, follow the steps above (see: What if I want to use a different email address to create my Atlassian account with?).
Upon migrating, we'll provide an extension to your Atlassian Guard Standard (formerly known as Atlassian Access) trial to help you adjust to using Atlassian admin and SSO tools. (excluding Free and Hobby pricing plans). Here are some examples of how your Atlassian Guard Standard bill is calculated:
Example 1:
You are only using Statuspage (on a qualifying pricing plan), with 10 users. You'll need an Atlassian Guard Standard subscription and your bill will be $0.
Example 2:
You are only using Statuspage on Free or Hobby pricing plans, with 2 users. You'll need an Atlassian Guard Standard subscription and your bill will be calculated according to Atlassian Guard's pricing plan.
Example 3:
You are using Jira Cloud (or any other Atlassian cloud product) and Statuspage, with a total of 100 users. 10 users out of the 100 are using Statuspage. Your Atlassian Guard Standard bill will be for 90 users.
Accidents happen! See the documentation: Transfer products to another organization to move your Statuspage instance to the right site/organization in Atlassian admin.
Was this helpful?