Reading tip
Identify the scenario first, then follow the checks in order. Jump to the linked download, subscription or configuration page when the issue becomes specific.
Choosing a Replacement
- Windows desktop: start with Clash Verge Rev or FlClash.
- Cross-platform workflow: compare FlClash, Clash Party and Clash Nyanpasu.
- If you only need an old profile for reference, back it up but do not rely on an unmaintained client long term.
Migration Steps
- Back up subscription URLs, profiles and custom rules in the old client.
- Do not upload configs that contain tokens, passwords or node addresses.
- Install the new client and import the provider subscription URL instead of copying an old cache file.
- Check nodes, proxy groups, rule mode and system proxy state.
- Migrate custom rules, overrides or mixins only after basic connectivity works.
- Keep the old client for a few days as a reference, then remove it after verification.
What Not to Transfer Directly
- Temporary cache files from old versions.
- Unknown scripts, overrides and rule snippets.
- Expired or previously leaked subscription URLs.
- Fields that may not be supported by the selected core.
Post-Migration Checks
| Check | Why |
|---|---|
| Node count | Confirms profile parsing |
| Proxy groups | Confirms selectable exits exist |
| Rule mode | Confirms daily routing behavior |
| System proxy/TUN | Confirms app traffic is captured |