Migrate from KulaHub to Pipedrive

KulaHub contacts map 1:1 to Pipedrive People. Every standard field (name, email, phone, address, job title) maps directly. We use the contact's email address as the dedupe key during import. Any contact that originated from a KulaHub form submission carries its form-field data into custom fields on the Pipedrive Person record, or into standard fields where field types match.

KulaHub has no separate Company or Account object. We derive Pipedrive Organizations by extracting the company_name field from KulaHub contacts, deduplicating by name, and creating one Organization per unique company. Contacts then link to their Organization via a lookup after Organization records are established. If KulaHub contacts contain a domain field, we use it to group contacts under the same Organization.

KulaHub does not have a Deals object, so all pipeline data must be created from scratch in Pipedrive. We work with the customer's RevOps lead during scoping to define the Pipeline name, stage names, stage probabilities, and any custom deal fields. We then create the Pipeline and Stages via Pipedrive's API before any deal records are imported. Deals can optionally be back-populated from any deal-related data stored in KulaHub custom fields or notes.

KulaHub call logs map to Pipedrive Activity records with type = call. Call duration, disposition, and any notes stored in KulaHub migrate to Pipedrive Activity fields. We set the activity's Person link to the migrated contact. Activities are loaded in chronological order by timestamp to preserve the timeline.

KulaHub email engagements map to Pipedrive Activity records with type = email. Subject, body content, and send timestamp transfer. Whether the email was sent, received, or logged manually in KulaHub is captured in a custom Activity field on the Pipedrive record. The Person link resolves via email-address match against migrated contacts.

KulaHub meeting logs map to Pipedrive Activities with date, duration, and title preserved. Attendee information is stored as notes on the Activity record. We link the Activity to the relevant Person in Pipedrive. Any meeting location or video call URL stored in KulaHub migrates as a note on the Activity.

KulaHub tasks and reminders map to Pipedrive Activities with type = task. Status (open, completed), due date, assigned user, and task body migrate. We resolve KulaHub task owners against the destination user list by email match; any unresolved owners are held for the customer admin to map before the task phase runs.

KulaHub email campaign sends, opens, clicks, and unsubscribes are extracted as engagement records. We load them as Pipedrive Activities with type = email, tagged with a custom campaign identifier field. Open and click events from KulaHub tracking are logged as separate Activities with a subtype field to preserve engagement detail.

KulaHub stores email unsubscribe states and GDPR preference flags per contact. We export these as custom fields on the Pipedrive Person record (has_unsubscribed = true/false, gdpr_consent_date if available). The customer should configure Pipedrive's email deliverability settings to respect the HasOptedOutOfEmail-equivalent flag after migration, and should run a suppression-list audit before launching email campaigns.

KulaHub documents attached to contacts are extracted as binary blobs and re-uploaded via Pipedrive's Files API, linked to the corresponding Person record via file-entity association. We preserve the original filename and, where available, the upload timestamp. Attachments that cannot be extracted (e.g. restricted by KulaHub) are logged in the reconciliation report.

KulaHub users appear in activity logs and task assignments. We export the full user list first and match by email address against the destination Pipedrive user directory. Any KulaHub user without a matching Pipedrive user goes to a reconciliation queue for the customer admin to provision before records that reference those users are loaded.

KulaHub exports system activity reports and CRM activity reports. We include these in the scope as reference data so that reporting context is not lost. Pipedrive has its own built-in reporting engine and does not accept report schema imports; we deliver a written mapping of which Pipedrive Reports replace each KulaHub report for the customer admin to configure post-migration.