Migrate from Launchpad CRM to Pipedrive

Launchpad CRM Clients (job seekers, benefit recipients, program participants) map to Pipedrive Contacts. Contact fields such as name, email, phone, and address migrate directly. The HubSpot-style deduplication pattern (same participant entered in both a client profile and a case record) is resolved at migration time by selecting the most recently updated field value across both record instances and writing a single canonical Contact. We preserve the original Client record ID in a custom field source_client_id__c for audit traceability.

Each Launchpad CRM Case maps to a Pipedrive Deal. The Deal title is constructed from the Client name and Program name for readability. Case status, enrollment date, and outcome fields migrate as custom fields on the Deal. A single Client can have multiple active Cases across different Programs, so the 1:N split from Case to Deal is preserved. We link each Deal to the canonical Contact via Pipedrive's person_id field at migration time.

Launchpad CRM Programs (workforce development, SNAP, TANF, housing, vocational rehabilitation) do not have a direct Pipedrive equivalent. We map Programs to Pipedrive Labels applied to Deals and create a custom field program_type__c to carry the full program taxonomy. If the customer has more than 20 distinct program types, we recommend storing program details in a Pipedrive custom field with a picklist to avoid label proliferation.

Launchpad CRM Service encounters logged against a Case map to Pipedrive Activities. Service type (assessment, counseling session, job placement support, training attendance) determines the Activity type. Each Activity is linked to the parent Deal (from the Case) and the Contact (from the Client). Service date and duration migrate to ActivityDate and duration fields. Service outcome and notes migrate as Activity notes.

Caseworker notes and case commentary migrate to Pipedrive Notes attached to the Contact or Deal. Plain-text notes transfer directly. Notes with structured fields (date, author, category) are parsed and the structured content is written to the Note body with the author and date preserved in Note metadata. Notes are linked to the Contact or Deal via Pipedrive's content_type and content_id fields.

Uploaded files attached to Clients or Cases migrate as Pipedrive Attachments. Document blobs are downloaded from the source export and re-uploaded to the relevant Contact or Deal record. We preserve the original document name and upload date. File-type handling is confirmed during scoping because some government agencies restrict certain file types in cloud-hosted CRMs.

Formal skill assessments or evaluations tied to a Case migrate as a Task-type Activity with the assessment instrument name and completion date in custom fields on the Deal. Assessment scores are stored in a custom field assessment_score__c. If the assessment contains multiple sub-scores, these map to individual custom fields created in Pipedrive during schema configuration.

Launchpad CRM Employer records used in job-placement workflows map to Pipedrive Organizations. The Employer name becomes the Organization name, and employer contact details map to Organization fields. We link the Organization to the Deal via Pipedrive's organization_id field on the Deal record.

Caseworker and staff accounts in Launchpad CRM map to Pipedrive User records. We resolve by matching email address. Any Launchpad CRM User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import continues, because OwnerId references are required on Deals and Activities.

Launchpad CRM custom properties (eligibility flags, compliance codes, funding source identifiers, federal reporting tags) migrate to Pipedrive custom fields of equivalent type. Text properties map to text fields, date properties to date fields, and multi-option properties to picklist or multi-select fields. Pipedrive custom fields are available on all paid plans. We pre-create the destination field schema before any data import to ensure referential integrity during the load phase.

Launchpad CRM program status or employment placement stages do not map 1:1 to Pipedrive's standard deal stages. We create a custom Pipedrive Pipeline with stage names that match the customer's workflow (for example: Intake, Assessment, Training, Job Search, Placement, Retention). Stage probability values migrate from the source system or are set to defaults during pipeline configuration, which the customer's admin approves before migration.