Migrating from Clash for Windows to Clash Verge in Ten Minutes

Clash for Windows has been unmaintained for over two years: no security patches, no new protocols, and providers slowly dropping compatibility with its legacy core. The good news — both clients consume standard Clash subscriptions, so moving house is cheap. Here is the actual sequence.

Step 1: Recover your subscription URLs from CFW

Open CFW's Profiles page; each profile card exposes its source URL via right-click or the edit icon. Copy them all out. If the UI will not start, the files themselves hold the answer:

%USERPROFILE%\.config\clash\profiles\

The YAML files there usually carry the subscription source in a header comment. Cleanest of all: log into each provider's dashboard and re-copy fresh links.

Step 2: Install Clash Verge and import

Installation: Windows install guide. Then import each URL on the Profiles page. CFW and Verge can coexist briefly, but never with both system proxies on — they overwrite each other's port settings and neither works (symptoms in the port conflict guide).

Step 3: Map your settings across

In CFW	In Clash Verge
System Proxy	Settings → System Proxy
TUN Mode (TAP driver)	Settings → Service Mode + TUN — no TAP driver needed anymore (TUN guide)
Start with Windows	Settings → Auto Launch (autostart guide)
Mixin	Merge / Script — next section
Parsers	Script (the JavaScript mostly ports over)
UWP Loopback tool	Not bundled — use CheckNetIsolation, or simply run TUN

Step 4: Translate Mixin into Merge

CFW's Mixin and Verge's Merge share the same idea — overlay changes on the subscription. Merge is more explicit about placement:

# CFW mixin
mixin:
  dns:
    enable: true
    enhanced-mode: fake-ip

# Clash Verge Merge equivalent — write it at top level
dns:
  enable: true
  enhanced-mode: fake-ip

Rule additions become prepend-rules: / append-rules:. Full syntax: Merge and Script guide.

Step 5: Verify, then remove CFW

Confirm on the Verge side: nodes return latency numbers, routing behaves (spot-check the Connections page), and system proxy or TUN works. Then quit CFW completely, uninstall it, and remove its TAP adapter (Device Manager → Network adapters → TAP-Windows Adapter → uninstall).