Migrate from Kuverto to Pipedrive

If Kuverto has been syncing CRM data from another platform or if contact records exist in a Kuverto-connected system, we migrate them as Pipedrive Person records. The mapping resolves email address as the dedupe key. Name, phone, address, and custom fields map by type: text to text, date to date, picklist to picklist. Kuverto does not natively store People data, so this migration assumes the source CRM data is extracted via Kuverto's integration connections or exported directly before migration scoping.

HubSpot Companies, Salesforce Accounts, or equivalent CRM organization records map to Pipedrive Organization. Organization is created before Person import so that the Person-Organization relationship is satisfied at insert time. Domain-based deduplication is applied if the source uses domain fields.

Deals and Opportunities from a Kuverto-connected CRM map to Pipedrive Deal. The source pipeline and stage map to a Pipedrive Pipeline and Stage via the mapping workbook. Deal value, expected close date, owner, and custom fields migrate directly. Pipedrive does not enforce the same stage probability enforcement as Salesforce; we configure StageProbability on each Stage during Pipedrive setup.

Kuverto agent definitions (system prompt, instructions, memory settings, model, tool permissions) are exported as structured JSON and YAML documentation. We attach this documentation to the most relevant Pipedrive Person or Organization record as a Note, and create custom fields (e.g., kuvo_agent_name__c, kuvo_system_prompt__c) to capture the agent reference and version. Kuverto agents cannot run inside Pipedrive; the documentation serves as the specification for rebuilding equivalent automation logic in Pipedrive Workflow Automation.

Kuverto workflows define trigger conditions and sequential LLM-prompted steps. We extract every active workflow: trigger type, step sequence, branching logic, integration calls, and AO consumption estimate. Pipedrive Workflow Automation uses a trigger-condition-action model that does not natively support LLM prompting. We deliver a written Workflow Inventory document mapping each Kuverto workflow to a recommended Pipedrive Workflow Automation configuration and noting the functional gaps the admin must address during rebuild.

Kuverto maintains OAuth tokens and API keys for connected platforms (CRM, email, calendar, helpdesk, payment). These credentials are scoped to Kuverto's environment and are not portable. We inventory every Kuverto integration during discovery and produce a Re-authentication Checklist organized by integration type, covering OAuth re-consent flows, API key replacement, webhook re-registration, and trigger validation in Pipedrive.

Kuverto custom tools include API endpoint specifications, parameter schemas, and response parsing logic. We export tool definitions as structured documentation. Pipedrive does not have a native equivalent to custom tool definitions; tools become API-based custom integrations or are documented as gap items in the Workflow Inventory requiring manual replacement in Pipedrive Workflow Automation or Smart Campaigns.

Agent conversation and execution history in Kuverto are ephemeral operational outputs stored by the platform. They are not configuration data and cannot be exported via Kuverto's public-facing interface. We advise customers to export any required run reports from Kuverto before the migration window if historical agent output is business-critical. Pipedrive's native activity timeline is the destination for forward-looking engagement records.

Kuverto workspace roles (editor, viewer, integration manager) map to Pipedrive User roles and permission sets. Admin users in Kuverto map to Pipedrive Admin users; non-admin roles map to Standard User permission sets. We resolve by email match against the destination Pipedrive User table. Any Kuverto workspace member without a matching Pipedrive User is held in the reconciliation queue for the customer's admin to provision before record import.

If engagement records (calls, emails, meetings, tasks) exist in a Kuverto-connected CRM, they migrate to Pipedrive Activity records. Calls map to Activity with type=Call and call disposition in custom fields; emails map to type=Email; meetings map to type=Meeting with attendees; tasks map to type=Task with Status and Priority. Pipedrive's Search API burst limit (10 req/2s regardless of plan) constrains engagement extraction from connected CRMs during the migration window.