Pipedream Workflows shuts down in March 2027: a migration map to n8n
Description and use
Pipedream will shut down on March 31, 2027, requiring migration of automations to n8n. The author offers a step‑by‑step migration plan, including export, conversion, concept mapping, and reusable templates for common business patterns.
Problem
Pipedream Workflows will shut down on March 31, 2027, requiring users to migrate their automations to another platform before data and tokens are deleted on April 30, 2027.
Outcome
Migrating to n8n preserves existing automations while avoiding future shutdown risks, with a clear step‑by‑step checklist and reusable templates for common customer‑operations patterns.
Workflow
- Export all Pipedream workflows before March 31, 2027
- Use the open‑source converter davobene/migrateflows to generate n8n workflow JSON
- Map Pipedream concepts to n8n nodes (e.g., HTTP trigger → Webhook node, Cron → Schedule Trigger, code steps → HTTP Request node with stored credentials, step state → getWorkflowStaticData or database)
- Replace credential‑reading code steps with HTTP Request nodes while the old workflow is still running
- Replace step state with workflow static data or a database with unique constraints
- Stagger schedule triggers to odd minutes to avoid contention
- Dual‑run Pipedream and n8n versions for a week, comparing logs and destinations
- Turn on error notifications to catch silent failures
- Cut over one workflow at a time after confirming parity
Evidence
Pipedream is shutting down Workflows, and String with it, on March 31, 2027.
After April 30, 2027 the data is gone, including the tokens for your connected accounts.
The export is a JSON record per workflow. Nothing imports it directly, n8n included.
An open-source converter exists: davobene/migrateflows. It takes a project export or a GitHub Sync folder and outputs n8n workflow JSON plus a checklist per workflow.
The state row deserves the most respect, because it fails silently.
- Record date: 2026-10-18T05:41:18.937Z