Moving a Campaign to Another Device

Nothing about a campaign lives on a server, so nothing follows you around. Moving to a new phone, or onto the Mac you prep on, is a thing you do on purpose. Two ways, and they are not interchangeable:

• A backup file moves the whole authored campaign, DM hat on: every map, encounter, photo, clue, and the edits you made last Tuesday.
• Send to phone pushes a player-side reading copy to a paired phone. It is not a hand-off of your authored campaign.

Moving your authored campaign with a backup file

This is the DM path: chapter 31, Backing Up and Restoring Campaigns, used deliberately.

1. On the old device, open the campaign list, tap the three-dot menu on the campaign row, and choose Back up…. Wait for the green verified checkmark on the BACK UP TO… sheet. Do not skip this part. Verified means the file was written and read back intact.
2. Get the file to the new device however you like. AirDrop between iPhone, iPad, and Mac. A thumb drive or network folder on Windows. A cloud folder that syncs. Far Table does not care which; it is an ordinary file ending in .ftbk.
3. On the new device, open Far Table, go to the campaign list, and tap Restore backup at the bottom. Choose A backup file… and pick the file you sent.

That third step is the one people get wrong. Tapping the backup file itself does nothing useful. Far Table is the file's registered handler, so it carries the right icon in Finder, Files, and AirDrop notifications, but tapping it lands you on the app's start screen with nothing imported. The in-app picker is the only working way in.

If the file arrived from a device you have paired with, it may already be listed in the RESTORE FROM… sheet under Received backups. Pick it there instead of hunting through the file picker.

Continue this campaign, not import as a copy

After you pick the file, the ADD dialog offers two choices, and for a device move you want Continue this campaign.

It means what it says: this is the same campaign arriving on new hardware, keeping its identity and its history rather than becoming a second campaign that happens to look the same. On a fresh device the campaign is not there yet, so you get one confirm dialog and the import runs.

Choose Import as a copy only when you want a separate, independent campaign, for example a spare version to experiment in. A copy lives its own life from that moment; there is no merge between it and the original, ever.

If an older version of the campaign is already on the receiving device, Continue this campaign puts you into the guarded replace flow instead: a red ALREADY ON THIS DEVICE dialog, then a REPLACE CAMPAIGN preview counting what would be added, changed, and removed. Chapter 31 walks that through. Read the counts; differences are overwritten, never merged.

Nothing is removed from the old device by any of this. Restore on the new device, confirm it looks right, and only then wipe the old phone.

Send to phone: a reading copy, not a hand-off

This one is player-side, desktop-only, and part of Mirror pairing (chapter 34, Pairing Your Phone).

On a Mac or Windows machine, open Browse Offline from the app's first screen. If a paired phone is connected, a green dot and "Phone connected" sit above the list and each campaign row carries a Send to phone button. If no phone is connected, the button is grayed out and a note tells you to open Mirror on the phone and pair it first.

Press Send to phone and:

• The button becomes a Sending 4 / 31 counter with a thin progress bar under the row, then Send again when it finishes, or Retry if it fails.
• The phone's Mirror screen shows "Receiving [campaign name]…" with a files-received counter, then a green tick, "It's now in Browse Offline", and an Open button.

What lands on the phone is the read-only player view: browsable with no session, no editing, the same thing chapter 30, Browse Offline: the Player's Atlas, describes. It does not carry your authoring work, and the phone cannot send it onward. If you want to author on the phone, use a backup file.