/
Before migration - requirements and understand limitations

Before migration - requirements and understand limitations

Not all data from The Scheduler DC is migrated to Cloud

Dear customers,

Please contact us if you encounter any issues during migration. Atlassian supports a wide range of add-ons and custom fields that often require individual handling on our side.

If you experience any difficulties, reach out so we can adjust the migration to meet your needs.

Thank you for your cooperation.

Won’t be migrated

  • Calendars (global and project)
    Calendars in Cloud are more limited due to data storage constraints. As a result, calendars from The Scheduler DC will not be migrated.

  • Scheduled Issues ownership
    In DC, each Scheduled Issue has an explicit Owner and templates can be shared with specific users.
    In Cloud, all users with access to the app within a project have the same permissions, and The Scheduler app is considered the Owner. Ownership information will not be migrated.

  • Execution history
    Differences in how the system identifies issues created by the app mean that not all historical execution data can be reconstructed in Cloud.
    You will not see the complete list of issues created from a particular Scheduled Issue after migration.

Limited migration

  • Maximum 10 subtasks
    When migrating a Scheduled Issue with more than 10 subtasks, only the first 10 will be migrated. This is the application limit.

On request, we can increase your subtask limit. In that case, the migration limit will match the configured limit on your Jira Cloud instance.

Retrying migrations

Rerunning existing migration plan is currently unsupported and may cause unexpected behavior (for example, your migration may be stuck indefinitely on 0% progress). We’re planning to address supporting migration reruns in the future - in the meantime, please create new migration plan each time you want to “retry” your DC->Cloud migration.

Recommendations

  • Clean up
    Remove unused templates before migration. If you are keeping old templates only to access their execution history, be aware that execution history will not be migrated. Instead, create a Jira filter or add a dedicated label to issues created from those templates so you can track them in Jira.

  • Clean up (again)
    Migration is a good opportunity to review and rationalize your templates. Remove unnecessary or unused templates to simplify your configuration in Cloud.

Data Security in terms of migration

Here you can read about it: Data Security and Privacy Statement