Migrate from Groundhogg to Nutshell

Groundhogg Contact records map to Nutshell Person objects. The standard contact properties (email, first_name, last_name, phone, address) migrate directly. We use email as the dedupe key during import. Custom meta fields from Groundhogg export as Nutshell custom properties; we match meta field types (text, date, dropdown, checkbox) to Nutshell field types during mapping. Opt-in status (confirmed, unconfirmed, unsubscribed, bounced) migrates to Nutshell's email status fields.

Groundhogg Companies (available on Plus and above) map to Nutshell Company. Company name, address, phone, and domain migrate directly. We link Contacts to Companies during migration by matching the Groundhogg company_id reference to the Nutshell Company ID. If the customer's Groundhogg account is on Basic tier without Companies enabled, contacts with company information stored in custom meta fields are mapped by company name string match to Nutshell Company records created during import.

Groundhogg tags are a flat taxonomy for contact classification. Tags export as a list per contact and apply as Nutshell Tag records linked to each Person. Tag hierarchy is not supported in Groundhogg and does not require transformation. Tags used for lead scoring or segmentation in Groundhogg Flows migrate as tags only; the scoring logic is documented for rebuild in Nutshell's automation layer.

Groundhogg custom fields are stored as contact meta (key-value pairs in the wp_postmeta-style table). We export the full meta schema during scoping, map each meta key to a corresponding Nutshell custom property of matching type (text, number, date, dropdown). Choice and dropdown fields require value mapping where Groundhogg option labels differ from Nutshell dropdown values. The migration includes a custom property creation step in Nutshell before contact import.

Groundhogg owners are WP user IDs referenced on Contact records. We export WP user email addresses and match them to Nutshell User records by email during migration. Any Groundhogg owner without a matching Nutshell User is placed in a reconciliation queue; the customer's Nutshell admin provisions missing users before contact import resumes. Owner is assigned to each Contact during import via the resolved User ID.

Groundhogg Deals (Pro tier and above) map to Nutshell Deal records. Deal name, value, stage, and close date migrate directly. Groundhogg pipeline stages map to Nutshell Deal status values. If the customer's Groundhogg account is on Basic or Plus, Deals may not exist or may be stored in a workaround custom field; we audit the account during scoping and document the actual Deal presence before migration.

Groundhogg logs contact activities as chronological events (email opens, link clicks, tag applied/removed, form submissions). We export the full activity log per contact and create timestamped Activity records in Nutshell. Activity type maps to Nutshell's activity type field (email_opened, link_clicked, tag_added, tag_removed, form_submitted). The original Groundhogg timestamp is preserved on each Activity record to maintain the engagement timeline order. Activity records are imported after Persons and Deals so that parent record lookups resolve correctly.

Groundhogg contact-level notes migrate to Nutshell Note records linked to the corresponding Person. Note content, author attribution, and creation timestamp preserve. Notes authored by WP users with no matching Nutshell User are attributed to the Nutshell admin user who initiated the migration.

Groundhogg Broadcast emails are exported with subject, send date, and recipient count metadata. We do not migrate broadcast content as discrete objects. Recipients of broadcasts are flagged in the contact record's activity history (email_sent event type). The customer should document broadcast content separately for re-sending in Nutshell's email campaigns or an alternative sending tool.

Groundhogg Flows cannot be exported as automation logic. We export the trigger type, step count, step names, and tag actions as a written Flow Audit document. This document is delivered to the customer's admin team with recommended Nutshell Workflow equivalents. Rebuilding Flows in Nutshell is a manual admin task outside migration scope.