> 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.md).

# Sourcepoint

In July 2025, Didomi and Sourcepoint joined forces to build the future of privacy and to establish itself as the authority on privacy-respecting data collection, utilization, and attribution across all digital platforms and channels.

Our combined teams have been hard at work to create efficient tooling that will allow your organization to migrate its existing configuration from Sourcepoint to the Didomi platform. 

* [Prerequisites for Sourcepoint migration](#prerequisites-for-sourcepoint-migration)
* [Permissions](#permissions)
* [Resources ](#resources)

***

### Prerequisites for Sourcepoint migration

Before your organization migrates its Sourcepoint components and configurations to the Didomi platform it must ensure that it has a signed migration addendum. Once signed, the Didomi team will:

* Create the required link between your Sourcepoint and Didomi accounts that will be used for the migration
* Enable any migration related features in your Sourcepoint account

{% hint style="info" %}
Please reach out to your Sourcepoint representative for any questions regarding the migration.
{% endhint %}

### Permissions

In order to migrate a component 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><th></th></tr></thead><tbody><tr><td><strong>Admin access</strong></td><td></td></tr><tr><td><ul><li>Permission to access the component (e.g. <strong>Vendor List - GDPR</strong>)</li><li><strong>Didomi Migration</strong> permission</li></ul></td><td></td></tr></tbody></table>

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FAuJMZZIoCXlZuyEvHJNB%2FScreenshot_2026-10-19_at_1_49_03%E2%80%AFPM.jpg?alt=media&amp;token=0beaa203-e220-4f9d-ac12-292b68a7c044" alt=""><figcaption></figcaption></figure>

### Resources&#x20;

Below are the current available resources for the Sourcepoint to Didomi migration:

* [Migrate Sourcepoint vendor list](/releases-and-announcements/migrations/sourcepoint/migrate-sourcepoint-vendor-list.md)
* [Migrate Sourcepoint messages](/releases-and-announcements/migrations/sourcepoint/migrate-sourcepoint-messages.md)


---

# 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.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.