comfyui-node-migration

Migrate legacy ComfyUI V1 nodes to the V3 API with a step-by-step checklist.

265|28|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/jtydhr88/comfyui-custom-node-skills --skill comfyui-node-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comfyui-node-migration
Source: https://github.com/jtydhr88/comfyui-custom-node-skills/tree/main/plugins/comfyui-custom-nodes/skills/comfyui-node-migration
Command: npx skills add https://github.com/jtydhr88/comfyui-custom-node-skills --skill comfyui-node-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts legacy ComfyUI V1 nodes to the modern V3 framework, enabling continued functionality and future-proofing node code by updating class structure, input/output definitions, and registration patterns.

Core Features & Use Cases

  • Provides a practical migration checklist to transform V1 node definitions into V3-compatible io.ComfyNode implementations.
  • Documents and explains the mapping between V1 properties, inputs, and the V3 Schema to ensure accurate behavior and compatibility.
  • Serves as a reference for teams updating custom nodes during platform upgrades, feature deprecations, or API migrations.

Quick Start

Apply the migration checklist to convert your V1 node to the V3 API by renaming the base class, updating inputs, and registering with ComfyExtension.

Frequently Asked Questions about comfyui-node-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate legacy ComfyUI V1 nodes to the V3 API?

To migrate ComfyUI V1 nodes to the V3 API, apply a step-by-step checklist that updates base class changes, define_schema transformations, and ComfyExtension registration patterns to ensure correct execution.

What is the difference between ComfyUI V1 and V3 node definitions?

ComfyUI V3 node definitions modernize V1 properties by mapping them to a new Schema using typed inputs, updated classmethods, and io.ComfyNode implementations for improved compatibility and future-proofing.

How do I update custom node inputs for ComfyUI V3?

Updating custom node inputs for ComfyUI V3 involves applying define_schema transformations to map V1 input properties into typed inputs within the modernized io.ComfyNode class structure.

Do I need to register ComfyExtension when updating to the V3 API?

Yes, registering with ComfyExtension is a required step in the migration checklist to ensure your updated V3 custom nodes are correctly recognized and executed across projects.

Why does my migrated ComfyUI V3 node fail to execute correctly?

Migrated ComfyUI V3 nodes may fail if hidden input access patterns or base class changes are not correctly applied, making it crucial to follow the define_schema transformations and registration checklist precisely.