Before anything else: get your export
Relay deletes free accounts and their data after August 15, 2026, and paid accounts after September 14, 2026. The export is the only thing with a hard deadline, so do it first: in Relay, choose Export workspace data, wait for the email (generation can take up to 24 hours), and download the zip within 48 hours of receiving the link. Full details are in our shutdown explainer.
The four steps
Download the full workspace zip. Per workflow you get a prompt.md (plain-language description), a workflow.json (exact structure), and run history CSVs. Keep all of it.
Read each prompt.md and write one line: what did this workflow actually produce? An invoice, a follow-up email, an order update, a payment reminder. The outcome is what you migrate; the steps were just Relay’s way of getting there.
Join early access and connect the tools those workflows touched: Gmail, QuickBooks, Shopify, Stripe, and the rest. Connections start read only, so nothing can send while you set up.
Run flo.space read only for a few days and compare its prepared actions against your Relay run history CSVs. When the approval queue is proposing the right work, approve your first action.
How Relay concepts map to flo.space
| Relay.app concept | flo.space equivalent | Notes |
|---|---|---|
| Workflow | A recurring prepared action | You do not build it; the AI proposes it from your connected tools |
| Trigger (new email, new row, schedule) | Context flo.space watches in your tools | Read only until an action is approved |
| Human approval step | The approval queue, on every action | The part that maps one to one |
| AI steps (draft, summarize, extract) | The prepared draft, with reasoning and sources shown | Editable in plain language before approving |
| Paths, branches, loops | No direct equivalent | Keep genuinely branchy pipelines in a workflow builder |
| Tables | Your existing sheets and systems | flo.space reads Google Sheets rather than hosting tables |
| App connections (~100+ apps) | 14 deep integrations | Outside the 14, use Zapier, Make, or n8n for that workflow |
| Run history | Action history and audit trail | Every proposal, edit, and approval is recorded |
What does not map cleanly
- Custom multi-step pipelines with branching logic. flo.space is not a workflow builder; if the logic itself was the point, a builder remains the right tool.
- Apps outside the 14 supported tools. We would rather say so here than have you discover it mid-migration.
- Fully unattended workflows. Relay allowed steps with no approval; flo.space intentionally does not. If zero-touch execution is a requirement, flo.space is the wrong choice, and we say the same on the comparison page.
Hands-on help for Relay users
During early access, Relay migrations get a working session with the team: bring the prompt.md and workflow.json files from your export, and we go through them together, configure the matching prepared actions, and flag anything that belongs in a different tool. Book it through the contact page and mention Relay, or join early access and raise it in onboarding. The step-by-step technical reference lives at docs: migrating from Relay.app.
Migration questions
You need to EXPORT before your deadline: August 15, 2026 for free accounts, September 14, 2026 for paid. Once you have the zip downloaded, the rebuild itself has no deadline, because everything needed lives in the export. Export first, migrate calmly second.
No, and not just here: Relay states that its workflow JSON does not transfer directly into any other tool. During flo.space early access onboarding we work from your prompt.md and workflow.json files and configure equivalent approval-gated actions with you. It is hands-on rather than one-click, and it is honest.
flo.space connects to 14 business tools: Gmail, Outlook, QuickBooks, Stripe, Shopify, Slack, HubSpot, Salesforce, Google Drive, Google Sheets, ShipStation, Twilio, DocuSign, and LinkedIn. If a workflow depends on an app outside that list, keep that workflow in a general-purpose builder like Zapier, Make, or n8n. Splitting your workflows across two tools is a normal outcome, not a failure.
Conceptually, yes, and this is the part that maps best. Every action flo.space prepares waits for human approval; riskier actions, like large payments or contract sends, are flagged high risk. You do not rebuild approval steps because approval is not a step here, it is the default for everything.
For the common case, a handful of communication workflows, plan for one onboarding call plus a week of running flo.space read only while you compare its prepared actions against what Relay used to do. Complex workspaces take longer to audit than to rebuild.
Bring your Relay export to onboarding
Connect your tools read only, see the first prepared actions in your queue, and keep the approval step that made Relay worth using. Nothing sends until you approve it.