Move from HubSpot to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
HubSpot inbox threads with their messages and comments, plus your knowledge base articles, move to Rinhelp. Snippets are the gap: HubSpot offers no import, export or API for them, so they get copied by hand.
| Conversations | Time to read them from HubSpot |
|---|---|
| 1,000 | about 1 minute |
| 10,000 | about 9 minutes |
Limit used: 1,140 requests a minute (Professional and Enterprise, 190 per 10 seconds), about 1 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. Someone in HubSpot creates a privately distributed app with the conversations.read permission for your AI agent. They also paste in any snippets you want to keep.
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.
HubSpot’s MCP server reads CRM records such as tickets, but not inbox threads or the knowledge base, so this chat can only do part of the move. Following https://rinhelp.com/migrate/hubspot.md, copy my public HubSpot knowledge base into Rinhelp, and save the snippets I paste in as saved replies.
Use https://rinhelp.com/migrate/hubspot.md to import every HubSpot conversation thread into Rinhelp through a private app with conversations.read. List threads 500 at a time, pull each thread’s messages, and keep COMMENT messages as notes. Stay under 190 requests per 10 seconds and the daily cap all our apps share.
Their words and ours
| In HubSpot | In Rinhelp |
|---|---|
| Thread | Conversation |
| Ticket | Conversation |
| Message | Message |
| Comment | Note |
| Contact | Customer |
| Agent | Teammate |
| Snippet | Saved reply |
| Knowledge base article | Article |
What stays behind
- Workflows
- Routing and assignment rules
- Help desk views
- Reports
HubSpot facts that shape the move
HubSpot lists inbox threads up to 500 at a time, and each thread’s full message history has its own call. Source, checked .
Internal comments are messages of type COMMENT, and they never go to the customer. Source, checked .
Reading threads needs the conversations.read permission. Source, checked .
Message attachments are links to files kept in HubSpot’s files tool. Source, checked .
A privately distributed app gets 100 requests per 10 seconds on Free and Starter, and 190 on Professional and Enterprise. Source, checked .
A daily cap is shared across all your apps: 250,000 on Free and Starter, 625,000 on Professional. Source, checked .
HubSpot’s official MCP server covers CRM records like companies, deals and tickets, and mentions neither inbox threads nor the knowledge base. Source, checked .
The knowledge base API is still in beta, so its behaviour can change. Source, checked .
Knowledge base articles list 25 per page by default and 100 at most. Source, checked .
Snippets live in the app, and HubSpot’s help page mentions no import, export or API for them. Source, checked .
Questions
Do my HubSpot snippets come over?
Not on their own, because HubSpot offers no way to export them. Paste them into the chat and your AI agent saves each one in Rinhelp as a shared saved reply.
Can I rely on HubSpot’s knowledge base API for my articles?
It works, but HubSpot still calls it beta. If a call fails, your AI agent can read the public knowledge base pages instead.
Will the import use up our daily HubSpot API cap?
It draws on it. All your apps share 625,000 requests a day on Professional and 250,000 on Starter, and each thread takes about one, so most histories fit in a day.