Agent apps
Base44 AI Agents and Superagents
OffRamp · October 30, 2026 · 8 min read
Short answer: a Base44 Superagent is workflows, schedules, tool connections, messaging channels, and memory — and none of those come along in an app export. Base44's export carries code and data tables. Your agent's running life — the daily summary job, the WhatsApp thread, the HubSpot connection, the memory of how you work — lives in Base44's agent layer, not in the exported project. Migrating an agent means rebuilding those pieces on infrastructure you own. This page maps what moves, what breaks, and the order to do it in.
What it is
What a Base44 Superagent actually is
Base44 launched Superagents in March 2026 as a new surface beyond apps. The pitch, in Base44's own words: you don't design screens or pages — you describe the job, and the Superagent takes action using your connected tools, files, and memory. It can act as a personal assistant, support rep, marketer, or analyst depending on the job you give it. It isn't tied to one app the way an in-app agent is. You chat with it in Base44, or in messaging apps like WhatsApp, Slack, and Telegram (iMessage and LINE followed later in 2026), and it can work on its own — running on a schedule or when something happens in one of your tools.
Concretely, a Superagent is a bundle of four things. Workflows you describe in plain language: the daily inbox summary, the meeting-notes capture, the weekly report pulled from Google Workspace, Notion, and HubSpot. Tool connections set up through plugins: Gmail, Google Calendar, Slack, GitHub, Notion, HubSpot, your CRM — the agent pulls data and triggers actions across all of them. Schedules and triggers: recurring jobs, event-driven runs, responses to things that change in connected apps. Memory: Base44 describes it as persistent — every conversation, preference, and goal carries forward, so the agent gets more useful the longer you work with it.
There is also the smaller cousin: the in-app AI agent, available in every Base44 app and configured through the AI chat. It turns conversations into actions inside one app — updating records, triggering backend functions, answering questions about the app's data — and it can be reached from WhatsApp, Telegram, or LINE channels wired to that app. The distinction matters for migration: an in-app agent is attached to an app project, so it travels with the app's problems. A Superagent is standalone and cross-tool, so it has the same problems multiplied — more connections, more schedules, more memory, and no app project to anchor any of it to.
The migration problem
What breaks when your agents leave Base44
Here is the sentence that surprises people: Base44's export does not contain your agent. The export carries the app's code (via GitHub sync) and its data tables — our export guide walks through exactly what comes out and what never does. What it never carries is the running agent: its schedules, its tool authorizations, its messaging-channel registrations, and its memory. Those live in Base44's agent layer, a platform service with no documented exit path. A Superagent isn't a file you download; it's a configuration living on someone else's runtime.
So what actually breaks, item by item. Tool connections first. Every Gmail, Slack, HubSpot, and GitHub connection your agent uses was authorized through Base44's integrations — the OAuth grants belong to Base44's app registrations, not to you. On new infrastructure, every one of them must be re-granted in your own accounts. No export can carry credentials (and you wouldn't want it to), but the consequence is real: the agent goes blind to your tools until each connection is rebuilt, and each rebuild is a manual authorization, not a bulk import.
Schedules and triggers second. The daily summary, the "when a deal moves stage" trigger, the reminder that fires every Friday — these are jobs configured in Base44's agent runtime. They don't exist in the exported project, so they don't transfer. Each one has to be recreated as a scheduled job on infrastructure you control, with its prompt, its data sources, and its delivery channel re-specified. This is also where the credit meter bites hardest on the way out: scheduled agent runs are platform activity, and you can't tune or export the scheduler — you can only rebuild it elsewhere.
Messaging channels third. If your Superagent answers customers in a WhatsApp group, a Slack channel, or Telegram, that channel is registered through Base44's plumbing — the phone number, the bot identity, the webhook wiring. Moving means re-registering: a new bot connection on your own accounts, the number or channel re-pointed, and your users re-learning where the agent lives. The conversation history in those channels stays in those channels; the agent's side of the memory does not follow.
Memory last, and it hurts most. The preferences, the learned workflows, the "it just knows how I like the report" — Base44's agent memory has no documented export. The new agent starts with amnesia. The mitigation is to migrate the database first: the structured facts the agent learned usually exist as records — clients, preferences, past reports — and those tables do move. A rebuild seeded from the migrated database gives the new agent something to stand on from day one instead of a blank slate. Your data is the one part of the agent that exports cleanly — lead with it.
The way out
How OffRamp rebuilds agent workflows on infrastructure you own
The migration order matters, and it's the reverse of the breakage list above. First the database and the app, onto Supabase, Vercel, and GitHub accounts in your name — the same migration OffRamp runs for every Base44 app, verified live before anything else moves. The database is the agent's long-term memory in structured form, so it leads. Then the tool connections, re-authorized one by one in your own accounts: your Gmail, your Slack workspace, your HubSpot, your GitHub. The agent's new home holds its own credentials from the start — no shared platform registrations, nothing to re-grant if you ever move again.
Then the schedules, recreated as jobs you control on infrastructure you own — the daily summary, the event triggers, the recurring reports, each with its prompt and data sources re-specified against the migrated database. Then the channels: the WhatsApp number, Slack bot, or Telegram connection re-registered to the new host, pointed at the rebuilt agent. Then memory, seeded deliberately from the migrated records instead of accumulated by accident over months — which, honestly, is often an upgrade: you decide what the agent knows on day one instead of inheriting two years of drift.
What you end up with is the same agent surface — chat in the same channels, same scheduled jobs, same tool access — with every dependency held in your own accounts. No platform meter on the agent's activity, no agent runtime you can't export from, no single vendor account whose cancellation would lobotomize your workflows. The agent becomes portable the way the app becomes portable: because nothing it needs lives on someone else's servers. That's the whole OffRamp thesis applied to agents — migrate off Base44 once, and own everything the agent touches.
FAQ
Questions, answered honestly
What is a Base44 Superagent?
A Superagent is a standalone AI agent you describe in plain language: it takes action across your connected tools, files, and memory instead of living inside one app's screens. You chat with it in Base44 or in messaging apps like WhatsApp, Slack, and Telegram, and it can run on its own — on a schedule or when something happens in one of your tools. Base44 launched Superagents in March 2026.
What is the difference between a Base44 Superagent and an in-app AI agent?
An in-app AI agent works inside a single Base44 app — it updates that app's records, triggers its workflows, and answers questions about its data. A Superagent is not tied to one app: it operates across your tools (Google Workspace, Slack, GitHub, Notion, HubSpot), keeps persistent memory across conversations, and reaches you wherever you chat. The migration problem is the same for both, but a Superagent has more of it: more connections, more schedules, more memory.
Can I export my Base44 Superagent?
Not the way you export an app. Base44's export carries code and data tables — it does not carry a running agent's schedules, tool authorizations, messaging-channel registrations, or conversation memory. Those live in Base44's agent layer, not in the app's exported project. Migrating an agent is a rebuild of its connections and configuration on new infrastructure, not a file transfer.
What breaks when I migrate a Base44 AI agent to my own infrastructure?
Four things, in order of annoyance: every tool connection (Gmail, Slack, HubSpot, GitHub) must be re-authorized because OAuth tokens are issued to Base44's integrations; every schedule and trigger must be recreated as jobs on the new host; every messaging channel (your WhatsApp number, Slack bot, Telegram connection) must be re-registered through the new host's plumbing; and the agent's accumulated memory — preferences, context, conversation history — starts over, since there is no documented memory export.
Do I lose my Base44 agent's memory when I leave?
The conversation memory Base44's agent layer accumulates — what it learned about your preferences, workflows, and priorities — does not have a documented export path. Plan to reseed the new agent's memory deliberately: the structured facts usually live in the app's database (which does migrate), so a migration that moves the database first gives the rebuilt agent something to stand on from day one.
How does OffRamp rebuild a Base44 agent workflow on infrastructure I own?
The same way it migrates everything else: onto Supabase, Vercel, and GitHub accounts in your name. The app and its database move first; the agent layer is rebuilt with the same tool connections re-authorized in your own accounts, schedules recreated as jobs you control, messaging channels re-registered to your numbers and bots, and memory seeded from the migrated database. Once verified live, nothing about the agent depends on Base44's account, meter, or agent runtime.
Your agents shouldn't die with your Base44 account.
Rebuild the workflows, schedules, and tool connections on infrastructure you own: migrate your Base44 setup off the platform onto Supabase, Vercel, and GitHub accounts in your name. Connect the Base44 account from the OffRamp home page. The free analysis takes about a minute, and your fixed quote comes with it.
Start your free analysis