Migrate from ConSol to Pipedrive

ConSol contact records map 1:1 to Pipedrive Person records. Standard fields including name, email, phone, job title, address, and owner are transferred directly. For ConSol contacts linked to multiple companies, the primary organization maps to the main Organization field, and any secondary organizations use Pipedrive's secondary organization link to maintain the association without data duplication.

ConSol company records map to Pipedrive Organization objects. Core fields including company name, domain, industry, employee count, and address information transfer directly. Parent-company hierarchies in ConSol map to Pipedrive's Organization hierarchy where the structure is supported, or are flagged for manual configuration post-migration to ensure proper organizational relationships are maintained in the target system.

ConSol tickets and service requests are not Pipedrive Deals — they are activity logs. We convert them to Pipedrive Notes attached to the related Person or Organization, preserving the original request description, status, and timestamps. If the ticket represents a billable service engagement, it may map to a Deal depending on your ConSol usage pattern.

ConSol deal records (if your ConSol configuration includes a sales CRM module) map directly to Pipedrive Deals. Deal name, value, stage, expected close date, owner, and pipeline association transfer. Pipeline stages in ConSol map to Pipedrive stage values within your target pipeline.

ConSol engagement logs (calls, emails, meetings, tasks) map to Pipedrive Activities with the original timestamp, owner, and type preserved. Activity type (call, email, meeting) is set as the Pipedrive Activity type field so filters and dashboards reflect the original interaction category.

ConSol notes and document attachments link to the corresponding Person, Organization, or Deal record in Pipedrive. Rich-text formatting is preserved as-is during transfer. Inline images embedded in ConSol notes are extracted, downloaded, and re-uploaded as Pipedrive file attachments linked to the parent record, maintaining visual context within the migrated data.

ConSol SLA response times, resolution times, breach flags, and escalation status have no Pipedrive equivalent. These migrate as custom fields (e.g., SLA_Response_Date__c, SLA_Breach__c, SLA_Escalation_Level__c) on the relevant Pipedrive record. Pipedrive will not enforce or recalculate these values — they serve as reference data for reporting.

ConSol projects and assets do not map to a Pipedrive object. We migrate project names, asset IDs, and key project status fields as custom fields on the related Organization or Deal record. Deep project hierarchies require post-migration review and manual structuring in Pipedrive.

ConSol custom fields on contacts, companies, or deals that do not match Pipedrive's default field set require a corresponding Pipedrive custom field to be created before migration. FlitStack AI delivers a custom field creation plan specifying field name, type (text, number, date, picklist, etc.), and which Pipedrive object each field belongs to.

ConSol users, agents, and technicians are resolved to Pipedrive users by email address match. ConSol owner IDs that have no matching Pipedrive user email are flagged before migration — teams must provision Pipedrive accounts for those users or assign a fallback owner before the migration run. No record migrates without a valid Pipedrive owner.

ConSol workflows, escalation matrices, SLA rules, and multi-step case automations have no equivalent in Pipedrive's automation engine. We export ConSol workflow definitions as a structured reference document so your Pipedrive admin can rebuild equivalent automations in Pipedrive's workflow builder after migration.

ConSol file attachments linked to contacts, companies, or tickets are re-uploaded to Pipedrive as Files attached to the corresponding Person, Organization, or Deal. File size limits per Pipedrive plan apply (Pipedrive Essential: 5GB/user, Advanced: 10GB/user). ConSol version history is not transferred — the latest version of each file migrates.