Integrations & imports

Import from Groove

Move contacts, conversations, notes, drafts, and files while keeping source mappings clear.

Open Settings → Imports → Groove as an owner or administrator. Start with a small dry run so you can check source-account access and where the history will go.

Connect and map

Enter a Groove owner/admin token and choose Check connection. Under Map Groove agents to teammates, select the existing OutcomeArc person for each agent. Different source and sign-in email addresses are fine; don’t create a second teammate just to match an old address.

Map Groove channels to the intended OutcomeArc inboxes. Automatic mapping uses saved mappings and matching emails where available. A fallback inbox is a destination, not a filter that limits which source channels are imported.

Choose a sample

The default scope is the current UTC creation year, conversations only, one page, at most three conversations, and attachments off. Associated contacts are included with eligible conversations.

Run the dry run and check that conversations and messages were actually processed—not just users and channels. Then import the same sample and inspect its history. Dry-run mappings need to be retained or re-entered for the real import.

The import preserves supported contact data, messages, private notes, drafts, tags, assignments, and timestamps. Historical drafts are not sent, and imported history does not start new AI or live automation work.

Expand deliberately

For a full year, set Max pages per phase to 10,000 and clear Max conversations. Enable attachment downloads if you need files. All years includes all eligible creation years, with later replies included in each conversation.

Trashed and deleted history is excluded by default, even with All years. Include trashed and deleted conversations is a separate historical-recovery choice. A page or sample limit produces a warning rather than proving the migration is complete.

Recover a failed import

Open Import progress → Recover failed import, review the saved failure and scope, and supply a fresh token for the same Groove account.

Retry saved page and continue is the default recovery path. When a specific failed file is identified, Skip failed attachment only; keep its message can preserve the rest of the thread. Broader message or conversation skips omit more history, so choose them only deliberately.

Where supported by the recorded failure, a draft-only recovery choice can omit that conversation’s drafts while keeping sent messages and saved notes. Every skip or omission remains a warning; it is not a complete copy of that content.

Recovery creates a new job and retains the original. Save the new job URL and review its results. Re-imports use stable source identities but can update source-owned fields, so consider local edits before replaying history. Configure live email separately after migration.

Browse all topics →

Still need a hand? Ask our team.