Import configuration for Jamf Importer
- Pio
- Eva Ruzheva
1. Build Objects/Attributes
After completing the Source and Destination configurations, it's time to create Object Types and their relationships based on the Jamf Pro Data Model.
You can also choose to enable or disable Object Schema Sharing.
Pro Tip: Many of our customers create references from other Object Schemas and need access to the Azure AD data. We recommend enabling Object Schema Sharing.
Review the options, then click the "Build Objects/Attributes" button.
 |
This step only needs to be completed once. Once the build is successful, you won’t need to repeat it. If this step has already been completed, a message will appear confirming it.
You may check your new Object Schema now and make sure the Object Types and Attributes are successfully created.
The Object Schema Graph will be as follows:
 |
2. Test and Full Imports
You can verify the configuration by clicking the Test Import button. This action will import the initial Computers into your Object Schema. After the test has been executed, please allow a few minutes for the process to finalize, and then review your Object Schema.
To keep track of the progress, click the Check Import Status button to view the current execution status of the import.
If you are happy with the results of the test run, please run a manual full import.
3. Schedule
You have 4 options for the scheduling.
 |
Enable Hourly Imports: Runs the import once every hour when enabled.
Enable Daily Scheduled Imports: Runs the import once per day when enabled.
Enable Multiple Daily Scheduled Imports: Allows you to schedule imports at multiple time slots throughout the day.
Disable Scheduling: If you have a large number of records, the import may take time. We recommend testing it during off-peak hours when JSM usage is low.
Pro Tip: We recommend starting with a manual import by clicking the “Full Import” button to measure the import duration.
If the full import takes an extended amount of time (e.g., over an hour), or if multiple imports are scheduled simultaneously in your JSM Site, hourly scheduling may not be ideal. In such cases, we suggest using Daily scheduling, which is the most commonly used import schedule among JSM customers.
Due to the way Atlassian’s Forge platform handles scheduling, functions are repeatedly invoked at set intervals. Each trigger starts approximately five minutes after the app is deployed. As a result, it is not possible to specify the exact minute when the scheduled import will run. For more details, refer to Atlassian’s documentation Atlassian’s Documentation.