Skip to main content

Tools 6.0 Curate Migration FAQs

What happens to my existing project data in the new Curate page in Tools 6.0?

When you move to the new Curate in Tools 6.0, no data is lost. All existing projects, Source Data Files, and Sample Lists are retained and remain available.

During the migration, new indexing metadata is added automatically. Any existing File Lists are converted into Data Sets, and additional Data Sets may be created to organize the relationship between Source Data Files and Sample Lists.

What is a Data Set?

A Data Set is a group of Source Data Files that are intended to be used together to train and test AI models.

Each Data Set shares a common inference target, such as a class or value label. Source Data Files are grouped into Data Sets, and Sample Lists are created within those Data Sets.

What are the benefits of the new Curate workflow in Tools 6.0?

The new Curate workflow in Tools 6.0 simplifies the process of converting raw data files into Sample Lists through clear, step-by-step guidance.

It introduces Data Sets as a structured layer for organizing files and adds capabilities such as generating linked training and test lists, controlling data channel usage, and other advanced data preparation features.

Can I revert from the new Curate in Tools 6.0 to an earlier version?

No. The new Curate in Tools 6.0 introduces a data structure that is not compatible with earlier Curate versions.

Earlier Curate versions will be deprecated in March 2026 and will no longer be available.

What happens if a project shared with me is still using an older Curate version?

In the new Curate in Tools 6.0, you can view and use projects created in Curate with Tools 5.6 that are shared with you.

Some Curate features, such as random subsetting or copying Sample Lists, may be limited. However, using these Sample Lists in Explore, Test, and Optimize workflows—and reviewing all resulting models and test results—is fully supported.

For continued use of the new Curate features, the project owner should migrate the project when feasible.