• Products
  • Documentation
  • Resources

Zephyr Squad

This page provides an overview of things you should consider when assessing and migrating your Zephyr Squad - Test Management for Jira app data to Cloud.

General guidelines

  • Assess & plan app migration early
    Avoid assessing and planning app data migration late in your migration journey, as this can result in unexpected delays and challenges in your overall migration. If your app data is critical and required in cloud, you should plan your app migration early, along side your core Jira product migration.

  • Communicate directly with your Marketplace Partner
    Contact and establish a communication channel with SmartBear (the Marketplace Partner / app vendor) who owns the ‘Zephyr Squad’ app.
    Marketplace Partners have the most knowledge about their app, and are better prepared to support your migration when they’re informed early about your migration plans, degree of data migration complexity and your specific requirements for Cloud.
    We recommend that you inform your Marketplace Partners about:

    • your planned migration schedule (including updates about changes to your migration plans)

    • security considerations

    • the level of support you require, and

    • any other app specifics that would be valuable for them to know before you continue to install, test and migrate the app to Cloud

  • Refer Smartbear’s documentation for 'Zephyr Squad' migration information.

  • Assess your migration complexity
    Expect a higher degree of migration complexity if you have a large server/DC instances, or a highly customised instance.

  • Consider engaging a Solution Partner
    It is recommended that you engage a Solution Partner to assess, plan and migrate your app data. Solution Partners generally have extensive experience migrating customer data to cloud, and can help you plan ahead, foresee any risks, and offer the right strategies and solutions for migration.

  • Check for Marketplace Partner updates
    You should check for scheduled maintenance or incidents on the Marketplace Partner’s platform that can impact app migration.

  • Check for the level of support you can expect from the Marketplace Partner for migration.

If you’re planning migrations over weekends, we strongly recommend checking if the Marketplace Partner is available to support your migration.


Planning the Zephyr Squad app migration

Estimating app migration time

As migration time is directly dependent on the size and complexity of your data, it’s not always possible to determine exactly how long a migration can take. However, you could try estimating your Zephyr Squad migration time in the following ways:

  • Complete test migrations before committing to any migration timelines. This allows you to get a rough estimate of how long your final production migration can take, and also detect any issues that can potentially arise.

  • Refer Zephyr Squad’s migration planning documentation to understand the various factors that affect migration duration.
    Migration can take a few hours to days, depending on the number of entities you need to migrate.

Reducing (descaling) your app data

You can apply strategies to improve the speed of your future migration, particularly if you find that the migration takes a long time during your test migrations.

  • Descale data (reduce data size) using these options (where applicable):

  • If reducing data size is not possible for your migration requirement, or if descaling data did not reduce migration time sufficiently, contact SmartBear for further options.

Getting app migration progress updates

We recommend that you continue to use the JCMA’s progress logs to monitor your overall core product & app migration, even if you’re viewing the app’s progress on the Marketplace Partner’s own portal.

Unblocking a migration that appears stuck

If your Zephyr Squad migration appears to be stuck, it’s likely that the migration is likely that the migration is taking longer than expected.

For example, you may notice that Jira Cloud Migration Assistant (JCMA) displays the progress percentage at 32% with the following message:
To learn more on the migration procedure and logs, click on the link {{link:https://my-site.atlassian.net/plugins/servlet/ac/com.thed.zephyr.je/zconfig-jcma-migration?s=com.thed.zephyr.je__zephyr-jcma-migration-config-adg}}

In such scenarios:

Before you cancel the app’s migration, we recommend reaching out to SmartBear to confirm the status of your app migration. This is to ensure that you’re not canceling an app migration that actually might be progressing smoothly.

Using alternate migration methods

If the Jira Cloud Migration Assistant (JCMA) isn’t suited to migrating your Zephyr Squad app data, you could consider manually exporting and importing data.

This method isn’t a general recommendation strategy, and should only be used when JCMA isn’t an option for your migration needs. We strongly recommend getting support from the team of consultants at SmartBear in such scenarios, before making a decision about how to migrate.

Still need help?

The Atlassian Community is here for you.