Relay.app Shutting Down: Free Migration Guide to viaSocket (2026)

Relay.app has announced it is shutting down - free accounts on August 15, 2026 and paid accounts on September 14, 2026. New signups and free-to-paid upgrades are already turned off. After each shutdown date, accounts and all associated data are permanently deleted.

If you're a Relay.app user, this guide walks you through exporting your data and rebuilding your workflows in viaSocket before the lights go out.

Don't wait until the last week. A workflow migrated calmly today is one you won't be rebuilding in a panic in September.

viaSocket will move your workflows for you, for free. This is the recommended path if you have more than a couple of workflows or don't want to manually rebuild your automations.

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

2. Share your Relay.app export (see below for what to export).

3. The viaSocket team rebuilds your workflows and connections for you and confirms once they're live.

If you'd rather migrate yourself, follow the steps below.

Relay.app lets you export while your account is still active:

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

• Run history - as CSV

• Tables - as CSV

Your export includes a manifest.json file that summarizes everything you're exporting. For example:

<code>{
  "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
    }
  ]
}
</code>

The manifest.json is just an index — each workflow's actual steps, triggers, and logic live inside its own folder (e.g. workflows/meeting-briefing-generator-.../). Open that folder to see the full workflow definition and the AI-prompt version, which is the easiest reference when rebuilding in viaSocket.

For each workflow in your manifest.json:

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

2. In viaSocket, start from a blank Flow or search Templates for something close to what you're rebuilding — 243+ templates are available and may save you most of the work.

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

4. Reconnect each app under Connections.

5. Use Run flow individually or dry run to test before publishing.

6. Click Publish once it matches your original Relay.app behavior.

• Import table CSVs into viaSocket Databases.

• Keep run history CSVs for your own records — they won't be imported directly, but they're useful if you need to verify past outputs.

Don't want to do this alone? Click Talk to us on viasocket.com and share your Relay.app export - the team will migrate your workflows for you at no cost.