Copying a Mac app from Applications does not usually back up its settings or local data. Copying one folder from Library may miss documents, app-group data, credentials, or cloud state.

I use the app’s own export first, Time Machine for the broad backup, and a manual copy only when I know which files the app owns.

Make a backup before changing or restoring anything. Keep the original backup unchanged until the app opens and the important data has been checked.

Record what has to come back

Before making a manual backup, I write down:

  • the app name and version
  • whether it came from the Mac App Store, the developer, or another service
  • the folders containing documents I created
  • the app-owned support, preference, container, and app-group folders
  • whether the app syncs through iCloud or its own account
  • how the app’s licence or subscription is restored

The companion guide to where Mac apps store their data and settings explains the common Library locations. I do not include a folder merely because its name resembles the app. Developer names, bundle identifiers, shared frameworks, and app groups can overlap.

Prefer an app-provided export

If the app offers Export, Back Up, or Archive, I use it and read the vendor’s restore instructions at the same time. An export can preserve relationships between records that are spread across several internal files.

I inspect what the export includes. Some apps export content but omit preferences, attachments, plug-ins, accounts, or history. I keep the original documents and the broader Mac backup as well.

Use Time Machine for the broad backup

Apple says Time Machine backs up files including apps, photos, email, and documents, and can restore files to the same or a different Mac. I connect the backup disk, choose Back Up Now from the Time Machine menu, and wait until the menu reports that the backup is done.

I also open System Settings → General → Time Machine → Options and check the exclusion list. Apple notes that excluded items are not copied to the backup disk, and in rare cases third-party software can mark its files so Time Machine does not back them up.

The current steps are in Apple’s Back up your Mac with Time Machine and If Time Machine doesn’t back up certain files guides.

A Time Machine backup is my safety net. I still use an app export when the app provides one because the export is easier to inspect and may be more portable across app versions.

Make a manual copy only after identifying the files

For an app without an export, I use Finder to copy the known files and folders to a dated backup folder on separate storage.

  1. Save work, finish any in-progress import or sync, and quit the app.
  2. Quit its menu bar item and helper if the app provides a documented way to do so.
  3. Copy the documents I created.
  4. Copy the app-owned support, preferences, container, and app-group folders that its documentation identifies.
  5. Keep the folder structure in the backup notes so I know each original location.
  6. Record the app version, download source, and restore instructions beside the files.

I copy rather than move. I do not remove the originals to prove that the backup works.

Sandbox and app-group containers may be protected. A copy can require authorization, and another app or a different build of the same app may not be entitled to use the restored container. The appearance of a complete copy does not prove that macOS or the app will accept it later.

I usually leave caches and saved window state out of a focused manual backup. I include them only when the app’s documentation says they contain something that cannot be recreated.

Treat synced data as a separate copy

Apple says data for an app enabled in iCloud is stored in iCloud and kept in sync across devices. Sync can bring data to a replacement installation, but sync also propagates changes and deletions.

I check System Settings → my name → iCloud to see which apps use iCloud. For ordinary files in iCloud Drive, I use Download Now in Finder when an item is stored only in iCloud and I need a local copy. Apple documents this in Work with folders and files in iCloud Drive.

I do not overwrite local or cloud-backed data until I understand which copy the app treats as current. When the vendor specifies a sign-in or restore order, I follow it.

Restore without replacing good data

For a small restore, I start with the app’s supported import command. For an item in Time Machine, Apple says to open the Finder window for the item’s original location, open Time Machine, select the item or version, and click Restore. The item returns to its original location.

Before restoring app-managed files:

  1. Confirm that the backup predates the loss or bad change.
  2. Make another copy of the current files, even if they look broken.
  3. Install a compatible app version from the original source.
  4. Quit the app and its documented helpers.
  5. Restore only the files or folders whose ownership and original locations are known.
  6. Open the app and inspect the data before reconnecting a sync service or making more changes, when the vendor’s instructions allow that order.

Apple’s current item-restore steps are in Restore items backed up with Time Machine on Mac.

If the app reports an incompatible database, missing account, damaged library, or permission error, I stop. I keep the current data and backup instead of repeatedly replacing files. The app developer is in the best position to explain its database versions, repair tools, and container entitlements.

Check more than the launch screen

After restoring, I check:

  • several old and recent records or documents
  • attachments and linked files
  • search, tags, presets, and plug-ins that matter
  • preferences that affect where data is written
  • account sign-in and sync status
  • licence or subscription status

Passwords and licences can be stored in Keychain or validated by a server. They may need a separate sign-in or activation even when local data restores correctly.

I keep the dated backup until the restored app has been used normally and another full backup has completed. For a replacement computer, I use Migration Assistant first, then verify the app’s settings and local data on the new Mac.