Relay.app Is Shutting Down: Here's How to Export Your Data and Migrate Before It's Gone

Relay.app has confirmed it is shutting down, and the countdown has already started. New signups and free-to-paid upgrades are disabled. Once the shutdown dates hit, every workflow, connection, run history log, and table gets permanently deleted - no recovery, no grace period.

If you run automations on Relay.app, this is not a "someday" task. This is a "do it this week" task.

Here's everything you need to know: the exact dates, what to export, how to rebuild in a new tool, and the fastest way to do it without touching a single line of config yourself.

A workflow you migrate calmly today is one you won't be scrambling to rebuild from memory in September.

This isn't a feature deprecation or a pricing change — it's a full platform shutdown. That means the usual "wait and see" approach doesn't apply. Every team currently on Relay.app falls into one of three buckets:

• Free users with a hard deadline of August 15, 2026

• Paid users with a slightly longer runway to September 14, 2026

• Teams with MCP servers, AI agents, or multi-step sequences that took real time to build and are painful to lose

Whichever bucket you're in, the underlying problem is the same: your automations, your connections, and your run history all live inside an account that has an expiration date now.

Once the shutdown date for your account type passes, Relay.app deletes:

• All workflows and sequences

• All MCP server configurations

• All app connections

• All run history

• All tables

There is no stated recovery window after deletion. If you haven't exported by your account's date, that data is gone.

While your Relay.app account is still active, you can export:

• Workflows, sequences, and MCP servers — as JSON and as plain-language AI prompts

• Run history — as CSV

• Tables — as CSV

Your export comes with a manifest.json file that acts as an index of everything you're pulling out. It looks roughly like this:

{...}{
  "generatedAt": "2026-07-17T07:22:52.541+00:00",
  "workspaceId": "cml4rxlp033y50pm0dv9bf1k2",
  "workflowCount": 1,
  "runCount": 0,
  "tableCount": 0,
  "workflows": [
    {
      "templateId": "cml4s0g7434dd0pm0gx955xx9",
      "name": "Meeting Briefing Generator",
      "folder": "workflows/meeting-briefing-generator-cml4s0g7434dd0pm0gx955xx9",
      "runCount": 0
    }
  ]
}

The manifest is just the table of contents. Each workflow's actual steps, triggers, and logic live inside its own folder — that's where you'll find both the raw JSON and the plain-language AI-prompt version, which is usually the easier reference when you sit down to rebuild.

Once your export is in hand, you need somewhere to rebuild. viaSocket is a direct like-for-like landing spot for Relay.app users, because nearly every core Relay.app concept maps cleanly onto something that already exists in viaSocket:

With 2,200+ integrations, most Relay.app connections already have a direct equivalent inside viaSocket. Check Explore Apps on viasocket.com first — and if something's genuinely missing, Contact Sales can flag it for a build.

For every workflow listed in your manifest.json:

• Open its folder and read the JSON or the AI-prompt version to see the full trigger → action sequence.

• In viaSocket, start from a blank Flow, or check Templates first — with 243+ templates already built, there's a decent chance something close to your original workflow already exists and saves you most of the rebuild.

• Recreate the trigger, then rebuild each action step, matching the app and logic from your export.

• Reconnect each app under Connections.

• Use Run flow individually or a dry run to test before it goes live.

• Click Publish once behavior matches your original Relay.app workflow.

• Import your table CSVs directly into viaSocket Databases.

• Keep your run history CSVs on hand for your own records — they aren't imported directly, but they're useful if you ever need to verify what a past run actually did.

If you have more than a couple of workflows, or simply don't want to manually rebuild each one, viaSocket will migrate everything for you — for free:

1. Go to viasocket.com and click Talk to us in the top banner.

2. Share your Relay.app export.

3. The viaSocket team rebuilds your workflows and connections, and confirms once everything is live.

No cost, no manual rebuilding, no risk of missing a step buried in an old sequence.

If you're evaluating options rather than defaulting to the first alternative you find, the questions that actually matter are:

• Does it support the apps I'm already connected to? viaSocket covers 2,200+ integrations, which covers the large majority of what Relay.app users had connected.

• Can I reuse what I already built instead of starting from zero? viaSocket's AI Agent setup accepts your exported Relay.app prompt directly as a starting point, and 243+ ready-made templates can shortcut common workflows.

• Does migration require an engineer? With the concierge option, it doesn't — you hand over your export and the team rebuilds it.

• Can I test before I fully commit? Yes — you can rebuild and dry-run a Flow in viaSocket while your existing Relay.app workflow keeps running in parallel, and only cut over once you've verified the output matches.

For teams that just want their automations running again with minimal disruption, that combination — broad app coverage, reusable AI prompts, ready templates, and a free hands-on migration path — is the practical deciding factor over rebuilding from scratch on a different platform.

Is there a cost to migrate?

The concierge migration, where viaSocket rebuilds your workflows for you, is free.

Will my Relay.app data still be there if I wait?

Only until your account's shutdown date - August 15, 2026 for free accounts, September 14, 2026 for paid accounts. After that, it's permanently deleted.

What if I have workflows using apps viaSocket doesn't support?

Check Explore Apps on viasocket.com. With 2,200+ integrations, most Relay.app connections have a direct equivalent. If not, reach out via Contact Sales.

Can I test before fully switching over?

Yes. Rebuild and dry-run a Flow in viaSocket while your Relay.app workflow keeps running, then cut over once you've verified it.

Every week you wait is a week closer to your data being gone for good. Whether you rebuild it yourself using the mapping above or hand it off through the free concierge migration, the priority right now is simple: get your export done while Relay.app is still live.