When migrating Shadowrocket, check your connection details in Home, rule files in Config, and connection settings in Settings separately. This guide is for users who can still access their old iPhone and are preparing to restore on a new device. Save a separate backup first, verify the iCloud sync results, then test subscriptions, rules, and connection behavior one by one. The steps assume you already have your own service provider and subscription.
1. Separate Config files, connection details, and system permissions
Exporting a Config file does not back up the entire app. Config mainly contains the settings in the selected file. Subscription groups and manually added nodes in Home, along with options in Settings, need to be checked separately. Check the exported file itself to see whether it contains connection credentials; the file extension alone is not enough to tell.
| What to migrate | Where to check on the old device | What to verify on the new device |
|---|---|---|
| Subscriptions and nodes | Subscription groups and node details in Home | Subscription URL, group, server address, port, and authentication details |
| Rule configuration | Currently selected file in Config | File contents, rule order, policy references, and remote resource URLs |
| Routing mode | Home → Global Routing | Whether the current mode is Proxy, Direct, Config, or Scene |
| On-demand connection settings | Settings → On Demand | Toggle, matching conditions, and network names on the new device |
| System VPN permission | VPN configuration in iPhone Settings | Confirm again when prompted during the first connection |
Before migrating, note both what is currently in use and what has been saved. For example, Config may contain several files, but only one is selected; Home may also contain inactive subscriptions. Checking only the item count can lead you to mistake old data for a working setup.
2. Check system permissions and app sync settings in iCloud
iCloud sync depends on your system account, iCloud Drive, and app permissions. Installing the app does not mean these requirements are met. First check the system settings on your old iPhone, then open Shadowrocket and check Settings → iCloud. The available sync options depend on what the current app interface shows.
- Open Settings on your iPhone, tap your Apple Account at the top, then tap iCloud. Make sure you are using the account you plan to use on the new device.
- Check that iCloud Drive is enabled. In the list of apps using iCloud, find Shadowrocket and make sure its permission is on. Depending on your system version, you may need to tap Show All or See All to find the list.
- Open Shadowrocket → Settings → iCloud and check the available sync items and their status. If this option is not present in your current interface, do not assume your app data has been uploaded; continue with the separate export steps below.
- Keep the old device connected to the internet and check that you have enough iCloud storage. If you are using cellular data, check whether the system restricts iCloud Drive over cellular.
- Check the same permissions on your new device, then compare the contents in Home and Config. Verify what actually appears on the new device rather than relying only on the toggles on the old one.
Verify each part of the sync separately; turning on iCloud is not a substitute for checking the restored data. Sync options shown in the app, saving a file to iCloud Drive, and a full-device system backup are different things. Exporting Config to iCloud Drive only confirms that the file was saved there; it does not mean the file includes Home subscription lists.
Keep the old device until you have checked everything on the new one
Do not erase the old device or bulk-delete data on either device to force a sync before confirming that subscriptions, Config files, and working connections are present on the new device. Sync can propagate deletions. A separate export gives you a recovery point that does not depend on changes to the list.
Editing the same configuration on both devices makes it harder to identify differences. During migration, avoid renaming items, deleting groups, or changing rules on the new device. After exporting from the old device, try to stop editing its configuration too. If the contents differ, compare them with the separate backup before deciding which copy to keep.
3. Export Config files and keep an identifiable backup copy
The goal of a separate export is to create a Config copy you can find and reopen in the Files app. Before starting, open Config and note the name of the currently selected file. If you switch between multiple configurations, export each one you need rather than saving only the first item in the list.
- Open Shadowrocket → Config and note the file in use, along with the names of any other local files you want to keep.
- Open the action menu for the file you want. Try long-pressing its row to see the available actions. If Share appears in the row or a swipe menu, use that option.
- Tap Share to open the system share sheet, then choose Save to Files and save the file in a folder you control. Choose a descriptive filename, such as
home-rules-backup.conf. - Open the Files app, find the file you just saved, and make sure it opens and is not blank. Keep its original extension; do not save it as an image or text note that you can only view.
- For an offline copy, copy the file to another storage location you control. Two shortcuts to the same cloud file are not two independent backups.
Record remote configuration URLs separately, but do not treat them as a substitute for backing up local changes. The remote file may change later. If you adjusted DNS, rule order, or policy names on the old device, downloading the remote file again may not give you the same configuration.
Config file checklist
- File location
- Currently selected configuration in Config
- Export option
- Share in the file action menu
- Separate copy
- Readable Config file in the Files app
- Content check
- Rules, DNS settings, and policy references
Keep the actual contents, not just the filename or remote URL.
Home connection details checklist
- Subscription source
- Original URL from your existing service provider
- Manually added nodes
- Protocol, server, port, and authentication details
- Additional parameters
- Check TLS, SNI, and transport settings for each protocol
- Sensitive fields
- Subscription tokens, passwords, and private keys
If these details are not in the exported file, save them separately and securely.
4. Restore Home first, then select a Config file
On your new device, restore connection details first, then rule files, and finally the running state. This order makes it easier to identify anything missing. Visit the download page for platform-specific options, then open the app to restore your setup. The steps below use an iPhone as an example.
- Check what synced first. Open Home and check your subscription groups and manually added nodes. Open Config and see whether the file you need is there. Do not import items that have already been restored.
- Restore missing subscriptions. If a subscription is missing from Home, use the provider URL you already saved. Tap “+” in Home, set Type to Subscribe, enter the URL, and save. Then update the subscription.
- Restore manually added nodes. Use the connection details saved on your old device or content shared by the app. An address and port are usually not enough; check the authentication and transport parameters required by the protocol too.
- Import the Config file. Find the exported file in the Files app and share it with Shadowrocket using the system share sheet. Then return to Config, confirm the file is there, and select it. A file appearing in the list does not mean it is active.
- Check Global Routing. To use the rules in your configuration, select Config. Proxy, Direct, Config, and Scene are different modes. If you used Scene on the old device, check its conditions too; copying the mode name alone is not enough.
- Start the first connection. Follow the system prompt to add or confirm the VPN configuration, then return to Home and check the connection. The permission granted on your old device does not replace confirmation on the new one.
Updating a subscription fetches the list currently returned by the server; it does not restore a historical snapshot. If your provider has changed node names, addresses, or plan access, the updated list on your new device may differ from the old device's cached list. Check the subscription source and service status before assuming the Config import failed.
5. Verify nodes, rules, and On Demand after restoring
An enabled connection toggle only means a connection attempt has started; it does not prove the migration is complete. Test a known working node first, then check the rules, and finally restore the on-demand conditions. This helps narrow down any issue.
- Test a node: In Home, select the node you used before, run Connectivity Test, and try accessing a service you use regularly. Check both the test results and actual requests; a single latency reading is not the whole picture.
- Check the subscription: Run an update and make sure there are no URL or authentication errors. If the old list is still visible but the update fails, it may only be a local cache; that does not mean the subscription is working.
- Check the rules: In Config, confirm the file is selected. In Global Routing, confirm Config is selected, then check that the required rules and policy names are present.
- Check On Demand: Go to Settings → On Demand and review the toggle and each condition. If you have changed your home router or Wi-Fi name, the old network name may no longer match.
- Check external dependencies: If the configuration refers to remote rules, private domains, or additional certificates, make sure each is still accessible and valid. A single Config file does not automatically restore every system-level setting.
Compare the actual rule text and order when migrating, not just the file size. The examples below show rule syntax only; they are not a complete replacement configuration and do not include any working services. If the original file uses custom policy names, keep them consistent with the policy definitions.
[Rule]
DOMAIN-SUFFIX,example.com,DIRECT
IP-CIDR,192.168.0.0/16,DIRECT
GEOIP,CN,DIRECT
FINAL,PROXY
DOMAIN-SUFFIX matches domain suffixes, IP-CIDR matches IP ranges, GEOIP applies a geographic condition, and FINAL handles requests that do not match earlier rules. Preserve the original order when checking differences. Moving a catch-all rule earlier may prevent later rules from working as expected.
Test a manual connection before restoring On Demand
If a manual connection still fails, check the node and configuration first. If manual connections work but fail after switching networks, then check On Demand. Avoid changing nodes, rewriting rules, and adjusting on-demand conditions all at once while troubleshooting.
6. Common questions about restoring Shadowrocket
Why is the list still empty when both iPhones use the same account?
On both devices, first check iCloud Drive and Shadowrocket permissions in system settings, then review the app options under Settings → iCloud. Once you have confirmed that storage and network access are working, check Home and Config separately. If only one type of data is missing, restore that data from your separate backup. Do not delete anything from the old device first.
I imported a Config file, but there are no nodes. Why?
Open the file first and see what it actually contains. A rule file may not include subscriptions and nodes from Home. Check subscription groups in Home; if any are missing, add your existing subscription again. For manually added nodes, use the details from the old device to restore authentication and transport parameters.
The new device has nodes, but subscription updates fail with an authentication error. What should I do?
First check that the URL is complete, especially that the access token after the question mark is present and contains no spaces or line breaks. Then check with your existing provider that the subscription is still active. If the token has changed, update the URL instead of repeatedly importing the same expired link.
My old phone has been erased and I only have a Config file. How much can I restore?
Import the file and check its contents. You can restore the rules and settings it contains, but you cannot infer missing subscription URLs, passwords, or private keys from the filename. Check iCloud storage you control, your separate backups, and your provider account. You will still need to confirm the system VPN permission again on the new device.
7. Finish restoring before clearing the old device
Leave cleanup of the old device until the final step. Before deciding whether to stop using it, check subscription updates, a manual connection, the selected Config file, and On Demand conditions. Being able to open one webpage for a short time is not enough to confirm that everything has migrated.
- Confirm that all subscriptions and manually added nodes you need are in Home and that subscriptions can be updated.
- Confirm the target file is selected in Config, and check local changes, rule order, and policy references.
- Confirm Global Routing is set as expected, and test connections over both Wi-Fi and cellular data.
- Confirm the separate export is still readable, where it is stored, and who can access sensitive data.
- Before clearing the old device, distinguish between erasing the device and deleting synced items in the app. Avoid deleting content you need to keep in the cloud.
Verify cross-platform migrations separately; iPhone system settings do not determine how restoration works on other platforms. Download information for Mac (Apple silicon and Intel), Windows, Android, and Linux is on the download page. The system permission steps for iPhone in this guide do not necessarily apply to other platforms.