AJERIS
TourBlogDocsLog inText us
Log inText us
← AI agents

From OpenClaw to Ajeris: a switching guide

If you tried OpenClaw and want the agent without the stack, here is the practical migration path: memory, skills, channels, integrations.

Ajeris team·May 6, 2026·5 min read
A developer at a laptop in low light. Migrating off OpenClaw: memory, skills, channels, integrations, in order.

This is the practical version of the OpenClaw-to-Ajeris switch, written for people who already tried OpenClaw and decided they wanted the hosted contract instead. We are not going to argue you out of it; if you opened this page, you have already made the decision. The post is about the mechanics.

★The thesis

The migration is mostly recreating, not porting. There is no one-click memory import. The good news: most users discover the things they cared about porting are the things they remember well enough to recreate quickly.

What ports cleanly

The agent shape is the same on both sides. So the things that port cleanly are the things that are inherent to the shape:

  • The user contract. Text the agent; agent responds. Same on both sides.
  • The MCP servers you bring. If you have custom MCP servers running on OpenClaw, they work with Ajeris too. Same protocol; we add your URL and bearer token, the agent picks them up.
  • The model brain. OpenClaw lets you pick the model; Ajeris uses Claude as the default. Most operational tasks behave indistinguishably.
  • Your contacts and calendar. Those live in your OAuth-connected accounts (Google, Apple, etc.). The agent on the other side reads from the same accounts.

If your OpenClaw setup was mostly about "agent that uses my real accounts," the switch is roughly free.

What does not port and how to handle it

Three things that need attention:

1. Memory. OpenClaw's memory store is on your infrastructure. Ajeris's is on ours. There is no automatic import. The pragmatic workaround: text the new agent the things you want it to remember. The conversation that takes 15 minutes ("here is who I am, here are the people in my life, here are the routines I want you to know about, here are the preferences I want you to respect") is enough to recreate the most-load-bearing memory.

The longer-tail memory (specific conversations, niche facts) usually does not need migrating. Most of it was situational; it would not have been useful in the new context anyway.

2. Skills. OpenClaw's skill marketplace gives you 13,000+ skills to install. Ajeris's catalog is smaller and vetted; the pattern is to bring your own MCP servers for the long-tail tools you used.

The pragmatic workaround: list the OpenClaw skills you actually used regularly. Cross-reference against the Ajeris connector list and the built-in tool catalog. For anything not covered natively, your option is custom MCP. If the underlying tool has an HTTPS API, you can wire it.

Most users discover they were running 5-15 skills regularly out of the marketplace's 13,000. Those 5-15 are what need to port. The 12,985 you never used do not.

3. Channels. OpenClaw lets you wire 24+ messaging integrations. Ajeris ships six (SMS, WhatsApp, Telegram, voice, Alexa, email) out of the box. If you specifically used a long-tail OpenClaw channel (a regional messenger, a niche IRC bridge), that channel is on you to recreate.

Most US and global usage falls inside the six built-in channels. If yours does not, the switch is harder.

The migration sequence, day-by-day

A realistic week:

Day 1. Text the Ajeris agent at +1 (470) 821 4265. Run the setup wizard. Connect the OAuth integrations you actually use (Gmail, Calendar, Drive, etc.). Have a 15-minute conversation telling the agent who you are.

Day 2-3. Use the agent for normal tasks. Notice what is missing. Note the OpenClaw skills you reach for that the new agent does not have. Identify which need custom MCP and which can be recreated as agent skills.

Day 4-5. Wire the custom MCP servers for the tools you specifically needed. Most of them are HTTPS APIs you already had bearer tokens for; the switch is changing where you point them.

Day 6-7. Compare. By the end of week 1, you will know whether the switch holds. Most users who reach day 7 stay; the ones who do not are usually the ones with a hard requirement (open-source license, data residency, marketplace breadth) that should have flagged up front.

What you give up by switching

Honest answer:

  • Open source. Ajeris is closed-source. If MIT-licensed code is a hard requirement, do not switch.
  • Self-hosted operation. If data residency is a constraint, do not switch.
  • The marketplace breadth. 13,000 skills > a few hundred + your custom MCPs. If you genuinely use an obscure long-tail skill, you give it up.
  • The community. OpenClaw's Discord has 180,000 members. Ajeris's is smaller. We have a different shape of community (more end-users, fewer engineers).

What you gain by switching

The places we win are operational and accessible:

  • Setup is over. Five minutes vs hours. No more daemon to debug.
  • Updates and patches handled. No more breaking changes from upstream.
  • Bounded blast radius. The publicly-documented OpenClaw worst case (production database wipe) is structurally not the Ajeris worst case.
  • Voice receptionist. OpenClaw is not a phone product. Ajeris is.
  • Personal agent for non-technical users. The grandparent in your life can text the agent. They cannot run OpenClaw.
An old laptop with the cover closed and a newer phone resting on top of it, the visual of the operational simplification that comes from switching to a hosted product.
The laptop you used to operate the agent on is the thing you stop opening. The phone is the new interface.

Three switch stories

The engineer who chose hosted. Could absolutely self-host. Did the math; the operational time was not worth the savings. Switched and uses the time he reclaimed to ship his own product. Reports the only thing he misses is the open-source ergonomic.

The non-technical user whose engineer partner had set up OpenClaw for them. The partner moved out (different reasons). The OpenClaw setup needed maintenance. The user could not maintain it. Switched to Ajeris because the contract did not require maintenance.

The agency. Ran OpenClaw deployments for ~30 small-business clients. Each deployment was an engineering project; scaling was painful. Migrated all clients to Ajeris's business agent. The 5-minute-per-client setup made the agency model finally work.

OpenClaw (self-hosted)
  • Hours of setup; ongoing operations.
  • 13,000+ skill marketplace breadth.
  • Open-source license; self-hosted infrastructure.
  • Best for engineers who want the stack.
  • No phone number; not a voice product.
Ajeris (hosted)
  • Five-minute setup; hosted forever.
  • Vetted built-in catalog plus custom MCP.
  • Closed-source SaaS; we host.
  • Anyone with a phone can use it.
  • Phone number provisioned. Voice receptionist included.

Frequently asked

Will my OpenClaw memory transfer?+
Not automatically. The pragmatic workaround is a 15-minute conversation telling the new agent who you are. Most users find this is enough; the long-tail memory was situational and rarely matters in the new context.
What about the 13,000 skills I had access to?+
Most users were using 5-15 of them. Cross-reference your real list against Ajeris's built-in catalog plus custom MCP. The long tail you never used was, by definition, not load-bearing.
Can I run both during migration?+
Yes. Many users keep OpenClaw running for a few weeks while they get comfortable with Ajeris. The two do not interfere.
What about my custom skills I built for OpenClaw?+
If they are HTTPS-callable, port them as MCP servers. The protocol works on both sides; the configuration is moving where you point them.
What if I want to switch back?+
Free to start, no card. If you decide hosted is not the right shape, you walk away. OpenClaw will still be there. The switch is not irreversible.

Try it

Free to start. Text +1 (470) 821 4265. The migration takes a day or two of attention; the agent is usable from minute one.

For the head-to-head comparison, see Ajeris vs OpenClaw.

More stories

A phone on a cafe table, top-down. The case for the agent that lives where the conversation already is.
AI agents

Why texting wins: the case for messaging-first agents

Chat windows, smart speakers, and dedicated apps each have a thesis for the AI agent. The thesis that holds up daily is the one that meets people in their messages.

An iPhone on a cafe table with a serif headline reading 'An AI agent that lives in your text messages.'
AI agents

What is a personal AI agent?

A personal AI agent is one assistant that lives in your text messages and actually does the work across every tool you already use. Here is what that means.

Try Ajeris.

Text +1 (470) 821 4265. Your agent replies in seconds. Free.

Text on WhatsApp
Connects to

Every tool you already use. Your agent does the rest.

WhatsApp
Gmail
Calendar
Slack
Notion
GitHub
Instagram
Spotify
Uber
DoorDash
Apple Music
Telegram
WhatsApp
Gmail
Calendar
Slack
Notion
GitHub
Instagram
Spotify
Uber
DoorDash
Apple Music
Telegram
Shopify
QuickBooks
Xero
Square
HubSpot
Salesforce
Stripe
Lyft
Alexa
Google LSA
Hue
Claude
Shopify
QuickBooks
Xero
Square
HubSpot
Salesforce
Stripe
Lyft
Alexa
Google LSA
Hue
Claude

Message to start

+1 470 821 4265

Message the number above on WhatsApp or by SMS. Your assistant replies within seconds and sets itself up in the conversation. Or sign up by web form to be added to our list.

Welcome message. “Hi. I’m Ajeris. I’ll be your personal agent. What should I call you? Reply STOP to unsubscribe, HELP for help.”

STOP to unsubscribe. HELP for support.

Message and data rates may apply. Carriers are not liable for delayed or undelivered messages. Message frequency varies based on your interaction with the agent.

Questions: hi@ajeris.com

Your assistant is already in your phone. You just need to text it.

The personal assistant you can actually get today. No app, no waitlist.

WhatsApphi@ajeris.com
Personal
  • Channels
  • Morning brief
  • Meetings
  • Research and build
  • Laptop on a leash
  • Everyday
  • Memory
Platform
  • Connectors
  • Platform
Developers
  • Docs
  • Quickstart
  • Platform overview
  • Memory model
  • Skills
  • Scheduled tasks
  • MCP server
  • Claude Code
  • Alexa+
Resources
  • Blog
  • Compare
  • Glossary
  • Live webinar
  • Creator Program
Trust
  • Privacy
  • Security
  • Terms
  • Data retention
  • Access controls
  • Vulnerability management
  • Opt in
  • Disconnect

Your personal agent, by text.

Try it free·Ajeris for business·docs.ajeris.com·© 2026 Ajeris