Move from Front to Rinhelp
By Wilbert Liu, founder of Rinhelp · Facts checked · Markdown for AI agents
Front conversations, messages, internal comments, message templates and tags move to Rinhelp. Front has no export you can run yourself, and its API starts at 50 requests a minute, so the full move goes at your plan’s pace.
| Conversations | Time to read them from Front |
|---|---|
| 1,000 | about 20 minutes |
| 10,000 | about 3 hours |
Limit used: 100 requests a minute (Professional plan), 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. For the MCP server, someone in Front creates an OAuth client ID and secret, since Front doesn’t support dynamic client registration. If you want a file instead, only Front’s Support team can make that export.
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 Front’s MCP server at https://mcp.frontapp.com/mcp with read-only access, then follow https://rinhelp.com/migrate/front.md. Search my message templates and save each one in Rinhelp, and copy articles from my public Front knowledge base.
Move every Front conversation into Rinhelp using https://rinhelp.com/migrate/front.md and Front API credentials with the message_templates:read permission. Each conversation needs one call for messages and one for comments. The list can’t filter by date, so walk it newest first by page token and stay under my plan’s limit.
What we measured
We imported the public help center at help.front.com into a test workspace with Claude Code on : 829 articles in 5 sections came across as drafts in about 23 minutes, were published in about 1 minute more, and every old address answered with a redirect. 64 conversations with 207 messages, shaped like its API’s responses, came across with their files. The full run.
Their words and ours
| In Front | In Rinhelp |
|---|---|
| Conversation | Conversation |
| Message | Message |
| Comment | Note |
| Contact | Customer |
| Message template | Saved reply |
| Tag | Tag |
| Knowledge base | Help center |
What stays behind
- Rules
- Inbox and channel settings
- Analytics
- Shifts and SLAs
Front facts that shape the move
Front’s API allows 50 requests a minute on Starter, 100 on Professional and 200 on Enterprise. Source, checked .
Conversations are listed newest first, 100 per page at most, with a page token. Source, checked .
The conversation list has no date filter, only a sort order, so you can’t pull just a time range. Source, checked .
Messages come per conversation, newest first, 100 per page at most, each with its attached files. Source, checked .
Internal comments sit behind a separate call from messages. Source, checked .
Front has no in-app export: you ask its Support team, who only promise to acknowledge the request within 72 hours. Source, checked .
That support export leaves out templates and tags and covers shared inboxes only. Source, checked .
Message templates can be listed with the message_templates:read permission. Source, checked .
The API lists knowledge bases, but documents no calls for their articles or categories. Source, checked .
Front’s official MCP server searches conversations, people and message templates, and can be given read-only access. Source, checked .
Questions
Can Front just send me an export file?
You can ask Front’s Support team, but they only promise to reply within 72 hours, and the file skips templates, tags and anything outside shared inboxes. The API gets you everything.
Do Front’s internal comments come across?
Yes, as notes on each conversation. Front keeps them behind their own call, which is why each conversation takes two requests.
Can I move only the last year of Front conversations?
Front’s list can’t filter by date, but it runs newest first. Your AI agent can stop once it reaches the date you choose.