Consolidating Accounts

Ended up with two Town accounts — maybe you signed up once with your work email and again with a personal one? Here’s how to get everything back under a single Townie.

There’s no automatic merge

There’s no button that fuses two Town accounts into one. Instead, you consolidate manually: keep the account you want as your main one, move anything you need off the other, then delete the extra account and add its email to your main account.

Recommended steps

Decide which account is your main one — the Townie, history, and settings you want to keep.
Save anything you need from the secondary account. Ask that account’s Townie to compile what you want to keep — the migration prompt below does this thoroughly. (There’s no structured, one-click export — see Managing Your Account.)
Delete the secondary Town account from its Settings → Delete Account. See Managing Your Account.
Add that email to your main account as an additional email account. See Multiple Email Accounts. Now your one Townie covers both mailboxes.

Deleting an account is a soft-delete first (immediately deactivated) and a permanent delete within 30 days. Make sure you’ve saved what you need before you delete the secondary account.

One prompt that inventories your whole setup

Step 2 — saving what you need — is the part people underdo. The prompt below has your Townie write a complete, rebuild-ready inventory of your setup into a single doc: every routine with its full prompt text, skills, memories, notification settings, integrations, calendar labels, and more, plus a checklist to tick off as you recreate each item.

Run it on the account you’re moving away from — open a new chat with the prompt pre-filled (double-check which account you’re signed into before you hit send), or copy it into any chat:


I'm moving my Town setup to a different Town account. Produce a single, complete migration handoff document I can use to rebuild everything in the new account. Do a full inventory of my current setup and write it all into one Town doc titled "Town Migration Handoff — [today's date]". Be exhaustive and capture exact configuration — I'll be recreating each item by hand or by pasting these details to my new assistant, so don't summarize or truncate anything meant to be reused verbatim.

Capture each of the following in its own clearly labeled section:

Routines — Every routine I have: personal custom routines, installed shared routines, and team routines. For each, capture verbatim: name, description, the full prompt text (paste exactly, no summarizing), all triggers and schedules, which tools and integrations it uses, its approval mode, whether it's currently enabled, and any per-routine settings or linked sub-routines. For installed shared routines, note the source so I can reinstall rather than rebuild. Flag any routine that depends on an integration or MCP server that will need reconnecting.

Skills — Every skill available to me (personal and team). For each: name, description, and the full skill content (the complete skill instructions, plus a note of any companion files). Paste content verbatim.

Memories and preferences — Dump all stored memories and preferences, global and routine-specific. Include my assistant personality and voice settings.

Profile — Everything in the profile you keep about me, verbatim.

Notification preferences — All notification settings (where approval requests go; the channels for chats, tasks, reminders, agent-to-agent, meeting summaries, and product updates; away time) and email composition settings (signature, avatar).

Integrations and MCP servers — Every connected integration and every connected MCP server (personal and team), with enough detail to reconnect each one. State clearly that these must be re-authorized manually — credentials and connected accounts do not transfer.

Calendar labels — Any calendars I've labeled or described, and what I've said each one is for.

Content Library — My Content Library collection structure (the folder tree) with each collection's description, so I can recreate the organization. Note that the files themselves must be re-uploaded or copied separately.

Email accounts and trusted contacts — The email accounts connected, and any trusted recipient lists configured for my routines and assistant.

Formatting: one Town doc. Clear headers per section, a subsection per item. For routines and skills, wrap verbatim prompt and skill text in fenced code blocks so nothing gets reformatted. At the top, add (a) a short "what transfers automatically vs. what I must rebuild by hand" summary, and (b) a checklist I can tick off as I recreate each item. Where something genuinely can't be exported (live credentials, connected-account tokens, historical run and session data), say so explicitly rather than omitting it. When you're done, give me the link to the doc.

The handoff doc is created in the account you’re about to delete. Before you delete, get it out — ask your Townie to email it to you, or copy its contents somewhere outside Town. And remember what can’t transfer at all: integration credentials and connected email accounts (you’ll reconnect those by hand in the new account), chat history, and past routine activity.

The same prompt works if you’re moving into a team-managed account rather than consolidating two personal ones.

Changing your primary account

If you want to change which email is the primary account on your Town login (not just add another), that switch is handled by our team today. Email support@corp.town.com and tell us the account and the email you’d like as primary.

When to just email support

If any of this is unclear, or you’re worried about losing data, don’t force it — email support@corp.town.com. Account merges and primary-account switches are exactly the kind of thing our team handles directly.