How do we get Pipedrive into our reports?

[Tracker]

Most of our company reporting is already built in Amazon Redshift. Product usage and subscription payments are stored there, but the sales team keeps deals, contacts, organizations, and activities in Pipedrive, so we can’t connect the sales pipeline with actual customer revenue. I currently export a CSV once a week, but updated deals sometimes appear as duplicates and the custom fields don’t always arrive in a usable format. What’s a reliable way to move the Pipedrive data into Redshift and keep it synchronized without reloading everything from scratch each time?

 

[Anthem]

Decide what the reports need to show before building the transfer. A table containing only the current state of each deal won’t tell you how long it remained at a particular stage, so retain stage changes and activity timestamps as well. Keep the original Pipedrive IDs for deals, people, and organizations, and define which custom fields should be treated as dates, numbers, or free-form values. That structure will make it much easier to join the CRM records with billing and product data later.

 

[Chillus]

Once the reporting model is clear, weekly CSV exports are a poor fit because changed records need to update the existing rows rather than create new copies. Use an incremental ETL pipeline that loads each Pipedrive entity separately and can preserve flexible custom fields without rebuilding the Redshift schema. You can read how to transfer data from Pipedrive to Redshift here: http://datrise.com/en/pipeline/pipedrive-to-redshift . The approach uses stable IDs for merges and typed landing tables, with flexible values stored in Redshift SUPER columns. Validate the first full load against Pipedrive, then check that later syncs correctly update deals, activities, and stage changes.