Migration snapshot
DecliningPlatform
a Pipedream
Workday announced a definitive acquisition agreement on Nov 18–19, 2025, expected to close by Jan 31, 2026. Pipedream still operates under its own brand; roadmap and pricing are Workday's to decide post-close. Source-available license (Jan 3, 2022) means no community fork if Workday sunsets the product.
Typical timeline
6–10 weeks
Typical cost
$13K–$25K (agency, fixed)
Why teams leave a Pipedream
The Workday acquisition makes Pipedream a medium-risk dependency. Enterprise-software acquirers historically raise prices and narrow product scope within 12–18 months of close.
Acquisition risk
Workday announced the acquihire Nov 18–19, 2025 (expected close Jan 31, 2026). Consumer tiers may be retired, pricing restructured, or Pipedream integrated exclusively into Workday Extend — all outside your control.
No self-host option
Pipedream is cloud-only. GitHub issue #954 requesting self-hosting has been open since launch and remains unresolved — this is a hard blocker for HIPAA or data-residency compliance.
Source-available ≠ open source
The component license changed to the proprietary Pipedream Source Available License on Jan 3, 2022. There is no ability to fork the runtime or run it independently if Workday sunsets the product.
Workflow portability is false comfort
Workflow steps are written in Node.js, Python, Go, or Bash — but they run exclusively in Pipedream's cloud. The step code is readable; the runtime cannot be ejected to any other platform.
3,000+ connectors become a liability
Deep connector dependency creates complex migration planning. Each replaced connector requires its own OAuth setup, testing, and monitoring configuration on the destination stack.
What can you actually take with you?
Workflow step code is exportable via GitHub sync. Pipedream's runtime, trigger definitions, managed OAuth tokens, and execution history are not portable outside Pipedream's cloud.
| Asset | Can you export it? | How | Notes |
|---|---|---|---|
| Data | Partial | Source and destination data lives in your connected SaaS systems, not in Pipedream. Trigger/event payloads and step result logs are viewable in the Pipedream UI. | Execution logs are not documented as bulk-exportable; no CSV or API export of full execution history. |
| Code | Partial | Workflow step code (Node.js, Python, Go, Bash) is readable in the UI and syncs to a connected GitHub repo. Enable GitHub sync in Settings and export step code to your repo today. | No self-host runtime — code cannot run outside Pipedream's cloud even after export. Trigger definitions use Pipedream-specific component format that does not run elsewhere. |
| Design/UI | No | Not applicable — Pipedream is a workflow automation platform with no app UI. | N/A |
| Logic/Workflows | Partial | Step-level code is portable as a reference for rebuilding. Trigger definitions (event sources) use Pipedream's proprietary component SDK and have no equivalent drop-in elsewhere. | 3,000+ pre-built connectors have no direct equivalent on other platforms; each must be replaced individually. |
| Users & Auth | No | Pipedream manages platform auth. Connected OAuth tokens live in Pipedream's secret store. | OAuth tokens are not documented as exportable; all connected app authorizations must be re-established on the new system. |
Swipe the table sideways to see the full breakdown.
Where each piece moves in code
The target stack is Next.js + Supabase/PostgreSQL, replacing Pipedream's managed cloud runtime with standard serverless infrastructure.
a Pipedream
Trigger (HTTP/webhook)
In code
Next.js Route Handler (app/api/webhook/route.ts)
Implement the same signature validation the source system requires; add HMAC verification.
a Pipedream
Trigger (schedule/cron)
In code
Vercel Cron Jobs (vercel.json) or pg_cron in Supabase
Match original schedule exactly; document timezone; evaluate drift tolerance before choosing.
a Pipedream
Step (Node.js/Python code)
In code
Next.js Server Action or Vercel Serverless Function
Copy business logic directly; replace all $auth references with environment variables.
a Pipedream
Connected app (OAuth)
In code
Supabase Vault or server-side environment variables
Re-authorize each OAuth app for the new runtime; document all scopes before starting.
a Pipedream
Data store (key-value)
In code
Supabase table or Upstash Redis
Map key-value pairs to a typed schema; migrate data contents before cutover.
a Pipedream
Event source (polling)
In code
Supabase Edge Function on schedule
Replicate polling interval and add deduplication on the id field to avoid duplicate processing.
a Pipedream
Workflow branching
In code
TypeScript if/switch in a Next.js Server Action
Straightforward code translation; Pipedream branch logic is standard conditional control flow.
The migration roadmap
The migration has four phases. Begin with code extraction and inventory — this phase determines the scope and flags blockers before any code is written.
Phase 1: Extraction & Inventory
1 week- Enable GitHub sync in Pipedream settings; export all workflow step code to your repo
- List every connected app, its OAuth scopes, and the business owner of each credential
- Document all cron triggers with exact schedules and expected execution counts per month
- Identify any workflows using Pipedream-specific event sources (not webhook/cron) — these need full rewrites
- Map each Pipedream data store to its target Supabase table schema
Watch out: Connectors with no first-party API (only a Pipedream-managed OAuth wrapper) require building a new OAuth flow from scratch — flag these as high-effort items.
Phase 2: Infrastructure Foundation
1–2 weeks- Set up Next.js project with Supabase connection and Vercel deployment pipeline
- Configure Supabase Vault for secrets management; do not use plain environment variables for OAuth tokens
- Implement queue and retry infrastructure (Vercel Queue, Upstash QStash, or BullMQ) — do not defer
- Establish logging and alerting baseline (Sentry or Datadog) before any workflow goes live
Phase 3: Workflow Migration
3–5 weeks- Port step code workflow by workflow, starting with highest-frequency or most business-critical
- Re-authorize each OAuth connected app for the new runtime; test each before proceeding
- Implement webhook Route Handlers and update external services with new endpoint URLs
- Replace Pipedream data stores with Supabase tables; migrate data before switching
- Run old and new workflows in parallel during this phase using Pipedream inspect logs for comparison
Watch out: Event sources using Pipedream's proprietary component SDK need complete rewrites — no code reuse possible.
Phase 4: Cutover & Decommission
1 week- Validate output parity between old Pipedream workflows and new system for one full cycle
- Disable Pipedream workflows one by one after confirming new equivalents are stable
- Set a calendar reminder at first Workday contract renewal to confirm migration is complete
- Document the new stack architecture for team onboarding
Three ways to migrate — honestly
Every path has a real trade-off. Here is what each costs, how long it takes, and where it bites.
DIY (with AI tools)
$0–$500 + time
3–6 months part-time
Fits
Teams with Node.js/TypeScript capacity who have already enabled GitHub sync and have clean step code ready to port.
Risks
Queue and retry infrastructure is the hardest part — most DIY migrations underestimate this. OAuth re-authorization for 10+ connectors is time-consuming. Acquisition risk means the window may narrow unexpectedly.
Freelancer
$3K–$10K
1–3 months
Fits
Teams with fewer than 20 workflows and a manageable connector footprint. Works best when step code is already in GitHub.
Risks
Freelancers rarely implement production-grade retry/dead-letter queues without explicit specification. Ensure scope includes full queue infrastructure, not just code porting.
Agency (RapidDev)
Done-for-you$13K–$25K fixed
6–10 weeks
Fits
Teams with 20+ workflows, complex connector dependencies, or compliance requirements (HIPAA, data residency) who cannot afford migration gaps.
Risks
Minimal — fixed price covers full workflow audit, queue infrastructure, connector re-authorization, parallel running, and cutover. Free scoping call available at rapidevelopers.com.
The real risks — and how to defuse them
Workday roadmap divergence
Mitigation: Workday may retire consumer tiers, raise pricing, or integrate Pipedream exclusively into Workday Extend. Set a decision checkpoint at the first post-close pricing communication; start migration planning now.
OAuth token loss on migration
Mitigation: Pipedream stores OAuth tokens for 3,000+ connectors in its secret store; they are not documented as exportable. Document all connected apps and their scopes before starting; schedule re-authorization sessions with credential owners.
Connector parity gap
Mitigation: Some Pipedream-managed connectors (niche SaaS) may have no maintained SDK or webhook support. Audit the connector list in Phase 1 and plan custom integrations for any gaps before committing to a migration timeline.
Queue and retry re-implementation
Mitigation: Pipedream handles retries, error capture, and dead-letter automatically. Use a managed queue (Vercel Queue, Upstash QStash) rather than rolling a custom solution — this is not optional infrastructure.
Testing coverage on event-driven logic
Mitigation: Trigger-based workflows are hard to test locally. Use Pipedream's inspect logs during the parallel-running period to compare outputs and validate parity before cutover.
Should you actually migrate?
Migrating is a real project. Sometimes staying is the right call — here is the honest split.
Stay if
- Your workflows are low-volume (under 500 executions per day) and the Workday roadmap preserves your tier pricing at renewal
- You depend on 10+ niche Pipedream-managed connectors with no easy alternative — rebuilding those integrations would cost more than staying for 12 months
- Your team has zero Node.js or Python capacity and cannot maintain a self-hosted queue; Pipedream's managed reliability is genuinely valuable
Migrate if
- Workday raises pricing or alters the product scope post-close in a way that conflicts with your use case
- You need self-hosting for compliance reasons (HIPAA, data residency) — Pipedream's cloud-only model is a hard blocker
- Your workflows contain critical business logic that you cannot afford to cede to an enterprise acquirer's roadmap
Our honest verdict
No emergency today, but the acquisition makes Pipedream a medium-risk dependency. Start an inventory and migration plan now; execute on the first post-close pricing signal or roadmap change.
Do this today: pre-migration checklist
Whatever path you choose, protect yourself first. Work through this before you touch a line of code.
Enable GitHub sync in Pipedream Settings and export all workflow step code to your repo today
This is the only bulk-export path; if Workday changes account access before you act, this code may become inaccessible.
List every connected app, its OAuth scopes, and the business owner of each credential
OAuth tokens cannot be exported; you need this inventory to re-authorize every integration in the new system.
Document all cron triggers with their exact schedules and expected execution counts per month
Schedule specifications are not machine-exportable; documentation is the only migration artifact for triggers.
Map each Pipedream data store key-value pair to its target Supabase table schema
Data stores are a proprietary Pipedream feature with no export API documented; schema mapping must be done manually.
Identify any workflows using Pipedream-specific event sources (not webhook or cron) — these need full rewrites
Event sources use Pipedream's proprietary component SDK and cannot be ported; they require a rebuild estimate separately.
Set a calendar reminder at the first Workday contract renewal to re-evaluate pricing vs. migration cost
The acquisition risk is real but not yet realized; the renewal moment is when Workday's intentions become concrete.
Frequently asked questions
Can I export my Pipedream workflow code?
Partially. If you enable GitHub sync in Pipedream Settings, your workflow step code (Node.js, Python, Go, or Bash) syncs to a GitHub repository you own. What you cannot export is the runtime: Pipedream's event queues, trigger system, and concurrency model run exclusively in Pipedream's cloud and have no self-hosted equivalent.
Is Pipedream shutting down?
There is no shutdown notice as of July 2026. Workday announced a definitive acquisition agreement on Nov 18–19, 2025 (expected close by Jan 31, 2026). Pipedream continues operating under its own brand. The risk is not imminent shutdown but enterprise-acquirer pricing and product-scope changes within 12–18 months of close.
What happens to my OAuth-connected apps when I migrate?
Pipedream's OAuth tokens for connected apps are stored in Pipedream's secret store and are not documented as exportable. Every connected app (Slack, HubSpot, Shopify, etc.) must be re-authorized for the new system. Document all connected apps and their OAuth scopes before starting migration — this inventory drives Phase 2.
How long does a Pipedream migration take?
Typically 6–10 weeks end-to-end for teams with 10–30 workflows. The largest variables are the number of Pipedream-specific event sources (which require full rewrites), the connector count, and whether step code is already in GitHub. Complex setups with 50+ workflows or niche connectors may run 12–14 weeks.
Can I self-host the Pipedream runtime after migrating the code?
No. The Pipedream Source Available License (effective Jan 3, 2022) is proprietary — not open source. There is no self-hostable runtime. Migrating off Pipedream means rebuilding workflow execution on a standard stack (Vercel Functions, Supabase Edge Functions, and a managed queue like Upstash QStash).
What replaces Pipedream's 3,000+ pre-built connectors?
There is no direct drop-in. Each connector is replaced by the target SaaS platform's own SDK or REST API. Common replacements: Slack SDK, HubSpot API client, Shopify API, Stripe SDK. Niche connectors with no maintained SDK require a custom OAuth integration or a lighter automation layer (n8n, Make) for that specific connector.
How much does a Pipedream migration cost?
DIY (if step code is in GitHub and your team has TypeScript capacity): effectively zero in software cost, 2–4 weeks of developer time. Freelancer: $3K–$10K for straightforward workflow sets. Agency fixed-price engagement: $13K–$25K covering full audit, queue infrastructure, connector re-authorization, and cutover. RapidDev offers a free scoping call to size the effort at rapidevelopers.com.
Should I migrate now or wait to see what Workday does?
Start the inventory now regardless. Enabling GitHub sync and documenting connected apps costs a few hours and protects you if Workday makes an adverse move at renewal. The actual migration can wait until the first post-close pricing communication gives you a concrete signal. Do not wait past the first renewal without a plan.
We migrate no-code apps to production code
- Fixed price — $13K–$25K (agency, fixed)
- No data loss, no downtime
- You own 100% of the code
30-min call. Quote within 48 hours.