Cloud Migration Resources
Planning a Cloud migration? These resources can help you get started:
→ Time to SLA Cloud features – Review Cloud features and understand key differences between DC and Cloud.
→ Migration support from Appfire – Learn how we can help you migrate smoothly.
I want to migrate SLA data from one instance (DC) to another (DC)
Context: AA user is migrating from one self-hosted Jira instance to another and needs to preserve SLA configurations and historical SLA data during the transition.
User problem: As a Team Leader, I want to migrate from our current Jira instance to another self-hosted instance and ensure that all Time to SLA data is migrated correctly.
Solution: Using Time to SLA’s Import/Export feature.
You can use Time to SLA’s built-in Import/Export feature to transfer SLA configurations, calendars, and regenerate SLA data in the new instance.
Prerequisites
Before you begin, make sure that:
Time to SLA is installed on both Jira instances
Work item histories are fully migrated to the destination instance, as SLA recalculation relies on accurate status and field change history.
For large datasets, perform the migration during off-peak hours to minimize performance impact.
Migration steps
Follow our Import/Export guide for detailed instructions.
Step 1: Export SLA configurations and calendars
Navigate to the Import/Export section in Time to SLA.
Export your SLA configurations and calendars from the source instance.
Step 2: Import SLA data into the new instance
In your destination instance, go to the Import/Export section.
Import the TTS export file from your source instance.
Step 3: Recalculate SLA data
Go to Time to SLA > SLA Recalculation in the top menu.
Enter a JQL query to define the scope of SLA regeneration.
Click Generate to start the recalculation.