> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/data-migrator/templates/template-designer/applying-data-masking-to-fields.md).
# Applying Data Masking to Fields
##  Overview
This article explains what Data Masking is and how to apply it to specific fields to prevent sensitive data from being migrated to the target organization. Data Masking is useful in sandbox or testing environments where real customer information should never be exposed. By selectively masking fields, teams can maintain realistic data structures for validation while ensuring compliance with data privacy requirements.
### How Data Masking Works
Data Masking replaces a field's value with randomized data during a migration. The masking process follows these steps:
1. Records are retrieved from the source org.
2. If data masking is **enabled** for a field, the value is replaced with a randomly generated value of the same field type, with valid formatting.
3. If data masking is **disabled** for a field, the original value remains unchanged.
4. Records with masked fields are deployed to the target org.
{% hint style="info" %}
Masking is performed dynamically during the migration and occurs before data is written to the target environment. For masked fields, the original value is replaced with a randomized value not derived from the source data, so the original value cannot be determined.
{% endhint %}
### Data Mask States
The table below shows the different Data Mask State icons, with an explanation of each.
State
Icon
Description
Unmasked
The source data for this field will be migrated.
Masked
Masked data for this field will be migrated.
Non-Maskable
This field's data can not be masked, and the source data for this field will always be migrated.
## Apply Data Masking
{% stepper %}
{% step %}
### Select Template
1. Click **Templates** from the left sidebar menu.
2. Click the template to add Data Masking to.
{% endstep %}
{% step %}
### Apply Data Masking
1. Click the object to apply Data Masking to.
2. Click the **Eye** icon of the field to mask.
{% hint style="info" %}
See the **Data Mask States** section above for an explanation of each **Eye** icon.
{% endhint %}
3. Click **Add Masking**.
4. Click the **Data Masking Method** dropdown menu.
5. Select the masking method to use.
{% hint style="info" %}
Currently, the only masking method available is **Random**. This method generates random data for the mask during migration.
{% endhint %}
6. Click **Back**. Note that clicking the **X** will discard the Data Mask.
7. The Data Mask State icon shows that the field is now masked.
8. Click **Save** once all Data Masks have been applied.
{% endstep %}
{% step %}
### Remove Data Masking
1. Click the object to remove Data Masking from.
2. Click the **Eye** icon of the field to remove Data Masking.
3. Click the **Remove** icon to the right of the masking method.
4. Click **Back**. Note that clicking the **X** will leave the Data Mask unchanged.
5. The Data Mask State icon shows that the field is now unmasked.
6. Click **Save** once the desired Data Masks have been removed.
{% endstep %}
{% step %}
### Save Template
Once you are done applying or removing Data Masking to fields:
1. Click **Save template** to save your changes.
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flosum.com/data-migrator/templates/template-designer/applying-data-masking-to-fields.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
