What happens to my existing projects?
In Migrate 3, projects are automatically named after the destination domain name. However, with Migrate 4, you now have the flexibility to assign custom names to your projects. Additionally, in Migrate 4, each project is directly associated with a specific destination platform connection, including both the domain name and platform.
When upgrading to Migrate 4, your existing projects will be carried over with the destination domain name as their default project name.
If an existing project contains configurations for multiple destination platforms (e.g., Google Workspace and Google Vault), Migrate 4 will create separate projects for each platform. The additional project will have the destination platform name appended to its title.
If an existing project includes configurations for multiple source platforms, a new source connection will be created and integrated into the corresponding project in Migrate 4.
What happens to my existing configurations?
In Migrate 3, you can create multiple configurations within a migration project, each containing distinct settings for the source and destination platforms. However, in Migrate 4, connections are created independently of projects and can be reused across multiple projects.
Additionally, Migrate 4 replaces the concept of configurations with migration batches. Now, each source connection within a project can support multiple migration batches.
When upgrading to Migrate 4, the source and destination platform settings from your existing configurations will be converted into reusable source and destination connections within your project. A migration batch will then be created in the appropriate project, within the correct source connection, using the same name as the original configuration from Migrate 3.
What happens to my existing child configurations?
In Migrate 3, you have the option to create child configurations within your main configurations. This enables you to isolate specific items from the parent configuration and apply customized settings to them.
When upgrading to Migrate 4, these child configurations will be converted into migration batches within the project, linked to the appropriate source connection. If the source platform settings in the child configuration differ from those in the parent, a new reusable source connection will be created, and the migration batch will be associated with that connection.
What if I want to make a change to my platform settings?
As previously noted, platform settings will be converted into reusable connections, which will be named using the format 'domainname-platformtype'. If you need to modify these connections, they can be easily accessed from the Connections tab on the left-hand side.
The Projects page will also display which connections are being used within your projects.
Can I roll back to Migrate 3?
There isn't a direct rollback option for Migrate 3 to Migrate 4. However, migrating to Migrate 4 is non-destructive, meaning your data will remain intact. The only change will be how the data is displayed in the new user interface.