Move from Hiver to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
Hiver’s email conversations come over through its API or its official MCP, which reads the emails themselves, and Email Templates come from the admin export. The API allows 1 request a second and 5,000 a day, so a large history takes several days.
| Conversations | Time to read them from Hiver |
|---|---|
| 1,000 | about 34 minutes |
| 10,000 | about 4 days |
Limit used: 60 requests a minute (1 a second per account, and 5,000 a day), about 2 per conversation. Rinhelp takes up to 3,000 conversations a minute.
Free. Importing never emails your customers, never runs Rin and never counts toward a plan.
Needs a person. A Hiver admin creates the API key, which acts with admin power, and runs the admin export to get your Email Templates. With the MCP, each teammate connects their own Hiver account and sees only the Shared Inboxes they belong to.
Paste one prompt
Connect your AI agent to Rinhelp first, then paste the prompt for the app you use. It reads this page’s Markdown and follows Rinhelp’s steps.
Connect Hiver’s official MCP with my own account and follow https://rinhelp.com/migrate/hiver.md. Bring the email conversations from my Shared Inboxes into Rinhelp with their emails, tags and status, and use the Email Templates file from the admin export I upload for saved replies.
Use https://rinhelp.com/migrate/hiver.md to move my full Hiver history with the admin API key I give you. List each inbox’s conversations 100 a page until next_page is null, send at most 1 request a second, and pause until tomorrow when the 5,000 daily requests run out. If the API leaves out email bodies, read them through Hiver’s MCP.
Their words and ours
| In Hiver | In Rinhelp |
|---|---|
| Shared notes | Note |
| Contacts | Customer |
| Users | Teammate |
| Email Templates | Saved reply |
| Tags | Tag |
What stays behind
- Automations
- Analytics and reports
- SLA settings
- The emails themselves in Gmail
Hiver facts that shape the move
Only a Hiver admin can create an API key, and the key has an admin’s access. Source, checked .
Hiver’s API allows 1 request a second per account and 5,000 requests a day. Source, checked .
Hiver’s API lists an inbox’s conversations 10 to 100 a page, until next_page comes back null. Source, checked .
Hiver’s admin export emails a link to XML files with conversation details, Email Templates, drafts and contacts. Source, checked .
Hiver’s export lists subjects, IDs, assignees, status, tags and notes, but not email bodies, and a new export can’t start while one runs. Source, checked .
Hiver’s official MCP reads the content of every email in a conversation, along with its subject, status, assignee and tags. Source, checked .
Hiver’s MCP works only with email inboxes, so chat and other channels stay out of its reach. Source, checked .
Each person connects their own Hiver account to the MCP, which sees only the Shared Inboxes they belong to. Source, checked .
Hiver’s MCP signs in with OAuth, can make shared drafts and add notes and tags, and can’t send email. Source, checked .
Questions
Why does moving Hiver take days?
Hiver’s API stops at 5,000 requests a day, at 1 a second. With about two requests per conversation, the AI agent moves roughly 2,500 conversations a day and carries on the next morning.
Does Hiver’s export have my email bodies?
Its contents list subjects, status, tags and notes but no email bodies. The AI agent reads the emails themselves through Hiver’s MCP, which does return them.
Who on my team has to connect Hiver?
The MCP sees only the Shared Inboxes of the person who connects it, so someone in every inbox you’re moving connects their own account. An admin creates the API key for a full copy.