Can I migrate between Tempo for Cloud and Tempo for Server/Data Center?

This article is for Tempo for Cloud and Data Center

Question	Can I migrate between Tempo for Cloud and Tempo for Server/Data Center or vice versa?
Answer	Atlassian recently made an announcement regarding its intent to accelerate their journey to a cloud-first company. Over the next 3 years, Atlassian’s Server offerings will be adjusted to eventually lead to a complete transition away from the platform to a Cloud or Data Center deployment. We recognize this will have an impact on Tempo’s Server customers and partners. Here is what we know right now: Atlassian is simplifying their on-premise offerings and will no longer sell new perpetual licenses for Server and switch to subscription licensing only with Data Center and Cloud as of February 2nd, 2021. Existing Server customers will be able to renew their maintenance until February 2nd, 2024 when Jira Server reaches End-Of-Life, and will be able to purchase new Tempo Server licenses until February 2023. Support for these applications will continue until February 15th, 2024. We will continue to invest in and support our Data Center customers beyond 2024, and actively support migrations from Server to Data Center, for those customers looking at that option. As we have been successfully leaning into the Cloud over the last few years, Tempo was well prepared for this announcement, and, in many ways, we were simply waiting on Atlassian’s timing. This includes our recent efforts to focus on Server to Cloud migrations, and building out required tooling in close collaboration with Atlassian. Although we are excited about this shift in technology and business models, we recognize that this is going to be a major change for some of our customers and partners. We will do everything in our power to make it easier for all of our Atlassian customers. This includes our commitment to and ongoing support of Server to Cloud migrations, and participation in multiple programs with Atlassian that are aimed at identifying and removing blockers to cloud adoption. As Atlassian is moving away from Server products, we would strongly recommend against migrations from Cloud to Server. Data Center deployments are the recommended alternative.

Question

Can I migrate between Tempo for Cloud and Tempo for Server/Data Center or vice versa?

Answer

Atlassian recently made an announcement regarding its intent to accelerate their journey to a cloud-first company. Over the next 3 years, Atlassian’s Server offerings will be adjusted to eventually lead to a complete transition away from the platform to a Cloud or Data Center deployment. We recognize this will have an impact on Tempo’s Server customers and partners.

Here is what we know right now:

Atlassian is simplifying their on-premise offerings and will no longer sell new perpetual licenses for Server and switch to subscription licensing only with Data Center and Cloud as of February 2nd, 2021.
Existing Server customers will be able to renew their maintenance until February 2nd, 2024 when Jira Server reaches End-Of-Life, and will be able to purchase new Tempo Server licenses until February 2023. Support for these applications will continue until February 15th, 2024.
We will continue to invest in and support our Data Center customers beyond 2024, and actively support migrations from Server to Data Center, for those customers looking at that option.

As we have been successfully leaning into the Cloud over the last few years, Tempo was well prepared for this announcement, and, in many ways, we were simply waiting on Atlassian’s timing. This includes our recent efforts to focus on Server to Cloud migrations, and building out required tooling in close collaboration with Atlassian.

Although we are excited about this shift in technology and business models, we recognize that this is going to be a major change for some of our customers and partners. We will do everything in our power to make it easier for all of our Atlassian customers. This includes our commitment to and ongoing support of Server to Cloud migrations, and participation in multiple programs with Atlassian that are aimed at identifying and removing blockers to cloud adoption.

As Atlassian is moving away from Server products, we would strongly recommend against migrations from Cloud to Server. Data Center deployments are the recommended alternative.

Those Tempo Timesheet users that have migrated from a Cloud instance to a Server instance and are currently using any version prior to version 8.13.1

will need to perform the following actions after upgrading to version 8.13.1 or any version after that.

Those that are upgrading from any version released after 8.13.1 do not need to take note.

See here for more information

Those Tempo Timesheet users that have migrated from a Cloud instance to a Server instance and are currently using any version prior to version 8.13.1 will need to perform the following actions after upgrading to version 8.13.1 or any version after that.Those that are upgrading from any version released after 8.13.1 do not need to take note. This article is for Tempo for Data Center.Notes: Database modification is not supported by by Atlassian and Tempo. The scenario when this KB is needed is that customer has migrated between Cloud and Data Center. Since the migration is also not supported by Tempo, and the customer still decided to do so, then they'll have to follow this KB to generate the missing database table (Default Rate table does not exist in Cloud instance), which was supposed to be created automatically during normal upgrade or in new fresh install.We would always recommend that you to make a database backup before following the following steps in case something does not work out.QuestionWhat to do if "Error! Default Rate Table could not be found" message shows up after upgrading to Tempo 8.13.1?AnswerPlease, run these two queries on your database. INSERT INTO "AO_C3C6E8_RATE_TABLE" ("ID","NAME","CURRENCY_CODE","DEFAULT_TABLE","EFFECTIVE_DATE") VALUES (1,'Tempo Default Price Table','USD',true,'2003-01-01'); INSERT INTO "AO_C3C6E8_RATE" ("ID","AMOUNT","LINK_ID","LINK_TYPE","RATE_TABLE_ID") VALUES (1,'0',0,'DEFAULT_RATE',(SELECT "ID" FROM "AO_C3C6E8_RATE_TABLE" WHERE "DEFAULT_TABLE" = true)); These queries should recreate the rate tables that were not created with the upgrade, but you'll need to configure the rates manually.