
A tool to migrate data granularly between Jamf Pro servers
Repo jamf/Replicator, read from GitHub 1 min ago. jamf has not joined Take My Repo.
jamf/Replicator is a public repo on GitHub by jamf. A tool to migrate data granularly between Jamf Pro servers. It declares the MIT license on GitHub. It is written mainly in Swift, has 185 stars and last changed on 2026-09-15. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-19.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
Download Replicator
A tool to synchronize objects between Jamf Pro servers. Export objects and save locally, then upload them to another Jamf Pro server. You can also use the tool to delete objects from a server.
By default the application will submit basic hardware, OS, and jamfCPR application usage to TelemetryDeck. The data is sent anamously and used to aid in the development of the application. To opt out of data the sending of data click 'Opt out of analytics' at the bottom of the Settings --> app window.
Replicate items from one Jamf server, or XML file(s), to another. If an object (based on name) exists on both source and destination, the destination object will be updated with values from the source server.
Username and password fields can be hidden/shown using the disclosure tringle on the left.
When replicating files be sure to open the 'raw' folder.

Devices (computers and iOS), Groups, Policies, and Configuration Profiles can be targeted to a particular site.
Servers can be removed from the (source/destination) list by holding down the option key while selecting the server. A warning will be presented to verify the removal.
Limitations/requirements to be aware of:
Be aware you may see the following alert requesting network access. Click allow to permit Replicator to connect to a server.
The Selective tab provides the ability to select a subset of (or all) items within a collection of objects. For example you might only want to transfer 4 scripts from a larger pool of existing scripts.

Also, policies may have their dependencies checked/replicated using the Include Dependencies button. Only 'top-level' dependencies are checked. i.e. if the scope is being replicated and contains nested computer groups or groups assigned to a site that doesn't exist on the destination server the policy replication will likely fail.
Note: The ID of any object can be seen my hovering the mouse over the object.
Files exported using Replicator can be imported into another Jamf Pro server. Be sure to open the 'raw' folder when importing.
Important: Trimmed XML files cannot be used as they are missing data required for the replication.
Preferences:
In addition to scoping options the following are available:
** object name is used to determine whether or not it is on the destination server **
Options to export XML from the source server are also available.
Options for replicating object(s) (searches, policies, and configuration profiles...) to a particular site can be set.
Copying an object to another site either on the destination server or a site on the source server will create/update an object using the defined modifer to alter both the object name and name(s) of groups used in scoping. The variable $SITE may be used in place of entering a specific site name.
Moving an object will not change any of the names. Moving an object to a site on the same server will remove the object from its present site (of NONE) to the new site. Use caution as to not unintentionally unscope configuration profiles from current objects. Moving objects to another server will leave teh object as is on source server and create a new object in the site on the destination server.
The number of concurrent API operations (from 1 to 5), sticky sessions (when available), color scheme, number of log files to retain, number of servers can be remembered, toggling debug mode, and toggling analytic settings can be set.
Migrated computers can show as managed by setting the management account.
Set a password for following replicated service accounts; bind, ldap, file share Read/Write, and file share Read-only.
Note, the same password will be applied if you have multiple binds, or ldap servers, or file shares coonfigured.
Migration Summary:
To get details on how many items were created/updated or failed to replicate type ⌘S, or select Show Summary under the File menu.
Additional information about each count can be obtained by clicking on the number. For example, if we want to see a list of the 4 updated API clients, click on the 4.
Information about successes/failures can be found in the log, located in
~/Library/Containers/com.jamf.jamf-migrator/Data/Library/Logs/Replicator/<date>_<time>_migration.log
Logs can be quickly accessed using Command-L (⌘L) or selecting View --> Logs... from the menu bar.
More detailed logging can be performed by enabling 'Debug Mode' in Settings --> App.
If you have used Replicator and saved passwords you may see the following after launching a new version.
If you'd like the new version to access existing credentials select the desired option.
Important:
Note: the app can also be used to clear out a Jamf server. Typing the following after launching the app will set it into removal mode. Items from the destination server are deleted once Go is clicked.
touch ~/Library/Containers/com.jamf.Replicator/Data/Library/Application\ Support/Replicator/delete
Help is available by running:
/path/to/Replicator.app/Contents/MacOS/Replicator -help
Running the following in Terminal will export all objects (full XML) that can be replicated:
/path/to/Replicator.app/Contents/MacOS/Replicator -source your.jamfPro.fqdn -export -objects allobjects
In the event you have multiple entries in the keychain for a server you'll need to specify which username to use. For example:
/path/to/Replicator.app/Contents/MacOS/Replicator -source dev.jamfcloud.com -destination prod.jamfcloud.com -objects "categories,buildings" -migrate -sourceUser devadmin -destUser prodadmin
Before running an export via command line at least one export from the app must be manually run saving the source username and password or client ID and secret.
To replicate object(s) using the command line, something like the following can be used:
/path/to/Replicator.app/Contents/MacOS/Replicator -source your.jamfPro.fqdn -destination dest.jamfPro.fqdn -objects categories,buildings -migrate
If importing files, the import folder must be selected in the UI before the command line can be successfully run.
To set an ldap id of 3 on jamf user accounts and force that id (also converts local accounts to ldap) use the following:
/path/to/Replicator.app/Contents/MacOS/Replicator -ldapid 3 -source /Users/admin/Desktop/export/raw -migrate -objects jamfusers
This can also be accomplished using the UI by launching Replicator from Terminal:
/path/to/Replicator.app/Contents/MacOS/Replicator -ldapid 3
jamf/Replicator is a public repo on GitHub by jamf. A tool to migrate data granularly between Jamf Pro servers.
It declares the MIT license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-09-15. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Aftermath is a free macOS IR framework


Bash script to start DEPNotify and run policies during enrollment with Jamf Pro
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/jamf/ReplicatorTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.