Migrate from Zoho DataPrep 1.0 to 2.0
Zoho DataPrep has been upgraded to the new 2.0 version. In this new version, it is easy to build an end-to-end pipeline and have a complete control on data movement with our visual pipeline builder. This pipeline builder lets you bring data from multiple data sources, perform various transformations, including data blending, and export to multiple destinations in a single pipeline. This pipeline can be scheduled as a whole to make orchestration, pipeline management, and monitoring much easier.
However, this requires users to map their existing datasets to pipelines so that we can groups the datasets together and show as pipelines. This process can be done using our migration wizard, which lets you migrate your 1.0 workspaces to 2.0.
Important: Please ensure you have error-free datasets while migrating data from 1.0 to 2.0
Here's a quick video on how to migrate data from Zoho DataPrep 1.0 o 2.0
How to take a backup before migrating data from 1.0 to 2.0?
Let's say I have a workspace in the 1.0 version. Now I would like to migrate My-Workspace to the 2.0 version. Below are the steps for the same:
1. Click the 
ellipsis icon in My Workspace. Choose the Duplicate workspace option.
2. This will create a copy of 'My Workspace' named 'My Workspace-Copy'.
3. Next, you can switch to the 2.0 version using the Try new version button and migrate My Workspace-Copy. To know how to migrate, refer to the next section.
Info: As a best practice, migrate the copy of the workspace before migrating the original workspace.
Please note that the sample strategy changes will not be retained, any entities shared with the support will be removed, and the schedules will be paused in the duplicated workspace.
How to migrate workspaces from 1.0 to 2.0?
1. When you open Zoho DataPrep 1.0, the announcement pop-up appears. Click the Explore button. This will take you to new 2.0 version of Zoho DataPrep.
2. You can take a quick product tour and get a walk through of the new version. Once the product tour is completed, click the Workspaces tab from the top bar.
3. Click the To be migrated tab. You will find all the workspaces from your 1.0 version listed.
Note: You can migrate up to three workspaces at once. If you want to migrate more than three workspaces, you can migrate them in batches with three in a batch.
4. Once you choose the Migrate data option, the Migration wizard opens.
Note: You can also migrate workspaces individually by clicking on a particular workspace from the to be migrated list. Choose Workspace
5. In the Choose Workspace section, choose the workspaces that would like to migrate from 1.0 to 2.0 Pipelines. Click Proceed.
User Permissions
6. In the User permissions section, you can choose how you would like to migrate the shared users and groups in the workspaces with the below options. We have removed dataset as an entity in DataPrep and have simplified the user roles, hence this step is required to map your existing users to their new roles in the 2.0 workspaces.
a) Retain all users and groups sharing - If you select this option, the shared users and groups in the workspace level will be retained. However, the following roles are no longer supported in 2.0 and will be mapped to an equivalent role.
-
Workspace admin
-
Workspace level data consumer
-
Dataset level editor
-
Dataset level data consumer
Here's the mapping of the 1.0 shared roles and their equivalent roles in DataPrep 2.0
|
User role in DataPrep 1.0
|
User role in DataPrep 2.0
|
|
Workspace admin
|
Workspace shared user
|
|
Workspace level data consumer
|
Workspace shared user
|
|
Dataset level data consumer
|
Pipeline shared user
|
|
Dataset level data editor
|
Pipeline shared user
|
Let's look into a couple of examples to understand this better.
Example 1: Let's say you have shared a workspace with User A in the data consumer role in 1.0 version. Next, you migrate this particular workspace, and choose the Retain all users and group sharing option. Now when you see in the 2.0 version, the workspace will still be shared to User A but in the Workspace shared user role. You can view the shared entities and their roles in the Settings page under the User Management tabs. Click here to know more.
Example 2: Let's say you have shared a dataset with User A in the data editor role in 1.0 version. Next, you migrate the workspace with this dataset and choose the Retain all users and group sharing option. Please note all datasets will be created as pipelines in 2.0 when you migrate. Now when you see in the 2.0 version, the dataset or pipeline will still be shared to User A but in the Pipeline shared user role. You can view the shared entities and their roles in the Settings page under the User Management tabs. Click here to know more.
b) Remove editor and data consumer users and group sharing - This option removes the editor and data consumer users and group sharing in the dataset and workspaces since they are no longer supported. However, you can manually share the required workspace or pipeline with users after migration.
Here's the list of user roles that will be removed:
-
Dataset level consumers
-
Dataset level editors
-
Workspace level data consumers
c) Remove all users and groups sharing - This option removes all shared users and groups from the workspaces. Once the migration is complete, the workspaces and pipelines can be manually shared with the users and groups.
7. After choosing the required option in the User permissions section, click Proceed.
Pipeline Configuration
8. In the Pipeline configuration section, choose how you would like to migrate your datasets to pipelines using the below options
a) Create pipelines for each group of related datasets in each workspace - This option creates separate pipelines for each group of related datasets (joined, pivoted, unpivoted, appended and derived datasets). Separate pipelines will be created for individual datasets in their respective workspaces.
Example: Let's say you have a workspace in the 1.0 version. You have two datasets A and B and combined them using the Join transform. This would have created another dataset C. You also have a couple of other datasets D and E. Now when you migrate this workspace using the Create pipelines for each group of related datasets in each workspace option, one pipeline will be created for datasets A, B and C. One pipeline for the datasets D and E each will be created.
b) Create a single pipeline for all the datasets in each workspace - This option adds all the datasets to a single pipeline in their respective workspaces. All the related and individual datasets will be migrated to the same pipeline in their workspaces.
Example: Let's say you have a workspace in the 1.0 version. You have two datasets A and B and combined them using the Join transform. This would have created another dataset C. You also have a couple of other datasets D and E. Now when you migrate this workspace using the Create a single pipeline for all the datasets in each workspace option, one pipeline will be created for all datasets A, B, C, D and E.
You can also customize how the datasets will be grouped into pipelines in the pipeline summary screen; you can move a dataset from one pipeline to another using the move to option.
Pipeline summary
9. In the Pipeline summary section, you can see the overview of pipelines that will be created, the import and export schedule configuration in the 1.0 version, associated workspace and the option to re-configure the old schedules.
Note:
1. The import and export schedules of the datasets will not be migrated. Please make sure you reconfigure the schedules once the datasets are added to the pipeline.
2. Processing history, Operations history of the datasets will not be migrated, such details for pipelines will be captured in Jobs.
Pipelines - This section displays the pipelines to be created and the datasets under each pipeline. You can also rename the pipeline names using the ellipses icon.
Old import schedule - This section shows the old import schedule configuration.
Old export schedule - This section shows the old export schedule configuration.
Workspace associated - This lists the workspaces associated with each dataset.
Configuration - This section allows you to configure the pipelines and schedules.
Move to - Using the Move to option, you can move a particular dataset to another pipeline or a new pipeline if you so choose. When you move a dataset, all related datasets will also be moved along with the selected dataset, such as parent/child datasets created when performing joins, appends, pivots, and so on.
You can create a new pipeline following the below steps, if needed:
-
Click the Move to option displayed for the corresponding dataset and select the "+ New pipeline" option.
-
Provide a pipeline name. Now, a new pipeline will be created along with the selected dataset.
-
This newly created pipeline will be listed whenever you click the Move to option. You can now select and move other datasets into this pipeline.
Configure schedule - You can configure schedules for the pipeline using this option. Provide the details, such as the Repeat method, frequency, etc., and click Save. Click here to know more about Schedules.
10. After you have reviewed all the dataset grouping into pipelines, schedules for the pipelines, click Migrate to start the migration process. Once the migration is complete, you will be taken to the To be Migrated tab. This will show you the migration status, workspace names, associated pipelines and Tags(if any). You can click to open the workspace, view your pipelines, and start working with them seamlessly.
When does a migration fail?
Migrating data from 1.0 to 2.0 may fail if there are any errors in the datasets or if there is a need to re-authenticate. Taking over a schedule of a user who is no longer part of the organization or inactive is called Re-authentication. A schedule needs to be re-authenticated if any of the following conditions are true:
- A user who has configured a schedule is removed from the organization
- A user who has configured a schedule is inactive
- A connection used is either deleted or no longer with the user.
Note: If the migration fails due to any errors in datasets, you can switch to the 1.0 version, fix the errors and then migrate your data.
How to re-authenticate schedules in 1.0?
When the migration fails throwing the below error, you can follow the below steps to re-authenticate your schedule.
You can click the the Re-authenticate option from any of the following places:
1. Click the Settings icon from the top-right corner and go to the Schedules tab. The Re-authenticate option appears on the schedule that has failed either because the schedule creator is deactivated or removed from the organization, or the connection used is deleted or no longer shared with the user.
2. Open the required dataset and click the Export option from the top-right corner of the DataPrep Studio page and choose the Schedule export option. The Re-authenticate option appears on the schedule that has failed either because the schedule creator is deactivated or removed from the organization, or the connection used is deleted or no longer shared with the user.
3. Open the required dataset and click the Ruleset icon 
and then click the Data source configuration icon. The Re-authenticate option appears on the schedule that has failed either because the schedule creator is deactivated or removed from the organization, or the connection used is deleted or no longer shared with the user.
Once re-authenticated, you can proceed to migrating your data from 1.0 to 2.0 seamlessly.
FAQs
1. Who needs to migrate from 1.0 to 2.0?
All users who are on the 1.0 version of Zoho DataPrep need to migrate their workspaces to 2.0. This would be all standalone DataPrep customers who started using Zoho DataPrep before Sep 1, 2024. Also for Zoho One customers who were using DataPrep before Sep 12th.
2. Which user roles have the privilege to migrate data?
Only the account admin and organization admins can migrate data.
3. What happens if I don't migrate?
You can still keep working with the Zoho DataPrep 1.0 version, your workspaces will not be affected immediately. However with the GA launch of 2.0, we are deprecating the 1.0 version and will be discontinued in about 6 months. (Final date will be announced soon to existing users of 1.0)
4. Will I loose any data while migrating from Zoho DataPrep 1.0 to 2.0?
No, you will not lose any data during migration. However, you can also take a backup of your data before migrating.
5. How to take back up before migrating data from the 1.0 version to 2.0 version?
Let's say I have a workspace in the 1.0 version. Now I would like to migrate My-Workspace to the 2.0 version. Below are the steps for the same:
1. Click the 
ellipsis icon in My Workspace. Choose the Duplicate workspace option.
2. This will create a copy of 'My Workspace' named 'My Workspace-Copy'.
3. Next, you can switch to the 2.0 version using the Try new version button and migrate My Workspace-Copy. To know how to migrate, refer to the next section.
Info: As a best practice, migrate the copy of the workspace before migrating the original workspace.
Please note that the sample strategy changes will not be retained, any entities shared with the support will be removed, and the schedules will be paused in the duplicated workspace.
6. Are there any elements that will not be migrated?
The following elements will be excluded in migration:
-
The import and export schedules (replaced with pipeline schedules)
-
Sync status
-
Operations history - This is replaced with Pipeline Jobs in 2.0, however the historical log of operations on a dataset will not be carried forward.
-
Processing history of the datasets - This is replaced with Pipeline Jobs in 2.0, however the historical copies of previous processed datasets and the logs will be removed.
-
Datasets that are in trash, you can restore from trash if you want these datasets to included in the migration.
7. What happens to the schedules that I have configured in the old UI?
You can re-configure your import and export schedules in the Pipeline summary section of the migration wizard. This way, you can still have your schedules running right after the migration.
8. What are the new user roles supported in the new 2.0 version?
The following user roles are supported in DataPrep 2.0
Pipeline shared user
Workspace shared user
Account admin
Organization admin
9. What are the user roles removed in the new 2.0 version?
Below are the user roles removed in DataPrep 2.0:
Workspace admin
Workspace level data consumer
Dataset level editor
Dataset level data consumer
10. What happens to the deprecated user roles and groups from 1.0 when migrated to 2.0?
You will be given the below three options on how to migrate the deprecated user roles and groups
Retain all users and group sharing - This option retains the shared users and groups in the workspace level. The user roles that are no longer supported in the 2.0 version will by mapped to an equivalent after migration.
Remove editor and data consumer users and group sharing - This option removes the editor and data consumer users and group sharing in the dataset and workspaces since they are no longer supported.
Remove all users and groups sharing - This option removes all shared users and groups from the workspaces.
11. If I have two related datasets in a workspace shared to different users, how will the pipeline in 2.0 be shared?
Datasets will be grouped into pipelines in the 2.0 version. So the pipeline with these datasets will be shared with both the shared users if you choose to Retain all users and groups sharing while migrating.
12. If I migrate only specific datasets in a workspace, can I still access the remaining datasets in the 1.0 UI?
Partial migration of a workspace is not supported. If you do not select a specific dataset while migrating that particular dataset will be deleted from 1.0 and will not be accessible anymore. So make sure you include all datasets in a workspace while migrating if you want to retain them in 2.0
13. After migration, can I still access the workspace in the 1.0 version?
No, once migrated the workspaces will no longer be available in the 1.0 version.
14. What are the settings that will be synced in 1.0 and 2.0?
All the below settings will be in sync among the 1.0 and 2.0 versions of DataPrep. Any changes made in the 1.0 or 2.0 will be automatically updated in both versions
Organization settings
Manage subscription
User Management
Feature control
Compliance
Notifications
Connections
Databridge
Manage Privacy
Custom Data type
15. When does a migration fail?
Migrating data from 1.0 to 2.0 may fail if there are any errors in the datasets or if there is a need to re-authenticate. Taking over a schedule of a user who is no longer part of the organization or inactive is called Re-authentication. A schedule needs to be re-authenticated if any of the following conditions are true:
A user who has configured a schedule is removed from the organization
A user who has configured a schedule is inactive
A connection used is either deleted or no longer with the user.
Click here to know how to re-authenticate schedules in 1.0.
Access your files securely from anywhere
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
Zoho DataPrep Personalized Demo
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
New to Zoho Writer?
Create. Review. Publish.
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.
New to Zoho Survey?
Zoho Sheet Resources
Zoho Forms Resources
New to Zoho Sign?
Zoho Sign Resources
Sign, Paperless!
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho ZeptoMail?
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
New to Bigin?
Related Articles
Data migration for Zoho Creator using DataPrep
Zoho DataPrep is now integrated with Creator using Zoho Creator connector. The forms in Zoho Creator are used to collect and store data, serving as the main point of interaction between the created application and users. Zoho DataPrep allows you to ...Zoho DataPrep - FAQs
1. What is Zoho DataPrep? Zoho DataPrep is an advanced self-service data preparation tool that helps organizations model, cleanse, prepare, enrich and organize large volumes of data from multiple data sources to serve data analytics and data ...Data preparation for Zoho Creator using DataPrep
Zoho DataPrep is now integrated with Creator using Zoho Creator connector. The forms in Zoho Creator are used to collect and store data, serving as the main point of interaction between the created application and users. Zoho DataPrep allows you to ...Data backup for Zoho Creator using DataPrep
Zoho DataPrep is now integrated with Creator using Zoho Creator connector. The forms in Zoho Creator are used to collect and store data, serving as the main point of interaction between the created application and users. Zoho DataPrep allows you to ...Data sync for Zoho Creator using DataPrep
Zoho DataPrep is now integrated with Creator using Zoho Creator connector. The forms in Zoho Creator are used to collect and store data, serving as the main point of interaction between the created application and users. Zoho DataPrep allows you to ...
New to Zoho LandingPage?
Zoho LandingPage Resources