Shadowrocket Transfer to a New iPhone or iPad: iCloud Sync, Config Export, and Restore

At a Glance

This guide is for users with existing connection details or subscriptions who are moving to a new iPhone or iPad. Handle connections in Home, rule files in Config, and runtime options in Settings separately. Keep the old device, restore via iCloud or a file, then check rule matching and connectivity. Exporting a Config file alone does not back up all app data.

What to Transfer: Separate Connections, Rules, and Runtime Settings

When transferring Shadowrocket, the goal is not simply to reproduce the same list on the new device. Connection details, the active Config, and the Global Routing mode must all match. Seeing a connection in Home only confirms that its details are present. Check separately that the right Config is selected and its referenced policies are available.

iCloud sync can transfer app data supported by the feature between your own devices. Exporting a Config gives you a standalone file you can inspect and import again. First, check what each method actually covers. In particular, don’t assume that subscription-based connections, manually added connections, or system VPN authorization have all been restored just because a file was saved.

Home

Check connection entries, subscription groups, and the current selection

Config

Check local rule files and the active configuration

Settings

Review sync options, On Demand, and other runtime settings

Item	What to keep in the backup	What to check on the new device
Existing connections	Protocol, address, port, and authentication details	Check that all details are present and the right connection is selected
Existing subscriptions	Original subscription URL, group, and update settings	Check that it updates and whether entries change afterward
Config file	Local edits, rule order, and policy references	Check that the file is imported and selected for use
Runtime settings	Record settings such as Global Routing and On Demand	Review settings for the new device; don’t copy connection toggle states blindly

Bottom line: Keep two restore options

Even with iCloud sync enabled, save the active Config and existing subscription details separately. Don’t erase the old device until you’ve verified everything on the new one.

Back Up the Old Device: Create a Baseline for Comparison

Before backing up, make sure the old device is working as expected. If the existing setup has issues, transferring it will carry them over. Record its working state before exporting. Avoid making major rule changes, updating subscriptions, and deleting connections all on moving day; otherwise, it will be hard to tell which step caused a difference.

Record Home. Note the selected connection, its subscription group, and protocol. For manually configured connections, keep the complete original details—not just the display name.
Record Global Routing. Distinguish Proxy, Direct, Config, and Scene. These are different routing modes, not four copies of the same rules. If you rely on rule-based routing, note whether Config is actually selected.
Check Config. Confirm which file is in use, then save any manual rule edits before exporting. If you maintain related files locally, check separately how to restore them.
Review Settings → On Demand. Note whether it’s enabled and record its conditions. Verify the connection manually on the new device before deciding whether to restore automatic activation.
Choose a secure place for sensitive files. Keep subscription URLs, passwords, and exported files somewhere only you can access. Don’t share them through public links.

iCloud Sync: Check iCloud First, Then Verify the Restore

iCloud sync depends on the Apple Account, system iCloud settings, network connection, and the data Shadowrocket supports syncing. A full-device backup and in-app sync are different mechanisms: the former is for restoring a device, while the latter syncs app data it supports. A completion notice for one does not confirm the other is done.

Check old deviceEnable syncReceive on new deviceCompare itemsTest connection

On the old device, open system Settings and check your Apple Account and iCloud settings. Make sure iCloud Drive is available and review Shadowrocket’s iCloud access. Setting names may vary by system version.
Open Shadowrocket and check the iCloud sync options available in Settings. If you can choose what to sync, review each option. Don’t assume that enabling sync includes all data.
Keep the device online and allow time for it to sync. There’s no fixed completion time. Repeatedly toggling sync is no substitute for checking the data.
On the new device, use the same Apple Account, install and open Shadowrocket, and confirm the system and app sync conditions. Then check Home and Config for the expected content.
Compare entries, files, and key settings against your notes from the old device. Restore anything missing from the saved Config file or connection details rather than deleting data from the old device first.

Sync may propagate edits or deletions to other devices, so it isn’t a permanent standalone snapshot. During the transfer, edit on just one device if possible. If the new device already has a different setup, export it first, then decide whether to merge or replace it. Files with the same name may not have the same contents.

Export Config: Save the File and Its Dependencies

A Config mainly contains configuration text and rule logic. Whether it includes connection definitions depends on the file’s contents; don’t assume it includes connections maintained separately in Home. After exporting, check that the file opens, its rules are intact, and any referenced policy names are available.

On the old device, open Config and locate the local file in use. Make sure your edits have been saved.
Use the file’s action menu to share or export it to a location in your own Files. Use the options available in the current interface. Don’t treat a remote configuration URL as a copy of your locally edited file.
Reopen the saved file to make sure it isn’t empty or just a record containing a remote URL. Separately keep subscription details and manually added connections that aren’t in the file.
On the new device, import the file using the option in Config or a Shadowrocket destination available in the system share sheet. Then return to Config and confirm the file is listed and selected.

The rule snippet below illustrates where to check; it is not a complete, usable configuration. example.com and 192.0.2.0/24 are documentation examples. Don’t use this snippet to overwrite your complete file.

[Rule]
DOMAIN-SUFFIX,example.com,DIRECT
IP-CIDR,192.0.2.0/24,DIRECT,no-resolve
FINAL,PROXY

Check that exceptions such as DOMAIN-SUFFIX appear where expected and that FINAL remains at the end of the rules. If the file references custom policy names, confirm that their definitions are also available on the new device. A remote rule resource URL in the file doesn’t mean the resource was fetched successfully.

Bottom line: Check dependencies after import

Check policy names and connection sources before enabling rule-based routing. If connections are missing from Home, restore them from your saved connection details instead of repeatedly importing the same Config.

Restore on the New Device: Verify Connections, Rules, and Automatic Activation in Order

Get Shadowrocket from the App Store on the new device, then restore your data. Shadowrocket is a paid app for Apple platforms. For iPhone and iPad system requirements, see the App Store listing. Purchase history and configuration data are separate: restoring a purchase doesn’t restore subscriptions, passwords, or Config files.

Check the details first. Review restored connections in Home. For a Trojan connection, for example, make sure Address, Port, Password, and SNI match your original details. If the Port was 443, keep it as 443—don’t change it to a familiar value just because you’re moving devices.
Complete system authorization next. The first time you connect, follow the system prompt to allow adding a VPN configuration. Authorization is a local step on the new device; don’t skip it just because the old device was already authorized.
Test the connection and rules separately. Briefly use Global Routing → Proxy to verify the selected connection, then switch back to Global Routing → Config to test rule-based routing. Restore your intended mode afterward so you don’t leave a temporary test setting in place.
Check that Config works as expected. Choose destinations you know should use DIRECT and PROXY, then check the connection log for the matching policy. An enabled connection alone doesn’t confirm that the rules are working.
Restore automatic activation last. First confirm that a manual connection works. Then review the conditions in Settings → On Demand and observe what happens when switching between Wi-Fi and cellular.

If you use an existing subscription, check the restored content before running one deliberate update. An update may rename connections, remove inactive entries, or replace server details. Afterward, check the selected connection and any policies referenced by name in the configuration. Don’t mistake changes caused by a subscription update for a failed Config import.

Troubleshooting a Transfer: Find What’s Missing Instead of Overwriting

When something goes wrong, identify whether the missing item is a connection, rule file, or runtime setting, then take the relevant action. Change one thing at a time and check the result. Updating a subscription, changing routing mode, and replacing Config all at once makes it hard to identify the cause.

Why is Home empty when Config is visible on the new device?

First check whether the imported file contains connection definitions. A rules-only file won’t populate the separate connection list. Restore Home using your saved subscription URL or original connection details, then check the policy references in Config. Don’t keep importing the rule file to fill the list.

Why is content different between devices even though iCloud is enabled?

Check the Apple Account, system iCloud permissions, app sync options, and network connection in order, then identify exactly what’s missing. Don’t delete or rebuild all data on an empty new device first. Keep a copy on the old device and restore any urgently needed Config files from your saved files.

Why did my original routing rules not come back even though the connection works?

In Home, check whether Global Routing is set to Config. Then open Config and confirm the selected file. Proxy and Direct don’t route traffic according to that rule file. If you’re using Scene, also check which scene configuration is selected.

When can I clear data from the old device after moving?

First test the connection on the new device, check rule matching, run one update for an existing subscription, and confirm that your standalone backup can be opened. Before cleanup, review what iCloud syncs and distinguish removing data locally from deleting synced data. If you’re unsure, keep the old device’s data.

How Backups Work: Manage Sync and Standalone Copies Separately

iCloud sync keeps data consistent across devices; a standalone export preserves the contents from a specific point in time. Sync may propagate later changes, while an export won’t automatically reflect subscription or rule updates. Use both methods together. Save a new standalone copy after major rule changes rather than relying on an outdated file.

Connections: Keep the details needed to restore connections. Subscription content still depends on the status and access granted by your provider.
Configuration: Keep the Config text, rule order, and policy dependencies. After import, confirm that the file is selected for use.
Device settings: Recheck VPN authorization, Global Routing, and On Demand. Don’t assume the new device has the same runtime state as the old one.

The transfer is complete when the new device can connect as expected, match rules correctly, and restore from a backup when needed—not merely when sync is enabled. Keep an accessible Config file, recoverable connection details, and a brief record of key settings to make the next transfer easier.