Migration Prep Tool FAQs

Last modified: November 29, 2022
What should I do to prepare for the migration?

To prepare for Server migration, you can run the Pre-Upgrade Checks and back up your MongoDB. For more information, see Prepare for Migration

Will the Migration Prep Tool interrupt normal operation?
  • No, the migration prep step is non-blocking and should be able to be run without disturbing normal operation of your Server. 
  • The Migration Prep Tool prepares a new workflows table that is non-operational until after the upgrade. The new table has all the same workflows and apps in it, but they will be encrypted with the new AES256 standard using the Alteryx crypto library which Alteryx has standardized for better security. 
  • The system uses machine-level encryption, so there is no way to input, see or update the AES256 key being used for the encryption at this time. 
Will the Migration Prep Tool affect performance?

There will be a little bit of a performance hit on the Mongo instance. The Mongo instance should not run on the same box as a Worker. If the customer is using embedded MongoDB, it will be in the Controller, so there will be some degradation there. Users should not notice the performance hit. Engineering is still testing this though. 

Are there any time limits on when I need to finish the upgrade?

There are no time limits, but the longer you wait to do the upgrade while your users are modifying workflows, the more workflows need to be converted in the final steps of the upgrade which is during your maintenance window. Therefore, your overall downtime might be longer. Ideally, run the upgrade within a day of finishing the Migration Prep. 

How do I confirm that all my workflows are successfully migrated?

There will be a log file at %ProgramData%\Alteryx\Service\AlteryxServiceMigration_0.log that will explain if there were any failures during the migration. You can change this location and name when you are running the migration tool in advance of the upgrade.

It is important to verify that all workflows were successfully migrated. If there are any failures, we recommend you reach out to Support for help in resolving the discrepancies. 

A final run of the Pre-Upgrade Checks can also confirm that your database is once again healthy, and your upgrade is complete. 

Was This Page Helpful?

Running into problems or issues with your Alteryx product? Visit the Alteryx Community or contact support. Can't submit this form? Email us.