This guide is for people moving to a new iPhone or iPad who already have their own service configuration and subscription. First, distinguish Config files, connection details in Home, and device-level Settings. Then preserve your data with iCloud sync and a separate file backup, and verify each item on the new device. Importing a Config file does not restore everything. Keep the old device until you have checked the connection, rules, and subscription on the new one.
1. Identify what needs to be transferred
Transferring Shadowrocket is about more than checking whether a file with the same name appears in Config. Servers and subscriptions in Home, rule files in Config, and connection behavior in Settings serve different purposes. What a configuration file contains depends on the file itself; do not assume that a .conf file includes every server password, subscription URL, or device setting.
| Where to look | What to preserve | What to check after restoring |
|---|---|---|
| Home | The original URLs for your subscriptions, manually entered server settings, and group information | Whether subscriptions update successfully; whether manual entries have the correct address, port, and authentication details |
| Config | The currently enabled Config file, custom rules, and URLs for referenced remote resources | The selected file, rule order, policy names, and whether resources load correctly |
| Settings | On-demand connection settings, test methods, and records of other settings you changed | Whether Settings → On Demand matches how you use the new device |
| System settings | iCloud availability and VPN authorization | Whether the system VPN configuration has been authorized on the new device |
On the old device, make a checklist without passwords: the current Config filename, frequently used server names, subscription group names, the Global Routing selection, and any DNS or On Demand settings you changed. Store sensitive details somewhere protected, not in public notes or chat screenshots. This site does not provide, sell, or recommend servers or subscriptions; the steps below cover only data you already have.
2. Enable iCloud and confirm your data is visible
iCloud sync keeps data consistent across devices; it is not an immutable historical backup. Deletions and changes may sync to other devices, too. Before switching devices, keep a separate file copy as well. Do not test sync by deleting data from the old device and watching to see what happens on the new one.
- Check the system account. On the old device, open system Settings, tap Apple Account at the top, then check iCloud. The Apple Account used for syncing should be the same on both devices. The account used to get the app from the App Store is separate from iCloud data sync; having the app installed does not confirm that data is syncing.
- Allow iCloud access. In system Settings → Apple Account → iCloud, make sure iCloud Drive is on and Shadowrocket is allowed to use iCloud in the app list. Depending on the system version, you may need to expand Show All or See All to find the app. Follow the options shown on your device.
- Check in-app sync settings. Return to Shadowrocket → Settings and enable the iCloud sync option available in your current version. If the screen separates data into categories, check the scope of each one. Turning on iCloud Drive in system settings does not prove that app data has finished syncing.
- Use a stable network and check available storage. Make sure iCloud is not showing a storage-full or account-verification alert. Let the old device finish syncing, then open the app on the new device and check. There is no fixed wait time that guarantees sync is complete.
- Verify the actual contents. On the new device, check that Config files open and Home entries are present. Seeing a file with the same name does not prove that its contents, subscription credentials, and settings have all been restored.
3. Export a Config file and save a separate copy
The goal of exporting is to preserve configuration contents that can be imported again, not to save a screenshot of the Config list. Before exporting, note the name of the file currently in use. If several files have similar names, open and check their rules separately so you do not export an outdated configuration by mistake.
- Open Config and find the configuration file currently in use. Open that file's action menu and choose its share or export option. The location and wording may vary by version, so use the menu for the current file. Do not choose Delete.
- In the system share sheet, choose Save to Files and save the file in a folder you can access. Keep the
.confextension. You can add the device name to the filename to identify where it came from. - Open system Files and make sure the file is there and can be previewed or read. Check that the contents include the original configuration sections, such as
[General]and[Rule]. An empty file is not a complete backup. - Keep another copy somewhere that will not be affected by sync deletions. If the file is stored only in an iCloud Drive folder, deleting that folder can affect it as well.
- Separately record any server settings entered manually in Home that are not included in the file. Keep the full original subscription URL; do not mistake truncated text shown in a browser for the complete address.
A configuration may contain authentication details, subscription tokens, or internal domain names. When asking someone for help, share only snippets with sensitive values removed. Do not edit the original backup to create a troubleshooting sample. Make a copy first so the original remains available for recovery.
Bottom line: let the file contents define the backup scope
After exporting, check whether the file contains the data you need. Preserve any servers, subscriptions, and device settings not present in the file separately; do not wait until the old device has been erased to look for them.
4. Import on a new iPhone or iPad
Install the app and complete the initial system authorization on the new device before restoring data. Shadowrocket for iPhone and iPad is a one-time $2.99 purchase on the App Store; check the App Store listing for system requirements. The Mac (Apple Silicon and Intel), Windows, Android, and Linux versions are free. Find platform links on the Download page. Buying the app is not a service plan, and installing it does not automatically create a service configuration.
- Check sync first. After enabling iCloud access on the new device, open Home and Config to see what is already there. If the data has appeared, check its contents and entries before importing again to avoid duplicate files with the same name.
- Import any missing files. In Files, find the exported
.conffile and share or open it with Shadowrocket. If Config has a local file import option in your version, you can select the same file there. Make sure you select a file, not a folder or image. - Handle files with the same name. If prompted to replace a file, save a copy of the existing one first and compare their contents. If you need to test, give the copy a different name so you do not overwrite a configuration that already works.
- Select the configuration you will use. Return to Config and make sure the newly imported file is selected. Then check the available servers in Home. Importing a file and enabling that configuration are separate steps.
- Restore missing connection details. Reimport subscriptions using their original URLs. For manual entries, use your records to fill in the protocol, address, port, and authentication details. Match each Trojan TLS and SNI setting, WireGuard key and address, and other fields individually; copying only the server name is not enough.
- Authorize the VPN. When you start a connection for the first time, follow the system prompt to allow adding a VPN configuration. Authorization on the old device does not replace the system confirmation on the new one.
If you need to reimport a subscription, use the add option in Home, import the subscription URL you already have, then update that subscription. The token in a subscription link is a credential. Seeing the same group name on the new device does not prove the credential is valid. After importing, compare the entries before and after the update so you do not mistake an old cache for current results.
5. Check rules, subscriptions, and on-demand connections
After restoring, keep the test conditions consistent: use the same network, server, and test target, and change only one thing at a time. If you switch networks, update the subscription, and rewrite DNS all at once, it will be hard to tell which change fixed the connection.
- Check Home. Confirm the expected server is selected and run Connectivity Test. The result reflects only the reachability of the selected test method and target; it does not by itself prove that every website or rule is working.
- Check Global Routing. Select Config to test rule-based routing. Proxy and Direct do not mean that traffic is routed according to your configuration. If you use Scene, check its conditions as well; noting only the menu name is not enough.
- Check rule references. Make sure policy names in the configuration resolve to valid policies on the new device. If remote rules or other referenced resources need to be reloaded, confirm that their URLs are still valid.
- Check DNS. Compare the DNS settings in the old and new configurations. Do not replace every DNS setting just because a domain will not open. First distinguish an unreachable server from a DNS resolution failure or a rule selecting the wrong policy.
- Check Settings → On Demand. For initial troubleshooting, turn off on-demand triggers and connect manually to confirm basic functionality. Then restore the original conditions and check them on both Wi-Fi and cellular networks.
The examples below illustrate rule structure; they are not complete files to replace an existing configuration. Rules are evaluated in order. A broad rule near the top can take precedence over more specific entries below it. During migration, preserve the old file's order first; do not take the opportunity to reorganize rules in bulk.
[Rule]
DOMAIN-SUFFIX,example.com,DIRECT
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,PROXY
DOMAIN-SUFFIX matches domain suffixes. In the example, IP-CIDR targets a specified IPv4 range, while no-resolve means the rule does not actively trigger domain resolution for matching. GEOIP checks an IP geolocation database, and FINAL handles requests that did not match earlier rules. PROXY still requires a working proxy endpoint in the actual configuration and connection environment; rule text does not provide a service.
Bottom line: restore the existing behavior before changing the configuration
Compare network results only after Config, the selected server, and Global Routing match the old device. First complete a repeatable test, then update remote resources or change rules.
6. Common questions about restoring on a new device
Why are my files missing on the new device even though iCloud is on?
On both devices, check the account, iCloud Drive, and Shadowrocket permissions in system Settings → Apple Account → iCloud. Then check iCloud storage and the in-app sync settings. If the files still do not appear, restore from the separate export made on the old device. Do not delete the app from the old device or overwrite cloud data with an empty configuration.
Why are there no servers in Home after importing Config?
Open the imported file and check its actual contents. A file containing only rules and general settings will not automatically restore entries added manually before. In Home, import using your own saved subscription URL, or reenter manual settings from your records. Also make sure the new file is selected in Config.
What should I do if a subscription update fails after switching devices, even though the URL has not changed?
First check whether the URL was truncated, contains extra spaces, or whether your service account still has access. Distinguish an authentication failure from a network timeout: for an authentication failure, check your existing account with the original service provider; for a timeout, check whether the current network can reach the subscription URL. Repeatedly importing the same link is not a substitute for troubleshooting. Do not post the full token in a public discussion.
Why does traffic routing differ from the old device even though the new device shows a successful connection?
Compare Home → Global Routing, the selected Config, rule order, and policy references in that order. Then check whether Settings → On Demand changed the connection state after a network switch. If it fails only on one network, keep the same configuration and test on another network before resetting everything.
7. Clean up the old device only after confirming the restore
Keep the old device until you have confirmed that the new one works for everyday use. In particular, distinguish signing out of the old device from deleting synced data; the latter may affect other devices using the same iCloud account. Clearing Config or Home is not a required step when switching devices.
- On the new device, confirm the Config file is readable, the correct configuration is selected, and an exported copy is available separately.
- Confirm that your existing subscription can be updated and that authentication details for manual entries have been saved.
- Test access once on Wi-Fi and once on cellular, and confirm that Global Routing and On Demand behave as expected.
- Once you no longer need the old device, follow the system's data-removal process. Handle any service-side device limits or credential revocation through the management portal for your existing service.
Keep a recoverable file copy before making future rule changes. iCloud sync keeps data consistent across devices; a separate export preserves a configuration you have confirmed works. They serve different purposes. For details on individual settings, see the settings reference. For the initial connection steps, see the quick start guide.