# Move from Re:amaze to Rinhelp

Re:amaze conversations with their internal notes and files, articles by topic and Response Templates all come across over the Re:amaze API. Ask for filter=all, because the conversation list hides every archived conversation unless you do.

| Conversations | Time to read them |
| --- | --- |
| 1,000 | no per-minute limit to time it by |
| 10,000 | no per-minute limit to time it by |

Limit used: no per-minute number (per API token, number not published), about 2 per conversation. Rinhelp takes up to 3,000 conversations a minute. Importing is free: it never emails your customers, never runs Rin and never counts toward a plan.

Give the AI agent your Re:amaze login email, your own API token and the host name of each brand, since the API works one brand at a time. Afterwards, set each teammate’s role again in Rinhelp, because Re:amaze’s API doesn’t share staff roles.

## Prompt for a chat app

Re:amaze has no MCP or export file, so read https://rinhelp.com/migrate/reamaze.md and call the Re:amaze API with the login email and API token I paste here. Start with my Response Templates and articles, drafts included, then bring over a small batch of open and archived conversations.

## Prompt for a coding agent

Follow https://rinhelp.com/migrate/reamaze.md to copy every Re:amaze brand I have into Rinhelp. Sign in with my login email and API token, list conversations with filter=all, 30 per page, and fetch each one’s messages, keeping visibility 1 as notes. Re:amaze publishes no per-minute number, so back off whenever it answers HTTP 429.

## Words

| Their word | Rinhelp |
| --- | --- |
| Internal note | Note |
| Contact | Customer |
| Staff | Teammate |
| Topic | Section |
| Response Template | Saved reply |

## What stays behind

- Automations (workflows)
- Reports
- Satisfaction ratings history
- Status page
- Staff roles

## Facts

- The Re:amaze API signs in with your login email and a personal API token over HTTPS, and every staff user has their own token. Vendor page: https://www.reamaze.com/api (checked 2026-10-31)
- Each Re:amaze API request is scoped to one brand, chosen by the host name you call, so an account with several brands needs one pass per brand. Vendor page: https://www.reamaze.com/api (checked 2026-10-31)
- Re:amaze rate limits each API token per minute without publishing the number, and answers HTTP 429 when you go over. Vendor page: https://www.reamaze.com/api (checked 2026-10-31)
- By default Re:amaze lists only unarchived conversations, so a copy that skips filter=all quietly misses all closed history. Vendor page: https://www.reamaze.com/api/get_conversations (checked 2026-10-31)
- Re:amaze returns conversations and their messages 30 per page, moving on by page number. Vendor page: https://www.reamaze.com/api/get_messages (checked 2026-10-31)
- Re:amaze mixes internal notes into the messages and marks them only with visibility 1, so the AI agent must keep those private. Vendor page: https://www.reamaze.com/api/get_messages (checked 2026-10-31)
- Each Re:amaze message lists its attachments with a content type and download links. Vendor page: https://www.reamaze.com/api/get_messages (checked 2026-10-31)
- The Re:amaze articles call returns only published articles unless you ask for draft or internal ones, and each article names its topic. Vendor page: https://www.reamaze.com/api/get_articles (checked 2026-10-31)
- Re:amaze’s API doesn’t support its staff “Role” resource, so roles don’t come across. Vendor page: https://www.reamaze.com/api/get_staff (checked 2026-10-31)

## Steps

Import source: `reamaze`

Connect Rinhelp's MCP server, https://mcp.rinhelp.com/mcp, then follow https://mcp.rinhelp.com/migrate.md step by step with the facts above.

1. [Connect your AI agent](https://docs.rinhelp.com/articles/98a0def1-a07d-4c34-9f19-4d168626b40c-connect-your-ai-agent)
2. [Move to Rinhelp with your AI agent](https://docs.rinhelp.com/articles/5a2a3f45-4e61-4daf-8d23-570a8bfc24a1-move-to-rinhelp-with-your-ai-agent)
3. [Import your help center articles](https://docs.rinhelp.com/articles/a79b3172-a803-44a2-9236-0ab73d56b051-import-your-help-center-articles)
4. [Keep your old help center links working](https://docs.rinhelp.com/articles/ba9cf0f3-9740-4c90-9ca5-7a9a0ef0b450-keep-your-old-help-center-links-working)
5. [Import saved replies](https://docs.rinhelp.com/articles/5d8f8400-2a36-4974-a646-c9f04a41361d-import-saved-replies)
6. [Import past conversations](https://docs.rinhelp.com/articles/7e85f2b0-336d-4774-850a-826951d9585c-import-past-conversations)
7. [Switch your support email to Rinhelp](https://docs.rinhelp.com/articles/44c7935d-ccee-409b-83ac-fa4e5f762eb0-switch-your-support-email-to-rinhelp)
8. [Replace your chat widget](https://docs.rinhelp.com/articles/031f9d71-579b-4229-8f50-3eee8e31c277-replace-your-chat-widget)

## Questions

### Re:amaze shows only my open conversations. Where did the archived ones go?

Re:amaze leaves archived conversations out of its list unless the request says filter=all. Ask the AI agent to list again with that filter, and the closed history comes across too.

### I run three brands in Re:amaze. Do I move each one separately?

Yes. Re:amaze picks the brand from the host name each request goes to, so the AI agent makes one pass per brand host with the same login email and token.

### Will my internal notes show up as replies to customers?

No. Re:amaze marks an internal note with visibility 1, and the AI agent saves those as notes in Rinhelp, which customers never see.

By Wilbert Liu, founder of Rinhelp. Page: https://rinhelp.com/migrate/reamaze