Migrate from Groundhogg to Pipedrive

Groundhogg Contacts map to Pipedrive Person records. Standard fields (email, first_name, last_name, phone, address) map directly to Pipedrive Person fields. Custom fields on the Groundhogg contact export map to Pipedrive custom person fields; we create the Pipedrive field first, then import contacts with the custom property values. Groundhogg's primary contact flag maps to the first email address in Pipedrive's email array.

Groundhogg Companies (Plus tier and above) map to Pipedrive Organizations. We export the company name, address, phone, and domain, then create the Organization in Pipedrive before importing related People so the Person-Organization lookup is satisfied at insert time. Groundhogg's company-contact relationship migrates as a Person-Organization link in Pipedrive.

Groundhogg Deals and Pipeline Stages (Pro tier only) map to Pipedrive Deals and Stages. We export the deal title, value, stage name, and expected close date, then configure the Pipedrive Deal pipeline with stages named and ordered to match Groundhogg's stage sequence. Pipeline visual layout does not migrate; we document stage names and stage order during scoping for the Pipedrive admin to configure manually.

Groundhogg tags are a flat taxonomy stored as an array per contact. We export all distinct tag values and map them to Pipedrive Labels (for classification) or create Pipedrive person fields of type select or checkbox if the customer prefers structured filtering over label taxonomy. Tag hierarchy information does not exist in Groundhogg and has no mapping in Pipedrive.

Groundhogg contact custom properties export with their field type (text, number, date, dropdown, checkbox). We map each to a corresponding Pipedrive custom field: text to VARCHAR, number to INT or DECIMAL, date to DATE, dropdown to SELECT, and multi-checkbox to VARCHAR with comma-separated values. Pipedrive imposes a 200-character limit per custom field value which we check during the transform phase.

Groundhogg stores record ownership as WordPress user IDs. We export WP user email addresses during discovery and use email as the matching key against Pipedrive Users. Any Groundhogg Owner without a matching Pipedrive User is held in a reconciliation queue; the customer provisions the missing Pipedrive User before the production migration phase begins. This is a blocking dependency for record import because Pipedrive requires OwnerId on Deal.

Groundhogg activity log entries (email opened, link clicked, form submitted, tag applied, tag removed) export as timestamped records per contact. We create Pipedrive Activity entries with the corresponding activity type (email, call, note, or meeting) and set the ActivityDate to the original Groundhogg timestamp so the timeline order is preserved. The activity description carries the full Groundhogg activity type and metadata.

Groundhogg contact-level notes migrate to Pipedrive Notes linked to the corresponding Person record. We preserve the original timestamp, author attribution (resolved via the WP user email mapping), and note body. Rich text formatting in Groundhogg notes may require normalization to Pipedrive's plain-text or Markdown-compatible format.

Groundhogg broadcast emails (Pro tier) are exported with subject line, send date, and recipient count metadata. Pipedrive has no broadcast object, so we deliver a written broadcast inventory CSV that the customer can reference for campaign audit purposes. Recipients who received broadcasts are not duplicated as discrete objects in Pipedrive; their contact record status reflects their enrollment through activity history.

Groundhogg Flows cannot be exported as reusable automation logic via the REST API. We export the trigger type, step count, step names, and conditional branches as a written Flow Audit document delivered to the customer's admin before cutover. The admin rebuilds Flows in Pipedrive's automation rules or in a connected automation tool (Zapier, Make, or native Pipedrive automation). This is a manual rebuild scope, not a data migration deliverable.

Groundhogg Tracks (Agency tier visual funnels) are not exportable as objects. We document the funnel steps, entry trigger, exit conditions, and downstream actions during scoping and deliver this as a funnel audit CSV. The admin rebuilds the funnel logic in Pipedrive's deal stage automation or an external marketing automation tool. Track rebuild is outside the migration scope.