> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/releases-and-announcements/migrations/sourcepoint/migrate-sourcepoint-messages.md).

# Migrate Sourcepoint messages

In Sourcepoint, first layer messages and privacy managers (collectively referred to as messages) is the user interface whereby the end-user makes their consent choices.In this article, we will cover:

* [Sourcepoint message migration overview](#sourcepoint-message-migration-overview)
* [Sourcepoint message migration permission(s)](#sourcepoint-message-migration-permission-s)
* [Initiate Sourcepoint message migration](#initiate-sourcepoint-message-migration)
* [Migration status](#migration-status)

***

### Sourcepoint message migration overview

In the Didomi platform, [widgets](https://docs.didomi.io/widgets/manage-widgets.md) serve the same function as Sourcepoint messages. As such, any migrated Sourcepoint first layer message and/or privacy manager will be imported into the widgets section in the Didomi platform.

Each Sourcepoint first layer message and privacy manager is associated with a particular regulation or framework, the following message types can be migrated into Didomi:

<table><thead><tr><th width="215">Regulations/Frameworks</th><th width="160">Device</th><th>Message Type</th></tr></thead><tbody><tr><td>GDPR TCF</td><td>Web/Webview</td><td><ul><li>First Layer Message</li><li>Privacy Manager</li></ul><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Note</strong>: Only the preferences and vendor views of the privacy manager will be migrated into Didomi. Any configured custom views in the privacy manager will not be migrated.</p></div></td></tr><tr><td>GDPR Standard</td><td>Web/Webview</td><td><ul><li>First Layer Message</li><li>Privacy Manager</li></ul><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Note</strong>: Only the preferences and vendor views of the privacy manager will be migrated into Didomi. Any configured custom views in the privacy manager will not be migrated.</p></div></td></tr><tr><td>Global Enterprise</td><td>Web/Webview</td><td><ul><li>First Layer Message</li><li>Privacy Manager</li></ul></td></tr><tr><td>U.S. Multi-State Privacy</td><td>Web/Webview</td><td><ul><li>First Layer Message</li><li>Privacy Manager</li></ul></td></tr></tbody></table>

{% hint style="info" %}
Any messages not in the above table is not available to migrate into the Didomi platform
{% endhint %}

### Sourcepoint message migration permission(s)

In order to migrate a vendor list from Sourcepoint to the Didomi platform, the user in your organization will need to have one of the following permission groupings:

<table data-card-size="large" data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><strong>Admin access</strong></td></tr><tr><td><p></p><ul><li><strong>Campaign Entities</strong> permission</li><li><strong>Didomi Migration</strong> permission</li></ul></td></tr></tbody></table>

### Initiate Sourcepoint message migration

{% hint style="warning" %}
**Note**: Your organization can migrate a Sourcepoint first layer message or privacy manager multiple times into the same Didomi organization. Every time you migrate it will create a duplicate in the Didomi regulation manager.
{% endhint %}

In order to migrate a Sourcepoint vendor list, navigate to the Sourcepoint portal and click **Messages** on the left-hand panel.

Use the subsequent menus to select the type of message you wish to migrate into Didomi.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FeSRmLoB6lgCNStS7DOp6%2FScreenshot%202026-10-20%20at%2011.47.13%E2%80%AFAM.png?alt=media&amp;token=4b6669ef-ef25-4aae-bba3-e3d997319d3a" alt="" width="563"><figcaption></figcaption></figure>

Use the property field in the upper right-hand corner to select a property.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2Fw1cjjw1ozqqAAXRY8372%2FScreen%20Shot%202021-10-27%20at%2012.48.20%20PM.png?alt=media&amp;token=1167a09a-d273-4674-a357-1ba2b003dfda" alt="" width="563"><figcaption></figcaption></figure>

Navigate to the message that should be migrated into the Didomi platform and click the **Migrate to Didomi** icon inline with the message name.&#x20;

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FDcPvhSH03M7NnJe2Pmgo%2FScreenshot%202026-10-20%20at%201.12.28%E2%80%AFPM.png?alt=media&amp;token=280c59bb-ec30-4964-b9a4-a352f690f30c" alt="" width="563"><figcaption></figcaption></figure>

The subsequent modal, indicates the content that will be migrated. Sourcepoint will capture the content of your message(s) via a screenshot, HTML, and CSS, and use these artifacts to reconstruct the message(s) as a Didomi widget.

{% hint style="info" %}
In the case of a first layer message, any privacy manager associated with the first layer message will also be migrated and combined into a singular widget in the Didomi platform.&#x20;
{% endhint %}

Use the **Select Didomi Organization** field in the subsequent modal to select your organization's Didomi account and click **Continue** when finished.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FrZP02Z1LKkstLvsCY096%2FScreenshot_2026-10-26_at_2_16_45%E2%80%AFPM.jpg?alt=media&amp;token=7673589c-11af-4387-8bd8-401d712ed755" alt="" width="563"><figcaption></figcaption></figure>

Review the destination for the message(s) migration and confirm the decision to migrate by selecting **Confirm**.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FSrWBkoL57YE9MdqKsIAm%2FScreenshot_2026-10-26_at_2_23_24%E2%80%AFPM.jpg?alt=media&amp;token=f83cf611-1160-4917-ae17-eae809a4d7ca" alt="" width="563"><figcaption></figcaption></figure>

The subsequent modal will inform your organization of the migration status and any issues that occurred when migrating the message.

{% hint style="info" %}
If your organization receives an error please contact your Sourcepoint representative.
{% endhint %}

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FaltTSJKlncRUONZC0eE1%2FScreenshot%202026-10-26%20at%202.30.17%E2%80%AFPM.png?alt=media&amp;token=e5d94b36-2bbd-42b4-8bb3-600aacd52b8b" alt="" width="563"><figcaption></figcaption></figure>

If the migration was successful overall, the message page will indicate the last migrated date for the message in the **Last Migrated** column.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2F9ApuwRBfqNasX315e6qV%2FScreenshot%202026-10-26%20at%202.33.40%E2%80%AFPM.png?alt=media&amp;token=32476117-0c6b-4817-9c57-f2e54b8fa5f9" alt="" width="563"><figcaption></figcaption></figure>

In your organization's Didomi account, the migrated messages will appear in the widgets section and have all the successfully migrated settings applied.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FDIvUPvZHUxSZutGkW9Br%2FScreenshot%202026-10-26%20at%202.44.29%E2%80%AFPM.png?alt=media&amp;token=1e296e56-424c-4e8d-93b1-373bf6a39d96" alt="" width="563"><figcaption></figcaption></figure>

### Migration status

The migration status for a given first layer message or privacy manager is a manually configured field that enables your organization to visualize and manage the migration process across all of your messages.&#x20;

Select the **Migration Status** field inline with any first layer message or privacy manager to choose from the three available statuses:

* Done
* To Do
* Won't Do

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FnTIRU0GyvRjp7lhiq2EY%2FScreenshot%202026-10-20%20at%2010.50.58%E2%80%AFAM.png?alt=media&amp;token=b09f8f2a-fc76-4e34-889f-990138999573" alt="" width="563"><figcaption></figcaption></figure>


---

# 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.didomi.io/releases-and-announcements/migrations/sourcepoint/migrate-sourcepoint-messages.md?ask=<question>&goal=<user_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.
