Migrate from Groundhogg to Twenty CRM

Groundhogg's primary object maps to Twenty CRM's Person record. Standard properties (email, first_name, last_name, phone, postal_address) map to Twenty CRM's standard Person fields. Custom field values migrate as additional properties on the Person record. The contact's primary company link (if set in Groundhogg) maps to the Twenty CRM Organization lookup after Organizations are migrated. WordPress user owner references are remapped to Twenty CRM workspace member emails during import.

Groundhogg Companies map to Twenty CRM Organizations. Company name, address, phone, website, and domain fields migrate directly. Organization records are inserted before Person records so that the organization lookup is satisfied at Person import time. If Groundhogg stores multiple contacts per company, each Person record links to the same Organization after the Organization insert completes.

Groundhogg's flat tag taxonomy has no native Twenty CRM equivalent. During scoping, the customer chooses between migrating tags as Opportunities (one per unique tag with a name-value structure), as a multi-select custom field on Person, or as a flat custom field with comma-separated values. Tags do not carry hierarchy information in Groundhogg, so no nesting logic applies.

Groundhogg custom properties on contacts export with their field types preserved. We map text fields to Twenty CRM text properties, date fields to date properties, checkbox fields to boolean properties, and dropdown or choice fields to select properties. Choice field options are recreated in Twenty CRM's field configuration. Custom field schema is designed in Twenty CRM before any Person data import to avoid type-mismatch errors during insertion.

Groundhogg Flows store multi-step automation logic (trigger, conditions, time delays, actions) that cannot be exported via the REST API. We run a Flow Audit during discovery and produce a written document listing each Flow's trigger type, step count, step names, action types, and conditional logic. This document is the handoff artifact for the customer's admin to rebuild Flows manually in a third-party automation tool (Zapier, Make, or a custom script) or to accept the automation gap in Twenty CRM.

Tracks are a visual funnel-building interface available in Groundhogg's Agency tier. We do not migrate Tracks as discrete objects. We document the funnel stage names, contact counts per stage, and any automation rules attached to track entry or exit. The customer uses this documentation to inform pipeline stage design in Twenty CRM and to rebuild the funnel visualization manually.

Groundhogg broadcast emails carry subject, send date, recipient count, open rate, click rate, and bounce metadata. We export this as a structured metadata report attached to the Person records who received each broadcast. The broadcast HTML content, email templates, and send history do not migrate as sendable email content. Recipients are identifiable in the activity metadata but the email itself is not reconstructed in Twenty CRM.

Groundhogg logs contact activities including email opens, link clicks, form submissions, tag applied or removed, note added, and appointment booked. We export the activity log per contact and create timestamped Activity records in Twenty CRM ordered chronologically. The activity type, timestamp, and any associated metadata (URL clicked, form name, tag name) are preserved. Activity records are inserted after Person and Organization migration so that the Person lookup is satisfied.

Groundhogg contact-level notes migrate as Comment records in Twenty CRM, linked to the corresponding Person. Each Comment preserves the note body text, creation timestamp, and author attribution. Notes authored by a WordPress user are attributed to the matching Twenty CRM workspace member after owner reconciliation.

Groundhogg Deals and Pipeline Stages (available on Pro and above tiers) map to Twenty CRM Opportunities. We export stage names, deal values, and associated contact and company links. Pipeline visual layout and deal probability percentages do not migrate. We deliver a stage name and order document for the customer to configure Opportunity stages in Twenty CRM before migration. Deal notes migrate as Comments attached to the Opportunity.

Groundhogg maps ownership via WordPress user IDs. We export WP user email addresses and match them to Twenty CRM workspace members by email. Any Groundhogg owner without a matching Twenty CRM workspace member is held in a reconciliation queue for the customer's admin to provision before record import resumes. This step gates all subsequent record migration because owner references are required on most object imports.