---
schema_version: "1"
id: 9acfb770e9e41479fa3147f3b2571ccb2e1f0cae3534a25397b9dc8b51a10f18
title: OFM Data Portability
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/ofm_data_portability.md
canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.ofm_data_portability.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 09f6c676078f7db9bae708e17858f3e4e13bae00518a7c165548bd310facc687
description: Learn how to manage data portability in Outbound Funds Module.
products:
  - Nonprofit
release: "264"
---
# OFM Data Portability

Learn how to manage data portability in Outbound Funds Module.

- **[Data Portability for Your Product](https://help.salesforce.com/s/articleView?id=sfdo.ofm_data_portability.htm&release=264.0.0&type=5)**  
    Learn about data portability for Outbound Funds Module. When your constituents request it, prepare and pack up the data you've received from them so that you can work toward complying with GDPR data portability and export requirements. We offer the following examples of common requests and considerations to help you plan how best to honor constituent requests around data portability. These are only suggestions for your review, and not guaranteed steps for ensuring compliance with any legal rule.

## Data Portability for Your Product

Learn about data portability for Outbound Funds Module. When your constituents request it, prepare and pack up the data you've received from them so that you can work toward complying with GDPR data portability and export requirements. We offer the following examples of common requests and considerations to help you plan how best to honor constituent requests around data portability. These are only suggestions for your review, and not guaranteed steps for ensuring compliance with any legal rule.

Keep in mind that addressing constituent requests, including those provided for under the GDPR, can be challenging. A one-size-fits-all strategy may not always work, and you may need to adjust your approach when balancing organizational needs and legal obligations. For example, if exporting personal data to satisfy a GDPR data portability request may violate someone else’s rights, you might consider narrowing the fields in scope rather than exporting all data. If deleting personal data to satisfy a GDPR erasure request may conflict with other requirements around record preservation, you might consider anonymizing certain fields rather than wholesale deletion.

As always, there are pros and cons to each approach, including legal and business impacts and risks, and you are responsible for your own compliance obligations in your use of the Salesforce Services and Salesforce.org applications. You should work with your advisors, including legal counsel, to determine whether you are covered under a legal requirement, and come up with a compliance plan that’s best for your organization.

Salesforce resources:

- [Data Portability: Give Customers Their Data when They Want It](https://help.salesforce.com/articleview?id=data_portability.htm&type=5)
- [Export Backup Data](https://help.salesforce.com/articleview?id=admin_exportdata.htm&type=5)
- [Export results of SOQL query from workbench](https://help.salesforce.com/articleview?id=000205697&type=1)
- [Export Data with Data Loader](https://developer.salesforce.com/docs/atlas.en-us.208.0.dataloader.meta/dataloader/exporting_data.htm)

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-outbound_funds_module-264-0-0-production-enus/2f847b24-f1f1-4ef3-9181-163efc8e0a07/images/icon_important.png)

Important Remember to review both Salesforce Platform documentation AND Salesforce.org product-specific documentation. In addition to the information in this table, review:

- [Data Export for Sales Cloud](https://help.salesforce.com/articleview?id=data_portability_sales.htm&type=5)
- [Data Export for Salesforce Platform](https://help.salesforce.com/articleview?id=data_portability_platform.htm&type=5)

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
          <colgroup>
            <col style="width:33.33333333333333%">
            <col style="width:33.33333333333333%">
            <col style="width:33.33333333333333%">
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d7209e144">Common Constituent Request</th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d7209e147">Actions to Consider</th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d7209e150">Things to Do</th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="Common Constituent Request" class="slds-cell-wrap" style="vertical-align:top;" headers="d7209e144 ">A constituent is moving out of state and won’t be engaging with your organization anymore. They want to take their information with them.</td>

              <td data-label="Actions to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d7209e147 ">
                <a href="https://help.salesforce.com/articleview?id=exporting_data.htm&amp;type=5&amp;language=en_us" target="_blank">Export Data</a>
              </td>

              <td data-label="Things to Do" class="slds-cell-wrap" style="vertical-align:top;" headers="d7209e150 ">
                <p>Personal data can exist in many different records and fields.</p>
                <p>Consider exporting these records and fields for your client:</p>
                <ul>
                  <li>
                    <p>Contact</p>
                  </li>

                  <li>
                    <p>Tasks</p>
                  </li>

                  <li>
                    <p>Calendar events</p>
                  </li>

                  <li>
                    <p>Personal data in unindexed, free-text fields</p>
                  </li>

                </ul>
                <p>You can find personal data in unindexed fields by exporting the data, and then searching for the information.</p>
                <p>You may also consider exporting:</p>
                <ul>
                  <li>
                    <p>Funding Program</p>
                  </li>

                  <li>
                    <p>Funding Request</p>
                  </li>

                  <li>
                    <p>Funding Request Role</p>
                  </li>

                  <li>
                    <p>Requirement</p>
                  </li>

                  <li>
                    <p>Disbursement</p>
                  </li>

                </ul>
                <p>The export file should be in a structured, commonly used, machine-readable format that is transferable, such as a .csv.</p>
                <p>And if that person no longer wants you to keep the personal data you’ve collected, you can delete it.</p>
                <p style="margin-bottom:0;">If you maintain a Sandbox environment, you may want to refresh the environment afterward to remove that constituent’s data from it, or log into the Sandbox and manually remove the data.</p>
              </td>

            </tr>
            <tr class="">
              <td data-label="Common Constituent Request" class="slds-cell-wrap" style="vertical-align:top;" headers="d7209e144 ">
                <p>An employee is being assigned to a new position.</p>
                <p style="margin-bottom:0;">They ask for the personal data you collected from them.</p>
              </td>

              <td data-label="Actions to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d7209e147 ">
                <a href="https://help.salesforce.com/articleview?id=exporting_data.htm&amp;type=5&amp;language=en_us" target="_blank">Export Data</a>
              </td>

              <td data-label="Things to Do" class="slds-cell-wrap" style="vertical-align:top;" headers="d7209e150 ">
                <p>Personal data can exist in many different records and fields.</p>
                <p>Consider exporting these records and fields for the employee:</p>
                <ul>
                  <li>
                    <p>Contact</p>
                  </li>

                  <li>
                    <p>Tasks</p>
                  </li>

                  <li>
                    <p>Calendar events</p>
                  </li>

                  <li>
                    <p>Personal data in unindexed, free-text fields</p>
                  </li>

                </ul>
                <p>You can find personal data in unindexed fields by exporting the data, and then searching for the information.</p>
                <p>You may also consider exporting:</p>
                <ul>
                  <li>
                    <p>Funding Program</p>
                  </li>

                  <li>
                    <p>Funding Request</p>
                  </li>

                  <li>
                    <p>Funding Request Role</p>
                  </li>

                  <li>
                    <p>Requirement</p>
                  </li>

                  <li>
                    <p>Disbursement</p>
                  </li>

                </ul>
                <p>The export file should be in a structured, commonly used, machine-readable format that is transferable, such as a .csv.</p>
                <p>And if that person no longer wants you to keep the personal data you’ve collected, you can delete it.</p>
                <p style="margin-bottom:0;">If you maintain a Sandbox environment, you may want to refresh the environment afterward to remove that constituent’s data from it, or log into the Sandbox and manually remove the data.</p>
              </td>

            </tr>
          </tbody>
        </table>