Relay.app → Make migration
Relay Rescue reads a Relay workspace export locally, inventories its automation building blocks, and creates a Make-focused rebuild packet. It helps you understand the work before you recreate modules and connections.
Preserve the source, translate its structure, and prove each scenario with representative data before switching it on.
Download the complete Relay workspace archive and keep an untouched copy for reference.
Use Relay Rescue to identify workflows, sequences, tables, prompts, apps, branches, and missing files.
Use the generated prompt to recreate modules, routes, filters, iterators, data stores, and connections.
Compare outputs, review operation usage, test incomplete data and errors, then schedule the cutover.
The right Make modules depend on each integration. Treat these as reconstruction clues, not an automatic conversion.
| Relay concept | Likely Make building block | What to verify |
|---|---|---|
| Workflow trigger | Instant webhook, scheduled trigger, or watch module | Scheduling interval, webhook payload, starting point, and duplicate runs |
| App action | App module or HTTP module | Connection permissions, field mapping, pagination, and API limits |
| Paths and conditions | Router with route filters | Route order, fallback route, mutually exclusive conditions, and empty values |
| Loop or list work | Iterator and aggregator patterns | Bundle shape, aggregation boundaries, rate limits, and partial failures |
| Reusable sequence | Subscenario or callable scenario pattern | Inputs, outputs, shared connections, and error propagation |
| Relay table | Make Data Store or external database | Key choice, record schema, retention, and concurrent changes |
Make is often attractive when visual data mapping and scenario inspection matter to the team doing the migration.
Important: Relay exports are not Make blueprints. Relay Rescue gives you a redacted audit and rebuild packet; every scenario still requires configuration and behavioral testing.
The short answers before you start rebuilding.
No. A Relay workspace export is not a Make blueprint. Relay Rescue extracts a neutral inventory and generates a Make-oriented rebuild plan instead.
No. The ZIP is processed in the current browser tab. Workspace contents and generated packets are not uploaded.
No. Destination connections must be authorized again. Confirm the correct account, permissions, region, and owner for every scenario.
Rebuild and test a representative scenario first. Inspect how many modules execute per run, including iterated bundles and error paths, then project from actual run volume.
Run the free local audit first. If you want help with destination fit, risk review, and rebuild order, add the optional $99 migration-planning call. The $99 is credited toward an assisted rebuild if you continue.
support@relayrescue.app · Opens an email draft, not a booking or payment. Include your time zone and destination; do not send exports, credentials, packets, or customer data. No obligation to purchase rebuild services.