# Migrating from Self-Hosting to N8Nitro Cloud — What to Expect > Step-by-step guide for migrating from self-hosted n8n to N8Nitro Cloud. Learn how to move workflows, credentials, and domains with zero downtime. - Source: https://n8nitro.com/blog/migrate-to-n8nitro-cloud - Published: 2025-01-22 - Updated: 2026-10-11 - Category: Best Practices - Reading time: 10 min read - Publisher: N8Nitro (https://n8nitro.com) **Quick answer:** To migrate from self-hosted n8n to N8Nitro: export your workflows (JSON) and credentials, back up your environment variables, create a Nitro, import the workflows and credentials, update webhook URLs, test each critical workflow, then switch off the old server once everything passes. You can also map your own domain to the Nitro. A practical migration checklist for faster performance, higher uptime, and zero DevOps overhead. --- ## Introduction If you've been self-hosting your n8n instance, you already know the trade-offs: flexibility and control come at the cost of maintenance, scaling headaches, and constant monitoring. As your workflows grow, those small inefficiencies start to multiply — CPU spikes, memory exhaustion, broken Docker containers, or unexpected downtime during updates. N8Nitro Cloud eliminates all of that. It gives you instant n8n hosting with auto-scaling, 99.99% uptime monitoring, and zero DevOps setup, so you can focus on building workflows, not babysitting servers. In this post, we'll walk you through what to expect when migrating from self-hosting to N8Nitro, what changes (and what doesn't), and how to make the transition seamlessly — without losing a single workflow. ## Why Move to N8Nitro Cloud? Before diving into the migration steps, let's understand what you gain: ### 1. Instant Performance Boost Self-hosted setups are limited by your chosen VM or Docker resource allocation. N8Nitro dynamically scales between 2–8 CPU cores and 4–16 GB RAM per instance — automatically. No more manual tuning, restarting containers, or provisioning new servers. ### 2. Zero Maintenance Forget about: - OS updates - Docker patching - SSL renewals - Database migrations - Monitoring uptime manually All of that is handled by the N8Nitro platform. You focus solely on building automations. ### 3. Enterprise-Grade Security Every instance runs in an isolated environment with encrypted credentials, SSL by default, and optional Cloudflare tunnel protection. No shared resources, no credential leaks. ### 4. Predictable Billing Flat pricing tiers based on performance and usage. You only pay for what you need — not for idle resources sitting in your VM. ### 5. Seamless Scaling Traffic spikes or heavy workflows? N8Nitro scales automatically, then scales back down when idle — saving you time and cost. ## Migration Overview Migrating from self-hosting to N8Nitro Cloud is a straightforward three-stage process: 1. Export your workflows and credentials 2. Create your new N8Nitro instance 3. Import, test, and go live Let's break it down step-by-step. ## Step 1 — Export Your Workflows In your existing n8n instance: 1. Go to Workflows → All Workflows 2. Click Download Backup or Export (you can export individually or bulk). 3. This will generate a .json file for each workflow. To export credentials securely: - Navigate to Settings → Credentials - Choose Export Encrypted Credentials - Store this file safely (you'll re-import it later). **Tip:** If your instance uses environment variables (.env file), back them up too — you'll recreate them inside N8Nitro later. ## Step 2 — Create a New N8Nitro Instance 1. Log in to your N8Nitro Dashboard. 2. Click Start Your Nitro. 3. Choose your instance name and region. 4. Pick a plan (Monthly or Yearly — yearly billing saves about 15%). 5. Deploy your instance. Within seconds, your new n8n environment will be live, complete with: - SSL certificate - Auto-scaling - Built-in monitoring and analytics - One-click dashboard access You'll receive your unique dashboard URL, e.g. https://yourname.apps.n8nitro.com ## Step 3 — Import Workflows & Credentials Once your Nitro instance is running: 1. Open the n8n Dashboard → Workflows → Import 2. Upload your exported .json workflow files. 3. Repeat for credentials: Settings → Credentials → Import Encrypted File 4. Add your saved .env variables under Environment Settings. **Pro Tip:** You can also connect directly to Supabase or Postgres if you're migrating data workflows — N8Nitro supports native DB connectors. ## Step 4 — Verify Integrations and APIs Check that all external APIs, webhooks, and credentials are working: - Run a test execution for each critical workflow. - Confirm that webhook URLs now match your new domain (.apps.n8nitro.com). - Update any third-party services (e.g., Stripe, Slack, or Webflow) with the new endpoint URLs. **Note:** N8Nitro automatically manages SSL and port configuration — you no longer need to open or forward ports manually. ## Step 5 — Enable Auto-Scaling and Monitoring Your instance already scales automatically, but you can customize behavior from the N8Nitro dashboard. - Monitor usage: View CPU, memory, and execution count in real-time. - Adjust scaling thresholds: If you're running large automations, increase your scaling floor (e.g., from 1 core to 2). - Enable Alerts: Get notified if a workflow fails or CPU exceeds a threshold. This visibility is built-in — no third-party monitoring tools needed. ## Step 6 — Test, Validate, and Go Live Before switching off your self-hosted server: 1. Test all critical workflows (especially those with time triggers). 2. Check file uploads, email integrations, and database actions. 3. Compare execution speed — most users see a 30–60% faster runtime due to N8Nitro's optimized infrastructure. 4. Once everything passes, disable your old instance. That's it — you're now live on the N8Nitro Cloud. ⚡ ## Optional: Set Up Custom Domain You can map your custom domain (like automation.yourbrand.com) to your N8Nitro instance. 1. Go to your Nitro Settings → Domain 2. Add your custom domain 3. Update DNS records as instructed 4. N8Nitro automatically provisions the SSL certificate Your instance is now fully branded and production-ready. ## Migration Checklist | Step | Task | Status | | --- | --- | --- | | 1 | Export all workflows as JSON | ☐ | | 2 | Export encrypted credentials | ☐ | | 3 | Back up .env variables | ☐ | | 4 | Deploy N8Nitro instance | ☐ | | 5 | Import workflows and credentials | ☐ | | 6 | Update API/webhook URLs | ☐ | | 7 | Enable monitoring | ☐ | | 8 | Test and go live | ☐ | ### What Stays the Same - Same n8n UI and logic - Same node compatibility - Same workflow imports/exports - Same API endpoints and triggers You're just running it on a faster, safer, self-scaling engine. ## What Changes | Area | Self-Hosted | N8Nitro Cloud | | --- | --- | --- | | Setup | Manual Docker/CLI | One-click deploy | | Maintenance | You patch OS & SSL | Fully managed | | Scaling | Manual resource tuning | Auto-scaling 2–8 cores | | Monitoring | External tools | Built-in dashboard | | Security | Depends on host | Encrypted + isolated | | Support | Community only | N8Nitro Team | ## Conclusion Migrating from self-hosting to N8Nitro isn't just a convenience upgrade — it's an operational leap forward. You eliminate DevOps, gain reliability, and instantly unlock auto-scaling performance that grows with your automations. Whether you're managing personal projects or agency-level workflows, N8Nitro keeps your n8n environment secure, fast, and maintenance-free. ### Ready to migrate? Start your N8Nitro instance today and experience hassle-free n8n hosting. ## Frequently asked questions ### Will I lose workflows when I migrate? No. Export them as JSON from your current n8n and import them into your Nitro. Test critical workflows before switching off the old server. ### Do my credentials transfer? You can export and import credentials. If any do not decrypt after import, re-enter them in the new instance. ### Will my webhook URLs change? Yes, unless you map your own domain. Update third-party services such as Stripe or Slack with the new endpoint URLs. ### Can I use my own domain? Yes. Add your custom domain in the Nitro settings, update the DNS records as instructed, and SSL is provisioned automatically. ### How do I avoid downtime? Run both instances in parallel, test every critical workflow on the new one, then move traffic and disable the old instance.