How can I structure a data mapping document to ensure custom fields transfer seamlessly from Pipedrive to Salesforce without breaking historical reporting?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How can I structure a data mapping document to ensure custom fields transfer seamlessly from Pipedrive to Salesforce without breaking historical reporting?
1 real search · 1 real-search pass
Pipedrive API custom fields field keys metadata Salesforce custom fields field history tracking reports migration historical dataGoogle ↗
OBSERVEDReason
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model). 1 of 1 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT1 real searches · gpt-6
Pipedrive API custom fields field keys metadata Salesforce custom fields field history tracking reports migration historical data Google ↗
- Custom fields · pipedrive.readme.io
- Custom fields - Knowledge Base · support.pipedrive.com
- Field History Tracking · help.salesforce.com
- Field History Tracking Overview · help.salesforce.com