Glossary
Short definitions of product terms and easily confused concepts.
This page explains terms used in AppPorts and its documentation. The first sections cover product operations and states; the last covers general macOS and filesystem concepts. For individual badges, see badges and status.
Locations and entries in AppPorts
Local entry, launcher, Stub Portal
A small entry left on the Mac after migration that opens the real external app. It is neither a complete app nor a backup. It cannot run the full program when the external drive is offline. See app migration methods.
Real app, external copy
The complete application bundle, as distinct from its local launcher. After migration, the “external copy” may be the only real app in use. Do not delete it merely because it is called a copy.
Folder Mirror
A local directory structure retained for an app suite, with entries linking to external apps or files. “Mirror” here means neither a disk image nor a second complete backup. See app suites.
Migration and recovery operations
App migration
Moving the application itself and managing its local launch entry. Chat history, caches, and projects do not necessarily move with it. See migrate apps.
Data migration
Moving app data, tool directories, or custom folders. It can be used independently without moving the app itself. See migrate data.
Link migration
Data moves to an external location and the original directory becomes a symbolic link to it. Access through the old path leads to the target; permission restrictions still apply.
Mount migration
Eligible container data moves into a dedicated APFS data volume, which is then attached at the original directory. The real app keeps its signature. This currently requires APFS storage. See data migration methods.
Move back, restore
Moving external apps or data back onto the Mac. “Move Back to Local” applies to apps; “Restore” commonly applies to data directories. Both differ from relinking, which only restores an entry. See restore steps.
Relink, mount
Restoring access to external data at its original path while keeping that data on the external drive. Relinking usually rebuilds a link; mounting attaches a data volume at the original directory. Neither copies the data back to internal storage.
Unlink
Removing an app's local entry managed by AppPorts while retaining the real external app. It is not deletion of the external app or restoration of a data directory.
Normalize
Adjusting a recognized managed directory or existing link into the layout AppPorts uses. Check the real target first. In the current default mode, this does not recreate old-style container links.
Modes and protection
Classic data migration mode
A compatibility mode for old container link migration, off by default. Directory protection and risk confirmations still apply. It no longer includes automatic re-signing. See classic mode.
Locked Migration, update protection
Restricting certain updaters from changing the real external app so updates do not break the migration. This is not disk encryption and cannot prevent drive failure. See update protection.
Pending Move Out
A state shown when the real local app appears newer than the external copy. After checking versions, you can migrate the newer local app again. It does not mean migration is running in the background.
Historical feature archive
Documentation of retired features, older workflows, and experimental approaches that were not adopted, with versions and current alternatives. These pages are not current operating instructions. See the historical feature archive.
Signature original, AppPorts Backups
A complete official app saved before manual re-signing, used to restore its contents and original signature. Since 1.9.1 build 31, it is saved automatically in AppPorts Backups at the root of a suitable external drive, with a README.txt. That drive must be connected for recovery. It does not include personal data such as chats or documents; deleting it removes that offline recovery material. See originals and cleanup.
General system and file concepts
Symbolic link, symlink
A special file recording another file or directory's location, much like a direction sign. The sign can remain after the target moves or goes offline. It grants no additional access permissions.
Sandbox
System restrictions on what an app can access. An app may know where a file is and still lack permission to open it. AppPorts cannot remove those restrictions by creating a link.
App container, container data
Data areas managed by macOS for apps and app groups, commonly under Containers and Group Containers. These are different from APFS containers on a disk.
APFS container and volume
APFS is Apple's filesystem. One APFS container can hold multiple volumes sharing storage space. AppPorts mount migration creates a dedicated data volume; it does not install an app inside another program.
Mount point
The location where a volume appears in the filesystem. After an external volume is mounted at an app's original directory, access to that directory reaches the volume's contents. System permissions still apply.
Developer signature, re-signing
A developer signature helps macOS verify an app's origin and integrity. AppPorts' local, ad-hoc signing replaces that signature. It cannot impersonate the original developer and may change authorization behavior.
Restore Original Signature
Using verified original official app files to restore the signature and related contents, rather than applying another ad-hoc signature. A record containing only an old identity name is insufficient; a valid original copy or suitable official release is needed. See upgrade and repair.