Best Practices for Migration Projects
As a data owner, when you register raw assets with the platform, our recommended best practices include:
Create a separate dataset for the raw assets.
Mark datasets that contain raw assets as restricted. Mark datasets that contain the masked assets as unrestricted and made available for data consumers to request for use in a consumption project.
Use a different connection for the raw and masked assets.
Note
You may not reuse a connection that you previously used with another migration project.
The platform ensures that you only select and include raw assets within a migration project. Masked assets cannot be masked again, nor can they be added to a migration project.
Use only consistent numeric or text regular expression transformation types for data that you wish to allow a data consumer to reverse to its original value, according to their request and applicable policy. Other transformation types (such as Constant Text Value or Date Generalization) will not allow data to be reversed. The platform will return other transformation types in their transformed form, rather than the original values. For example, if Constant Text Value is the applied transformation type, the platform will return the constant text.