I will migrate self hosted n8n and fix breaking changes

F
felixnhl
F
felixnhl
Felix

About this gig

Did your n8n workflows fail after the n8n 3.0 update, or are you afraid to click upgrade?


n8n 3.0 removed the Function, Function Item, Item Lists, Cron and Read Binary File nodes, made Docker the only supported self-hosted install and changed several defaults. Workflows that use a removed node simply fail. I handle n8n breaking changes end to end so your automations keep running.


HOW I WORK

1. Run your built-in Migration Report and list every affected workflow

2. Back up your database and encryption key before anything changes

3. Replace removed nodes with their official 3.0 equivalents (n8n refactoring, not patching)

4. Test on a staging copy, then upgrade production in a planned window

5. Hand over a written change log and a rollback plan


WHAT YOU GET

Deprecated Function nodes rebuilt as Code nodes

Docker VPS check, or migration from npm

Env variables pinned where 3.0 changed defaults

Nothing goes live without your approval


You keep full ownership of your server, accounts and workflows.


Message me your n8n version (Settings > About) and how you host it.


Get to know Felix

Felix

Senior Automation Architect Infrastructure Consultant

  • FromUnited Kingdom
  • Member sinceOct 2026
  • Languages

    English
I specialize in self-hosted n8n upgrades, server migrations, and automated workflow refactoring. I help business teams safely upgrade their infrastructure to secure Docker VPS architectures without experiencing service downtime. I audit workflow instances, convert legacy JavaScript into modern Code nodes, and implement strict backup protocols.

Related tags