Migrate from Compass to DX
As part of Atlassian’s vision to help every engineering team ship faster with higher quality and confidence, we’re consolidating all software component tracking and health features into DX Fabric. DX uses data, insights, and automation to improve engineering standards and AI readiness, so your team can drive continuous, organization‑wide improvement.
With this change, all Compass customers are encouraged to transition to DX Fabric. There are a number of options for this transition, and they are outlined below. Read more about why this transition is happening.
Transition options within DX
For customers transitioning off Compass, we recommend DX Fabric to manage and track their software going forward.
DX Fabric includes a software catalog and scorecard functionality similar to Compass, and is built on a robust data lake that stores all your component data, making it simple to import catalog data from any source and access it in a flexible manner. This forms a foundational data layer that can be paired with AI agents to provide architectural context and automate software health improvements
For a full developer productivity platform, DX offers DevEx Cloud, which extends Fabric with self-reported developer experience metrics to help identify bottlenecks and track the impact of AI.
What if I don’t move to DX?
First, we recommend engaging with your account team with any questions about migration, pricing, and timelines.
If your team is not interested in moving to DX, your access to Compass will expire at the end of your contract or once Compass is no longer supported, which is planned for December 31, 2027.
Feature comparison: Compass and DX Fabric
Feature Area | Supported in DX? |
|---|---|
Custom component types, fields, and metadata | Yes |
Config-as-code | Yes DX offers a Terraform provider, which allows customers to manage their resources/services in Terraform. Through a webhook, DX gets updated when Terraform runs. |
Auto-import of components from source code tool | Yes After connecting your SCM tool to DX, it automatically imports all repositories into the catalog in a pending state that require a user to approve them. DX also offers continuous discovery of newly added repositories. |
Dependency support | Yes DX has a more robust relation model than Compass, supporting both grouped and vertical dependencies. It also offers robust visualizations of relations across your organization. |
Integration with Atlassian Teams | Yes There is a sync available from Atlassian Teams to DX teams that runs nightly. This ensures you can continue to use Atlassian Teams as your source of truth while you update to DX. If your team is not using Atlassian Teams as your organization source of truth, DX also has various connectors to tools like Workday that can be used to populate DX Teams. |
Link to Jira Service Management services from Catalog | Yes Within a DX entity, you can add a link (alias) to the relevant JSM Servic |
Link to DX entities from Jira Service Management | Current Gap When creating an alert or incident in Jira Service Management today, you will not be able to connect a DX entity as an affected service. However, when migrating from Compass to Jira Service Management, your Compass services are automatically imported into JSM, and can then be connected to alerts or incidents. For more information, see Migrate from Compass to Jira Service Management. |
Jira integration Link components to work items and filter Jira boards by component | Current Gap Within DX, you can connect a Jira work item to an entity via alias. However, within Jira, you cannot connect a DX entity to a work item. |
Show on-call schedules per component | Yes There is a built-in entity property for attaching an on-call schedule in DX. DX Catalog entities with a Jira Service Management alias will get on-call users in the DX catalog. |
Audit logs for catalog changes | Yes DX offers audit logs on changes made to the catalog from the UI. |
Custom Forge Apps | While DX is not supported within the Forge platform, it offers a flexible and robust API that allows you to programmatically access all catalog data to suit any custom needs. |
Data migration
When migrating from Compass to DX Fabric, there will be a fully supported onboarding process that includes tooling to sync your data. This tooling includes a one-time migration sync to import your Compass components into DX, as well as an automated daily connector to sync Atlassian Teams into DX.
What data gets synced?
When the catalog component connector is ran during onboarding, all components and component metadata are imported (including custom fields) unless otherwise described below:
Components will be imported into DX and recreated as entities. You can choose which entity types to use during the import.
Atlassian Teams will be imported to DX on a once-a-day basis to stay up to date, and are mapped to DX Teams.
There are two key differences between Atlassian Teams and DX Teams: 1) In DX, each user can only belong to one team, and 2) all teams must have a team lead. Due to this:
If users are a part of multiple Atlassian Teams, they’ll be assigned to only one of them in DX
The creator of the Atlassian team (if active) will automatically be assigned as the Team Lead during import, as Atlassian Teams lacks a dedicated team lead concept. If the team creator is no longer active, another member of the team will be assigned as the Team Lead.
As you import your teams into DX, ensure that Team Leads are properly assigned throughout your organization.
Once Atlassian Teams are imported to DX, component owners will be populated as well.
Dependencies will be imported into DX as relations.
This connector requires both Compass and DX API keys.
What data does not get synced?
Scorecards don't sync into DX, and must be recreated after onboarding to DX. Read about how to add scorecards to DX
ModernOps on-call schedules linked to Compass components will not be imported into DX entities.
All alerts and operations functionality must be migrated to Jira Service Management, as it is not supported in DX. Read about migrating to Jira Service Management
Steps for migration
Have your Compass admin reach out to your account representative or the DX team to schedule a migration date.
On this date, you’ll be invited to a call with the DX team to kick off the migration.
The DX team will guide you through the migration and onboarding, including:
Transferring all catalog data from Compass to DX
Syncing Atlassian Teams into DX
Setting up scorecards and other features within DX
After this, you will have one month with access to both DX and Compass to finish the migration.
Moving to DX
To begin your migration, reach out to your account representative, who will guide you through the process. If you don't have an account representative, please reach out to the DX team.
Was this helpful?