App catalog migration process commences on 22nd Aug 2022

Hi everyone! Here’s an update (13th Oct’22):

Over the past month we’ve migrated the catalog data in the background for all paid cloud apps that were listed before the catalog migration process began on 1st September. This background step is now complete for all apps that were listed before 1st September. Thank you all for your patience during this process. It is an important foundational step to support customers purchasing apps on the new billing system.

During the catalog migration period, around 20 new apps have been published on the Marketplace. If your app was published between 1st September and October 19 (tentatively), we plan to migrate the catalog data to the new billing engine in the next week. These will be the last apps to be migrated. All apps published after this last group will be automatically published on both the old system and the new one.

Please note: This is a background step for the new billing engine that does not impact and is not dependent on the new data pipeline.

Update 25th Aug’22 : Here are the new timelines for app catalog migration. We plan to start it on 1st Sept and complete by end of Sept. We have also created a page in the Partner Portal that has the order in which the partners are to be migrated.

Update 24th Aug’22 : App catalog migration has been put on hold temporarily since we are waiting for a few internal approvals from other teams to ensure it doesn’t impact any of our internal processes. We will notify you about the new timeline which will be in the next 2-3 weeks. As communicated earlier, we will make sure to give a one-week heads up before we start the app catalog migration.

Please note: We’ve made clarifying updates to this post in response to feedback that the scope of this activity was unclear. Please feel free to add other clarifying questions in the comments.


Hello Marketplace Partners,

This is to announce that Atlassian, as a part of its cloud transformation, is migrating the app catalog (app entities and pricing plans only) to new billing engine as communicated earlier through Stage 0 or the line item “app catalog migration - temporary unavailability of app management” in Resources for Marketplace Partners to navigate Atlassian’s migration to a new billing engine. This is a month long activity, starting from 22nd August 2022 to 23rd September 2022 with cohorts of apps being migrated every day.

Please note, this is work being done in preparation for our eventual go live of apps for customers to purchase on the new billing engine, but it is not the production go-live of apps or customers who purchase apps on the new billing engine. Production go-live of apps and customers who purchase apps on the new billing engine continues to be dependent upon Marketplace Reporting efforts in progress by Atlassian (See the latest update about reporting stability improvements here).

What’s the impact for Marketplace Partners ?

Partners whose apps are being migrated are requested to kindly refrain from making any updates to the app data (like editing app data or app pricing) during the migration period as it may result in loss of data.

The migration blackout period would be 2-3 hours per app. So, the total blackout period depends on the number of apps the Marketplace Partner owns. Once the migration is done successfully, partners can continue to edit app data for the migrated app. Partners will still be able to access apps transactional data and reports during the blackout period. To minimize the blackout impact, we will try to do the migration activity during off-hours of the partners.

Also please note that Partners will still be able to publish new apps during migration.

Each day, only a few partners will be migrated. All the apps for a single Marketplace Partner will be migrated in a single day, so one partner will experience only one day of disruption. All those partners are notified through Status page and Announcement banner on the vendor portal where you manage apps.

In addition to the temporary blackout period, Marketplace Partners should be aware that one of the workflow impacts outlined on the Resources for Marketplace Partners to navigate Atlassian’s migration to a new billing engine page — the “App Lifecycle - Paid to free conversion, and Archival Process” change — will also go into effect once your apps are on the new system.

Please note that these are background changes that we need to make in order to prepare for the new billing engine to support Marketplace app purchasing. The changes will not impact reporting and are not dependent on our new reporting pipeline. Any changes that impact reporting are still being delayed until Marketplace reporting is moved to a new data pipeline.

What’s the impact for customers ?

There’s no impact from customer side. Customers will still be able to view and use apps and make app purchases. Customers will still be billed through old billing system at this stage. We are not yet supporting app purchasing on the new billing engine at this time, as this is dependent on Marketplace reporting moving to a new data pipeline.

In case you need any help during the process, you can reach out to Marketplace Support.


How does it impact us (Marketplace Partners) ?
As part of this activity, we are only copying app catalogue data from old billing system to new billing system. So, there’s no impact on app data. To avoid data loss, You should refrain making any updates to existing apps during the migration which includes

  • Update App details - name, description, loyalty discount
  • Create new version of app
  • Update pricing of the app

You would still be able to publish new apps.

Your apps in the approval queue would not be approved on the migration day, which results in delay by one day.

Can we publish a new version of our app to the Marketplace?
You can only publish new apps. Please refrain from publishing new app versions during the 2-3 hour black out period specific to your app to ensure none of your updates are lost.

Should we stop our CI/CD pipelines from sending updates to the Marketplace?
It would be safest to stop them during the window (approximately 2-3 hours per app), all CI/CD mechanisms that use marketplace API to

  • Update App details - name, description, loyalty discount
  • Create new version of app
  • Update pricing of the app

should be disabled. If you are concerned, please open a ticket with Marketplace Support and we can work with you to minimize impact on your workflows.

Will this prevent clients from purchasing our apps?
No, customer billing will not be impacted. Customers will still be billed through the old system at this time. This stage is just a background step to lay the foundation to eventually support apps on the new billing engine.

Is there a communication when our apps will be started and when it is safe to resume operations?

You will see a banner on the vendor portal while the app entity and pricing plan migration is taking place. When this banner is gone you are safe to resume operations. We will also update Statuspage when the blackout period is over and migration is complete.

We are scheduling the migration windows with your time zone in mind in an effort to minimize downtime during your working hours.

Will customers see an impact to them during the transition?
At this stage, customers will experience no impacts. This work is being done in preparation of the eventual go-live of apps on the new billing engine. Customers who own apps are not planned to be migrated to the new system until later in the calendar year and this customer-facing release is dependent upon the work Atlassian is doing to improve current marketplace reporting pipelines (click here for more details).

Dinesh Kollosu,
Product Manager, Atlassian Marketplace


what does “app data” mean? Do you mean information filled at the marketplace or we shouldn’t release new versions of applications?

1 Like


We (Elements) are not part of the first batch, but our marketplace back office indicates that we are being migrated.

@KollosuDinesh can you explain what’s going on?


1 Like

Hey @christophe.prome , The message wasn’t supposed to be shown. Let me connect with the team and fix it.

1 Like

Hi @christophe.prome, Sorry for the trouble. This is fixed now and it would only be shown to relevant partners during migration.

1 Like

Thanks for the update and for solving the issue @KollosuDinesh

1 Like

Hello @KollosuDinesh,

I just learned that the migration that was due to happen yesterday was postponed and no new date has been set yet.

Could you please let me know via when a new date has been determined and for any changes of this date? Also, please let me know once the migration was successful. We have automated processes running via the Marketplace API that we need to disable for the migration, and I don’t want to disable/enable them more than necessary.



Hey @KollosuDinesh,

I just saw the updates you had made to your original post. I just wanted to let you know that I didn’t get any notifications about this even though I was watching this thread. Next time it would be amazing if you could add a new comment to the thread to let people know that you have updated the original post, so that notifications are sent out. :slight_smile:



Thanks @SvenSchatter, I also wouldn’t have caught this without your post.

1 Like

Hi @KollosuDinesh,

we were part of the first batch and it looks like the banner in the Marketplace UI telling us not to update our listings has disappeared. Does this mean we’re good to to touch stuff again?

Any updates on this, maybe by posting here that Batch 1 has been successfully completed, or even just marking that on the linked page in the partner portal would be very nice.


Hey @SvenSchatter,
When you start seeing banner on the Marketplace UI, it means the catalog migrations has started and when it disappears the catalogue migrations has ended.
Sure, We would update the partner portal schedule page with a ‘completed’ label for the partners that were migrated successfully.