Take advantage of the opportunities of Flow Cloud, including the most up-to-date product releases, by migrating your Flow Enterprise Server instance to Flow Cloud.
Migrating can take some time, depending on your current Flow Enterprise Server version as well as other factors. Use this article to get a better understanding of the overall process.
Note: While migrating to Flow Cloud, you can continue to use your Flow Enterprise Server instance. As your data begins to ingest into your cloud instance, you may notice slower data processing times, since you’re more likely to hit githost rate limits.
In this article
Why should I migrate to the cloud?
While Flow Enterprise Server has its benefits, and may be suiting your needs, there are several benefits to moving to the cloud, including:
- Immediate access to the latest features and releases, including new delivery workflow analytics
- Access to pre-release features through Pluralsight’s alpha and beta programs
- Significantly reduced costs related to hardware and maintenance
- Improved performance and uptime, with no need to apply patches or updates
How do I start the migration process?
If you’re interested in migrating to Flow Cloud, reach out to your Customer Success Manager or Account Executive at Pluralsight to start the conversation.
After that, you will be provided with Flow cloud security documentation for you and your Information Security team to review.
Once your team approves the information, your Pluralsight contact will follow up with information about any contract amendments and statements of work you may need to sign to proceed with the migration. This process will look slightly different for each customer. Ask your Pluralsight contact for more information on exactly what you can expect.
During this time, you’ll be asked to provide information about your current Flow Enterprise Server instance. This information will help your migration team know how best to assist you when you migrate—because every Flow Enterprise Server instance looks very different, we want to have the most up-to-date information to best help you be successful in the cloud.
Information you’ll be asked for may include:
- The size of your database
- The total number of integrations, repos, active users, and aliases you currently have
- The total number of commits and PRs that Flow has processed
The migration team will work with you to find the answers to questions about your current implementation, so you can have the best success during migration.
What steps will I need to take during the migration?
Once the migration is approved, the process of migrating your instance begins.
The migration process will largely look like setting up a new Flow instance, following the steps for Getting started with Flow. You will need to reconnect your integrations, reingest your data, and remerge your users. This process takes time, but your migration team will help you through it.
Tip: If you’re on a Flow Enterprise Server version 2020.3.1 or newer, download your team membership from your Flow Enterprise Server instance so you can easily upload it to your new cloud instance. That way you don’t have to recreate your teams manually.
Your migration team will walk with you through the steps to get up and running in your new Flow cloud instance.
If you’re interested in discussing a migration to Flow cloud, reach out to your Customer Success Manager or Pluralsight Account Executive.
If you need help, please contact Pluralsight Support.