Migrate from Groundhogg to Microsoft Dynamics 365 Sales

Groundhogg Contact records map to Microsoft Dynamics 365 Sales Contact. Standard properties (email, firstname, lastname, phone, address) map directly to Dataverse Contact fields. Custom fields export from Groundhogg's REST API as key-value pairs and are pre-created as Dataverse custom fields before import. Contacts must be imported before any object that holds a Contact lookup reference.

If Groundhogg contacts include a mix of prospect and customer lifecycle stages, we split by a defined criteria during scoping. Groundhogg contacts flagged as prospects with no associated Deal map to Lead; contacts attached to Deals or with a customer lifecycle stage map to Contact. The split criteria is documented and approved during discovery before migration begins.

Groundhogg Companies (Plus tier and above) map to Microsoft Dynamics 365 Sales Account. Company name becomes Account Name; address fields map to Address fields on Account. We link each Contact to its parent Account during import by matching Company name or a Groundhogg company_id if present. Companies on Basic-tier Groundhogg instances are audited before export because the feature may have been used via legacy entitlement rather than an active plan.

Groundhogg tags are a flat taxonomy stored as a comma-separated list on each Contact. Tags export as a full distinct list during discovery. We map tags to a Dynamics 365 multi-select picklist field on Contact or to Topics with TopicAssignment records, depending on whether tags represent contact classification or content categorization. The customer chooses tag strategy during scoping.

Groundhogg Deals (Pro tier and above) map to Microsoft Dynamics 365 Sales Opportunity. Deal name becomes Opportunity Name; Deal value maps to Amount; stage name maps to a Dynamics Sales Process stage. If the customer has multiple Groundhogg pipelines, each becomes a Dynamics Opportunity Record Type with its own Sales Process whitelisting the relevant stage values.

Groundhogg pipeline stages export with stage names and display order. We configure corresponding Dynamics Sales Process stages before migration, mapping probability percentages from Groundhogg to the Stage Probability field. Visual pipeline layout does not migrate; we document the stage order and names for the customer's admin to configure in Dynamics.

Groundhogg maps owners via WordPress user IDs. We export WP user email addresses and match them against the destination Dynamics 365 organization's Azure Active Directory users. Any Owner without a matching Azure AD user goes to a reconciliation queue for the customer's admin to provision before record import. Migration cannot proceed past Contact and Opportunity import until all OwnerId references are resolved because Dynamics enforces referential integrity on OwnerId.

Groundhogg activity logs (email opens, link clicks, form submissions, tag applied/removed) export per Contact with timestamps. We create corresponding Dynamics Activity records: email opens as Email with date; link clicks as Task with subject and timestamp; form submissions as Note or Task. Activity ordering is preserved by setting the ActualEnd or ScheduledEnd date to the original Groundhogg timestamp. Large activity volumes use Dataverse Bulk API with batch chunking.

Groundhogg contact-level notes export with body text, author attribution, and creation timestamp. Notes map to Dynamics 365 Annotation records linked via regarding_objectid to the Contact or Account. Author attribution maps from the Groundhogg WP user email to the Dynamics User lookup on the Annotation.

Groundhogg custom fields on Contact, Company, and Deal records export with field type information (text, number, date, dropdown). We pre-create corresponding Dataverse custom fields in the destination Dynamics 365 environment before data import. Dropdown and choice-type custom fields require a value mapping table to translate Groundhogg option labels to Dynamics option set values.

Groundhogg Flows cannot be exported as automation logic via the REST API. We run a Flow Audit step during discovery: we export trigger type, step count, step names, and step action descriptions for every active Flow. This documentation is delivered as a written inventory with a recommended Power Automate or Dynamics Workflow equivalent for each Flow. The customer's admin rebuilds Flows post-migration.

Groundhogg broadcast emails export with subject, send date, and recipient count metadata. Broadcast content and recipient lists do not migrate as discrete objects. Contacts who received broadcasts are flagged with a custom field or tag indicating broadcast receipt so the customer's admin can re-segment in Dynamics. We document broadcast send history for reference.