VNCCS Migration Assistant

VNCCS 3.0, released in mid-2026, wasn't an incremental update - the pack's own author described it as "a completely new project, based on the previous release," rewiring the whole pipeline onto Qwen-Image-Edit 2511 and Anima Base 1.0 in place of the older Illustrious-and-SDXL-era workflow. That kind of ground-up rebuild means the character data format changed too, and Migration Assistant exists purely to carry your existing characters from the old layout into the new one. If you're setting up VNCCS for the first time, this node isn't for you - skip straight to Character Creator. If you've got characters built under an earlier VNCCS version, this is Step 0, run before anything else.

What it actually is

The schema tells you almost everything: no inputs, no outputs. This is a widget-driven utility node, not a graph component you wire anything into. You open the dedicated VNCCS_MigrationAssistant.json workflow (not a node you drop into an existing graph), pick which existing characters to migrate from its UI, and click migrate. It's flagged as an output node because the migration itself - writing files to disk in the new folder structure - is the whole point, not something with a downstream ComfyUI value to hand off.

The one instruction worth repeating

Do not delete your old character folder immediately after migrating. Verify the migrated characters actually load and work correctly in the new format first. This isn't excess caution for its own sake - it's the pack's own explicit warning, in capitals, in the README. A migration step that silently drops a field or mishandles an edge case in your old character's data is exactly the kind of thing you want a backup for, and once you've deleted the source there's nothing to fall back on.

How to install it

Comes with the main pack - there's nothing separate to fetch for this node specifically:

• ComfyUI Manager - search VNCCS - Visual Novel Character Creation Suite, install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/AHEKOT/ComfyUI_VNCCS.git, then cd ComfyUI_VNCCS_Utils && pip install -r requirements.txt, restart, and click "Install missing custom nodes" in Comfy Manager once - VNCCS depends on a companion utilities pack for some of its UI widgets, including this one.
• First time touching ComfyUI at all? Use VNCCS Easy-Install instead - a preconfigured setup with everything already wired, which also sidesteps most of the issues below.

Common issues

A companion node - "VNCCS - Collection of utility nodes" - refuses to install through Comfy Manager. This has been reported directly against VNCCS 3.0: the install can silently fail with no console error until you lower ComfyUI Manager's security level to weak in its config.ini. If Migration Assistant (or any of VNCCS's control-panel-style nodes) isn't showing up after an otherwise successful pack install, check that setting before assuming something else is wrong.

Model or asset downloads inside VNCCS's control panels just say "error" with nothing in the console. Reported by more than one user on third-party ComfyUI launchers - specifically the "EZi Launcher" - which blocks some of the JavaScript these control-panel widgets rely on. The pack author's own advice: use the plain .bat launcher in your ComfyUI installation folder instead of a wrapper launcher if VNCCS's UI-driven nodes behave oddly.

Paths look broken, or files end up in the wrong place, on Linux or macOS. VNCCS's workflows were originally built and tested on Windows, and at least one user traced broken node behavior to backslash-versus-forward-slash path handling on Ubuntu. If migration produces folders in an unexpected location, check for this before assuming your character data is lost - it's usually a path-separator issue, not a data-loss one.