This article explains what happens during auto migration and what users need to be aware of before the migration takes place.
During auto migration, the following actions are done automatically:
This section explains how user roles and shared access from DataPrep 1.0 are mapped to the updated roles in DataPrep 2.0 during migration. Learn more.
During auto migration, the editor and Data consumer users will be removed as these roles are not available in Zoho DataPrep 2.0. User Group sharing in editor and data consumer role will also be removed.
However, you can manually reshare the required workspaces or pipelines with users in any role after migration.
During auto migration, new pipelines will be created for each group of related datasets. There won't be individual datasets listed in the UI.
For additional details on how datasets from DataPrep 1.0 are structured into pipelines in DataPrep 2.0 as part of the auto migration process: Learn more.
During auto migration, the lowest scheduling frequency among the grouped datasets is applied to the newly created pipeline schedule, and the schedule is set to a paused state. You can review and enable the schedule after migration if needed.
For more details on how existing schedules from DataPrep 1.0 are represented in DataPrep 2.0 during the auto migration process: Learn more
To ensure a successful migration, please review the following:
Fix ruleset errors: If a dataset contains any errors in the ruleset, the migration for that entire workspace will fail. In that case, you will receive an email notification to fix the errors. Once you fix them, you can try to migrate the dataset again. If errors are not resolved within 7 days and manually migrated from your end, the workspace and associated datasets may not be migrated and data could be lost.
Clean up unused workspaces and datasets: You can permanently delete workspaces and datasets that are no longer required. During migration, all datasets are processed and keeping unused datasets may increase rows processed and storage usage during migration. Cleaning up in advance helps you avoid unnecessary usage increases.
Migration of a dataset fails if there are any errors in the ruleset, and if even one dataset contains errors, the migration of the entire workspace will fail. In that case, you will receive an email notification to fix the errors and you can try to migrate the workspace again. If errors are not resolved within 7 days and manually migrated from your end, the workspace and the associated datasets may not be migrated and data could be lost.
If you prefer to migrate manually before the auto migration date, please refer to our migration guide.
You can refer to our FAQs for answers to common questions on migration.