Migrate from SimplyConvert to Pipedrive

SimplyConvert's client contact records map directly to Pipedrive Persons. Name, email, phone, address, and job title transfer as standard Pipedrive Person fields. Client notes and bot conversation history migrate as Pipedrive Notes attached to the Person record for full context continuity.

Each SimplyConvert Case maps to one Pipedrive Deal. The case name becomes the Deal name; the matter type, litigation stage, and TDP Quantifier score migrate as custom fields on the Deal. The associated intake contact links via Pipedrive's person_id field on the Deal so the client record is immediately accessible from the deal view.

SimplyConvert's referral tracking includes referring attorney name, firm, co-counsel fee agreements, and referral source channel. These map to Deal custom fields (e.g., Referred_By_Firm__c, Referral_Fee_Agreement__c) and are also logged as Activities on the Deal so referral history surfaces in the timeline without cluttering the primary deal record.

SimplyConvert's standalone referral records represent inbound co-counsel or partner referrals with fee-split metadata. Pipedrive has no referral object, so we transform these into a Deal-scoped Activity with the referral type and fee terms captured as custom fields on the associated case Deal. Duplicate referrals that have no linked case are imported as standalone Activities with no deal association.

Staff notes attached to SimplyConvert client records migrate as Pipedrive Notes on the Person object. Each note preserves its create timestamp in a field (Original_Note_Date__c) as Pipedrive's created_at is immutable. Author attribution resolved by matching creator's email to a Pipedrive user; unmatched authors are recorded as a generic user. The note body transfers and file attachments linked to note are uploaded as Pipedrive attachments on the Person record.

SimplyConvert's document attachments — claim forms, intake documents, correspondence — re-upload to Pipedrive as attachments on the corresponding Deal or Person record. File size limits apply per Pipedrive's storage tier (5GB–unlimited per user). We batch-upload in groups of 50 to stay within rate-limit budgets.

SimplyConvert's mass-tort custom properties have no Pipedrive native equivalent. Each custom property requires a corresponding Pipedrive custom field created on the Deal object before migration begins. Pick-list value properties (e.g., Case_Status__c with values Open, Pending_Investigation, Filed, Settled) require value-by-value mapping to Pipedrive's pick-list options.

SimplyConvert captures the full chatbot conversation at intake as a structured log attached to the client record. This data has no Pipedrive equivalent object, so we transform it into a formatted Note on the Person record — the first line contains a conversation-summary header, followed by the full transcript. Full conversation history is preserved for compliance and audit purposes.

If SimplyConvert uses pipeline terminology for case stages (e.g., Intake, Review, Filed, Settled), we map each stage to a corresponding Pipedrive Pipeline stage. Pipedrive allows multiple pipelines per account — we configure one pipeline per SimplyConvert matter type so stage labels are semantically correct in Pipedrive.

SimplyConvert assigns each case to a staff member or attorney. Pipedrive assigns records to users. We resolve by email match — if the SimplyConvert owner email matches a Pipedrive user account, the record lands with that owner assigned. Unmatched owners are flagged pre-migration so your team can either invite them to Pipedrive or reassign before the migration run.

SimplyConvert's intake forms create custom properties per form — practice-area questions, qualification criteria, financial information. Each intake form field becomes a Pipedrive custom field on the Person (for client-answered questions) or Deal (for matter-specific questions). We deliver a field-mapping matrix before migration showing exactly which form field lands where.

Phone calls, emails, meetings, and tasks logged in SimplyConvert migrate as Pipedrive Activities of the corresponding type (call, email, meeting, task). Each activity links to the Person and optionally to the related Deal via the activity's deal_id field. Original timestamps and assigned users are preserved — user assignment resolved by email match as described above.