Migrate your GrooveHQ data

Conversations are Groove's primary ticket object. Each conversation contains the full message thread, timestamps, assigned agent, status, and attachments. We map this directly to the destination ticketing object preserving all metadata.

Customers represent end-user contacts with name, email, phone, and custom contact-level fields. We map this to the destination's contact or customer object 1:1.

Groove stores company data as a separate object with its own custom fields distinct from contacts. Where the destination CRM does not have a separate Company object, we merge company fields into the customer record as custom properties.

Agents are team members with name, email, role, and assignment permissions. We transfer agent records as users in the destination system, preserving their display names and email addresses.

Custom Fields applied at the conversation level include dropdowns, date fields, and text fields. Available on Plus and Pro plans only. We map these to destination ticket custom fields, flagging any field types that do not exist natively.

Contact and company custom fields are configured in Settings and apply globally. We map these to destination contact or account custom properties, preserving field types and values across all associated records.

Inboxes are shared workspaces containing assigned conversations. Plan tiers cap inboxes at 2, 5, or 25. We flag inbox count during scoping and recommend a plan upgrade if the source org exceeds the target plan limit before migration.

Knowledge Bases are top-level containers with locale, password, and IP protection settings. We transfer the full knowledge base configuration including primary flag and theme ID. Downgrade from Pro may deactivate secondary knowledge bases.

Articles sit inside knowledge base categories with title, body content, meta tags, and open graph fields. We map articles to destination help center articles preserving category structure and SEO metadata.

Tags are key-value labels applied to conversations for categorization. We transfer tags as a simple list attached to each conversation, mapping them to destination ticket tags or labels.

Smart Folders are saved filtered views based on status, assignee, custom field conditions, or inbox scope. The filter logic does not export directly—we recreate Smart Folders as saved filter views in the destination and document the original filter criteria for manual setup if needed.

Rules trigger actions based on conversation events like assignee changes, status updates, or custom field conditions. We export rule definitions as structured JSON and map them to destination automation equivalents, flagging any conditions or actions that do not have a direct counterpart.

Instant Replies are templated responses inserted by agents during conversations. We transfer the full library of instant replies as canned response templates, preserving formatting and variable placeholders.

File attachments within conversation messages are stored as URLs pointing to Groove's file storage. We download each attachment and re-upload to the destination system's file storage, preserving original filenames and attachment order within message threads.