Relay.app → Make migration
If you saved a Relay workspace export before access ended, Relay Rescue can inspect it locally and create a Make-focused rebuild packet. If you have no export, start with the recovery guide and reconstruct the workflow from other evidence.
After shutdown: Relay Rescue cannot obtain a new Relay export or recover deleted account data. Work only from files and other evidence you already saved.
Preserve the source, translate its structure, and prove each scenario with representative data before switching it on.
Keep an untouched copy of any saved Relay ZIP. Without one, gather screenshots, app histories, schedules, webhook callers, and team notes.
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.
Use the packet's validation checklist to record normal, branch, bad-input, and failure results before enabling a replacement.
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.
Make support: Make's published Relay migration offer said free white-glove help was available to eligible accounts through September 14, 2026. That window has passed; do not assume the offer or its AI-building tools are available to your account. Ask Make directly about current support before choosing a paid service.
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.
No. The included validation checklist is blank until you compare real source evidence with actual Make runs, record the results, and have an owner approve activation.
Start with a free local audit and migration packet. The optional $9 Automation Rebuild Kit adds an offline workbook, destination checklists, and editable test and rollback templates. No call or subscription.
Optional support is not connected yet.
Do not send exports, credentials, packets, or customer data. The kit is not a working importer or account recovery service.