Pipedream data deletion: what to back up before April 30, 2027

Pipedream's data deletion deadline is April 30, 2027. By that date, according to Pipedream's Workflows notice, all Workflows data is permanently deleted, including the credentials and OAuth tokens of connected accounts. Workflows stop running a month earlier, on March 31, 2027. The export ZIP covers only part of your data, so use the checklist below to back up the rest.

Timeline

Date	Event
Now	Workspaces run normally; no new sign-ups or subscriptions
March 31, 2027	Workflows and String shut down
By April 30, 2027	All Workflows data permanently deleted

Connect (Connect API, MCP Servers, API Proxy) is not affected, and Pipedream says Connect settings and credentials are not deleted.

Don't plan to export in April 2027. Once workflows stop, you are counting on an export path still being available in a workspace that no longer runs. Do it while everything works.

Backup checklist

Data	In the export ZIP?	How to back it up
Workflow definitions (triggers, steps, branches)	Yes	Project → Settings → Export Workflows, download from File Store
Code of code steps	Yes	Included in the workflow JSON
Never-deployed workflows	No (skipped_never_deployed)	Deploy them before exporting, or copy the code
Workflows over 500 / 256 MB	No (skipped_export_limit)	Move them to another project and export it
Environment variables	No	Copy non-secret values from Settings → Environment Variables and each project's Variables; secret values are never shown, so get them from the provider or rotate them
Secret prop values	No (<redacted>)	Get them from the original source (the provider's dashboard) or rotate them
Connected accounts and OAuth tokens	No	Reconnect each app on the new platform
Data store records	No	Export with a code step (see below)
File Store files	No	Download from the project's File Store
Event history	No	There is no export; copy by hand what you need for audits or debugging
Private multi-file component code	Key only	Keep your own copy of the source

Source for every "No": Pipedream's export documentation.

Environment variables and secrets

Pipedream environment variables are set at workspace level (Settings → Environment Variables) or project level (Variables). New variables default to secret, and secret values are never shown again in the UI. If you don't have the original values, regenerate the keys at the provider (Stripe, OpenAI, your database) and store the new ones on the new platform. Rotating keys during a migration is good practice anyway.

Data store records

Data stores have no export button. Pipedream's docs show a sample Node.js action that reads records and posts them in chunks to an external endpoint. By default that sample deletes the keys it exported (its "delete keys after export" option is on); turn the option off for a non-destructive copy.

A minimal read-only alternative is a code step that returns all records:

export default defineComponent({
  props: { data: { type: "data_store" } },
  async run() {
    const out = {};
    for await (const [key, value] of this.data) out[key] = value;
    return out;
  },
});

Run it once with a test event and copy the JSON from the step's result. For large stores, the 6 MB limit on step exports and logs applies (limits), so post the records to your own storage in chunks instead. In n8n, the destination is usually a Data table; see Pipedream data stores to n8n.

File Store files

File Stores are project-scoped storage, available on Advanced plans and above. The export ZIP itself lands there. Open File Store in the project navigation and download every file you need, not only the export.

After the backup

With the export ZIP and the rest of the data saved, you can migrate at your own pace until March 31, 2027. The migration guide covers moving to n8n. Our free report reads the ZIP in your browser, and lists the credentials and data stores each workflow needs. The report and 1 workflow are free. Full export: $3 per workflow, $19 minimum — coming soon. See pricing.

moveworkflows is not affiliated with Pipedream or n8n.