Skip to main content

User Guide

Migrating Data

When migrating data, users in your organization will perform the following tasks:

  1. A data owner registers raw assets with the platform.

    Note

    Our recommended best practice is to create a separate dataset for the raw assets and mark it as restricted.

  2. A data guardian approves the raw assets.

  3. The data owner creates and submits a migration project.

  4. A data guardian approves the migration project, and this automatically registers the corresponding masked assets to the data exchange.

  5. The data owner reviews and submits masked assets.

  6. A data guardian approves the masked assets.

  7. A data integration developer executes a data migration pipeline, which references the migration project. This process completes the data migration and transformation of raw assets to masked assets, allowing data consumers to request and access the data.

  8. A data consumer creates a consumption project to request access to the masked assets.

  9. A data guardian approves the consumption project.

  10. The data consumer copies the proxy URL to use in their business intelligence (BI) tool, for example.

In this section: