Moving from a Connect customer-sync app

Atlassian is ending support for Connect apps on 31 January 2027. If a Connect app keeps your organizations in step today, here’s how to move without losing track.

Why move

Atlassian is retiring Connect, the older app framework, in favor of Forge. Connect apps lose support on 31 January 2027. Customer Roster is a Forge app that runs on Atlassian: no outside servers, data in Atlassian's cloud. Check your current app's listing or vendor for their own plans first.

Step 1: write down what the old app does

For each rule in your current app, note the source (group, domain, list), the target organization, the projects, and whether it removes people. Export your organizations and memberships now (Customer Roster's Export works before you set up any rules), so you have a before-picture.

Step 2: set up the same rules in Customer Roster

• Create each sync rule and domain rule, and read the preview before saving.
• People already in the organization are treated as added by hand: Customer Roster never removes them. It only removes people it adds itself.

Step 3: don't run both at once

Two apps syncing the same organization can undo each other's work — especially if the old app removes anyone who isn't in its source. Pause or switch off the old app's rule before saving the new one, then remove the old app when you're happy.

Step 4: check the result

• Export again and compare with your before-picture.
• Run the wrong-organization report. It checks organizations that have email domains in Customer Roster.
• If a rule went wrong, Undo last sync.