So you’re done with n8n Cloud. Maybe you’ve spun up a self-hosted instance and realized you don’t need to drop money on a monthly subscription anymore. Maybe you’re cutting back on SaaS bloat. Or maybe you just want to see if running the open-source version yourself makes sense for what you’re actually building.
The scary part? When you go to cancel, the immediate panic sets in: Will everything I’ve automated just vanish?
It won’t. This guide walks you through exactly where the cancel button hides, what happens to your workflows when you pull the trigger, and how to back up your automations in about five minutes. No mystery, no trapped data. ⚡
TL;DR: The Quick Version
TL;DR:
- Where to cancel: Admin Panel → Manage → Cancel plan → Type “CANCEL” → Confirm (2 minutes).
- Your workflows don’t disappear immediately: they stay until your billing cycle ends, then the workspace is deleted.
- Backing up is easy: open each workflow, press
Cmd/Ctrl+A, thenCmd/Ctrl+C, and paste into your new instance. - Credentials never transfer: API keys and connections must be recreated and reattached in the new instance.
You’re Not Stuck—Here’s Your Way Out
Canceling n8n Cloud is less about “ending” automation and more about changing where it runs. Whether you’re moving to self-hosted or just pausing paid automation for a while, the key is making sure your workflows and logic come with you.
Your cancellation game plan in one sentence
First back up everything you care about, then cancel, then rebuild your credentials in your new environment at your own pace.
The Cancellation Process (Seriously, It’s Not Hidden)
How to cancel your n8n Cloud plan
- In the left sidebar, click Admin Panel.
- Open the Manage tab at the top of the page.
- Locate your current plan details and click Cancel plan.
- Type CANCEL in the confirmation field when prompted.
- Click Cancel subscription on the final confirmation screen.
- Optionally answer the exit survey, or skip and finish.
What to know before you click
- You are canceling future billing, not instantly deleting your workspace.
- Your workspace remains active until the end of the current billing cycle.
- You can still sign in, access workflows, and migrate during that period.
- After the cycle ends, the workspace is permanently removed.
Think of cancellation as starting a countdown, not pushing a self-destruct button. You still have time to move.
What Actually Happens to Your Data (The Part You Care About)
The confusing part is that after you cancel, everything appears normal—your instance still loads, workflows still exist, and you can still make edits. That’s by design.
What happens immediately after you cancel
- Your workspace is flagged for removal at the end of the current billing cycle.
- Your Manage page shows a yellow warning with a message like: “Set for removal on 22 Dec 2025.”
- You keep full access to workflows, triggers, and settings during this grace period.
- If you change your mind, you can usually resubscribe before deletion and keep everything as-is.
What happens when the billing cycle ends
- The entire workspace is deleted: workflows, credentials, execution history, logs, and configuration.
- There is no built-in “undelete” or archive layer available to end users.
- Customer support may not be able to recover anything once the deletion process completes.
Data retention at a glance
| Data type | Available after cancel? | What you should do |
|---|---|---|
| Workflows & nodes | Yes, until billing cycle ends | Copy each workflow to your new instance before the deletion date. |
| Credentials / API keys | No (not transferable) | Recreate and reconnect credentials in your new instance manually. |
| Execution history & logs | Yes, until deletion | Export or capture any logs you need for audits or debugging. |
| Workspace configuration | Yes, until deletion | Note key environment details, triggers, and integrations before your last day. |
Large Black Text Callout
Your real deadline is not the day you cancel—it’s the day your billing cycle ends and n8n deletes your workspace.
How to Back Up Your Workflows (It’s Borderline Stupid Easy)
n8n’s copy–paste workflow export is one of the simplest migration mechanisms you’ll ever use. No JSON files, no export/import wizards—just your keyboard.
Step-by-step: Copy a workflow from Cloud to self-hosted
- Open the workflow you want to migrate in your n8n Cloud editor.
- Click anywhere on the canvas and press Command+A (Mac) or Ctrl+A (Windows) to select all nodes.
- Press Command+C (Mac) or Ctrl+C (Windows) to copy the selection.
- Watch for the green toast that says “Copied to clipboard.” That means your entire workflow JSON is in your clipboard.
- In your new instance (self-hosted or another Cloud workspace), create a new blank workflow.
- Click the empty canvas and press Command+V (Mac) or Ctrl+V (Windows).
- Confirm that all nodes, connections, and settings render as expected.
Pullquote
Migrating an n8n workflow is literally copy, paste, save. The “hard” part is just reconnecting credentials.
Large Accent Text Callout BLACK BOX WHITE TEXT
Back up more than you think you’ll need. Old experiments and “dead” workflows often become templates that save hours later.
The One Thing That Won’t Transfer (Credentials)
Credentials—API keys, OAuth connections, passwords—are intentionally not bundled into workflow copy–paste. n8n keeps them separate on purpose so you never accidentally leak secrets when sharing or migrating workflows.
What you’ll see after pasting workflows
- Nodes that previously used credentials will often show warnings like “No credential selected for <Service>”.
- The workflow logic, branches, and parameters are intact; only the secure connections are missing.
- Credential dropdowns will be empty until you recreate those credentials in the new environment.
How to reconnect credentials in your new instance
- Open a node that needs access to an external service (for example, Stripe, Gmail, or Slack).
- In the Credentials section, click to create a new credential.
- Enter the required details (API key, OAuth client, service account file, etc.).
- Save the credential, then select it in the node’s credential dropdown.
- Repeat for each external service used by your workflows.
Yellow Warning/Don’t Icon Callout Box
Warning…
Do not store raw API keys in screenshots, shared docs, or chat logs while migrating. Use a safe password manager or secret vault instead.
Before You Cancel: Do This First
Pre-cancellation checklist
- Back up every workflow. Go through each project and copy it to your new instance, even if you’re not sure you’ll need it again.
- Document your credentials. Note which services and auth methods each workflow relies on (for example, “HubSpot OAuth,” “Gmail service account,” “Stripe secret key”).
- Save execution history if required. If you use n8n logs for audits, debugging, or client reports, capture them before deletion.
- Test one full migration. Choose a representative workflow, move it, reconnect credentials, and make sure it runs end-to-end in your new setup.
- Give yourself calendar time. Don’t start this on day 20 of a 21-day window—plan a buffer.
50/50 Boxes
Do
- Schedule migration time before your renewal date.
- Verify each critical workflow after pasting.
- Store secrets in a secure manager, not random notes.
Don’t
- Assume n8n can restore deleted workspaces.
- Rely on memory to rebuild complex credential chains.
- Wait until the last 24 hours to start copying workflows.
Red Critical Warning/error Icon Callout Box
Critical warning!
The deletion is permanent. Once your billing cycle ends, n8n removes your workspace. There is no guarantee that support can recover workflows, logs, or credentials after that point.
Why People Actually Cancel (And Why It Makes Sense)
People rarely cancel n8n Cloud because they dislike the tool. They cancel because their usage pattern changes and the economics shift.
Common reasons for canceling n8n Cloud
- Cost: High or constant automation volume can make a self-hosted instance cheaper, especially if you already pay for servers.
- Control: Some teams want all data, logs, and infrastructure to live within their own environment.
- Compliance: Certain industries need strict control over where automation runs and where data is stored.
- Consolidation: Cutting back on SaaS tools and standardizing on self-hosted stacks.
Large Accent Text Callout ORANGE BOX WHITE TEXT
Canceling Cloud isn’t giving up on automation—it’s choosing where your automation lives and how you pay for it.
FAQ: The Actual Questions People Ask
Frequently asked questions (FAQ)
Practically speaking, no. Once n8n deletes your workspace after the billing period ends, your workflows and data are gone. Always back up while your account is still active.
Yes. When your workspace is deleted, execution logs and history go with it. If you need historical data for audits or debugging, export or capture it before your end date.
Instead of canceling completely, consider downgrading to the Free tier if your automation volume is low. You’ll retain your workspace and workflows without facing deletion, as long as you stay within free limits.
No. Cloud and self-hosted are separate environments. When you copy a workflow from Cloud and paste it into self-hosted, it becomes an independent copy with no ongoing sync between the two.
Copying workflows is fast—often just a few minutes for several workflows. The bigger time investment is recreating and testing credentials. For 5–10 workflows, plan for 30–60 minutes; for dozens, set aside a dedicated session.
Green Success/Accepted/Complete/Done Icon Callout Box
Success!
If you can open it, you can migrate it. As long as your workspace is still active, every workflow is just a copy–paste away from living in your new environment.
Final Thought: Canceling Isn’t Giving Up
Canceling your n8n Cloud subscription doesn’t mean you’re abandoning workflow automation. It usually means you’ve grown enough to decide how and where your automations should run—on managed infrastructure or on your own stack.
Large Accent Text Callout
The real decision isn’t “Cloud vs. no automation.” It’s “Do I want to pay for hosted infrastructure, or manage the servers myself?”
Large Accent Text Callout BLACK BOX WHITE TEXT
Once you’ve copied your workflows and rebuilt credentials, you’re free to experiment, optimize costs, and scale automation on your own terms.
Large Accent Text Callout ORANGE BOX WHITE TEXT
Give yourself time, follow the checklist, and your “goodbye” to n8n Cloud will feel more like a clean handoff than a risky leap.
