> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/crm/pipedrive/migrating-from-pipedrive-legacy-source.md).
# Migrating from Pipedrive legacy source
### Why you need to migrate
The legacy Pipedrive source in Coupler.io is built on **Pipedrive API v1**, which Pipedrive deprecated last year. Since v1 is no longer officially supported, it can be sunset by Pipedrive at any time without advance notice — which would break your existing exports without warning.
The new Pipedrive source uses **API v2** (Pipedrive's current, supported API) wherever v2 endpoints are available. We strongly recommend starting your migration as soon as possible to avoid any disruption to your data flows.
### How to check if you use legacy Pipedrive source?
Use search on Data flows list by "Pipedrive (legacy)" keyword - found data flows use legacy source:
During editing of data flow - you can navigate to Sources summary page and review type of source - if you see Pipedrive (legacy) - it is source you need to migrate.
### What's different in the new source
**1. Flatter data structure**\
The old source returned related objects (like the full person or organization record) nested inside a deal. The new source only returns the **ID** of related records, not the full embedded object.
To rebuild those relationships in your export, you have two options:
* Use the **JOIN** option in Coupler.io to combine data from multiple entities (e.g., Deals + Persons) into one flow.
* Use one of our **prepared** [**dataset**](https://app.coupler.io/app/dataflows/new?template_modal=1) **or** [**dashboard**](https://app.coupler.io/app/templates) **templates**, which are already updated to work with the new source's structure.
**2. Incremental fetching**\
The new source supports incremental data fetching, so it handles large data volumes more efficiently than a full re-fetch each time.
**3. Filters and column picker**\
Filters are available in the new source, just as they were in the legacy one. Column picker not added, as new source build to handle large amounts of data. You can limit columns you don't need on **Data set** step.
**4. New entity: Users**\
The new source adds a **Users** entity, which wasn't available before.
**5. Column names match the Pipedrive UI**\
In the legacy source, some columns used internal API field names. In the new source, all column names match exactly what you see in the Pipedrive UI, making it much easier to identify the right fields.
### How to migrate
#### Use [**dataset**](https://app.coupler.io/app/dataflows/new?template_modal=1) **or** [**dashboard**](https://app.coupler.io/app/templates) templates
If you used built-in Coupler.io templates and did not apply custom changes - setup needed one from scratch - it will be the easiest way.
#### Replace source in existing data flow
1. Edit you data flow.
2. Add Pipedrive source.
3. Connect your Pipedrive account. (new source requires new connection)
4. Rebuild any relationships you relied on previously using the **JOIN** option.
5. Review column names (as new source has names from Pipedrive UI) and rename columns if needed.
6. Once on preview you see needed output - disable old source and use new one as data set to share in your destination.
#### Create new data flow from scratch
1. Create a new data flow and select the **Pipedrive source**.
2. Connect your Pipedrive account. (new source requires new connection)
3. Rebuild any relationships you relied on previously using the **JOIN** option.
4. Review column names (as new source has names from Pipedrive UI) and rename columns if needed.
5. Run a test export and compare the output against your legacy flow before switching production processes over.
6. Once you've confirmed the new flow works as expected, delete the legacy data flow or disable sources in it and disable schedule.
### Need help?
If you run into any issues while migrating, reach out to our support team - we're happy to help you map your existing flow to the new source.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.coupler.io/sources/category/crm/pipedrive/migrating-from-pipedrive-legacy-source.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.