Import

The Import page creates supported library definitions from an uploaded JSON document or imports a complete job from an Ordyn job bundle.

Open Library > Import, select one file, review what Ordyn detected, and resolve any local references before creating the item.

Supported Files

The page accepts:

• .json documents for job definitions, configuration profiles, scripts, and dynamic endpoint groups
• .zip Ordyn job bundles created by Export complete job

JSON imports create only the definition contained in the document. Complete job bundles can also carry the job's portable dependencies.

See Complete Job Bundle Format to generate a version 1 bundle outside Ordyn, including its manifest, scripts, collectors, files, folders, persistent variables, icon, checksums, and external-reference mappings.

Import A JSON Document

1. Select the JSON file.
2. Confirm the detected document type and name.
3. Map required references to resources in the current Ordyn environment.
4. Clear optional references that should not be retained.
5. Select the create action.

After a successful import, Ordyn opens the created job, configuration profile, script, or dynamic endpoint group.

Import A Complete Job

Complete job bundles are analyzed in the background. Ordyn validates the archive, verifies declared file sizes and checksums, and malware-scans the archive and every included file before showing the review.

Version 1 bundles are limited to 10,000 archive entries, 15 GiB of uncompressed data, and a 1 MiB manifest. Archives with unsafe paths, symbolic links, undeclared entries, duplicate entries, conflicting file declarations, or excessive compression ratios are rejected.

The review shows:

• the job name
• counts and names for portable dependencies
• persistent variable definitions and whether each one will be created, reused, or blocks import
• name conflicts with existing scripts or collectors
• external references that need local mappings
• the destination for included managed files

For each script or collector name conflict, choose whether to reuse the existing definition or import a renamed copy. Jobs are always imported as a new definition, so an existing job-name conflict requires a different name.

When a bundle includes managed files, explicitly choose the Files root or an existing Files folder. Ordyn preserves the included relative folder hierarchy below that destination.

The imported job is standalone. It is not linked to the source job template, and the bundle does not import assignments, schedules, trigger rules, run history, or audit history.

Portable And External Dependencies

A complete job bundle can include:

• saved scripts used by the job
• collectors used by the job and the saved scripts used by those collectors
• global managed files directly used by the job
• global file-folder contents used by folder-sync steps
• the job's self-service icon
• persistent variable definitions referenced by the job

Existing variable definitions are reused by key when their kind, value type, and secrecy setting match. Missing custom definitions can be created only by a super administrator. Secret values and existing scope-specific overrides are not included in the bundle.

Environment-specific resources are mapped during import instead of copied. These can include:

• packages, software products, variants, and software update policies
• endpoints and endpoint-specific files
• secrets and Windows accounts
• operating systems, OS images, install-answer files, and driver profiles
• agent releases
• self-service categories
• organizational and library folders

Dynamic endpoint group imports also map their tenant and group folder, explicitly referenced endpoints and groups, job-run history definitions, collector fields, and variable fields. The importer rewrites collector and variable field identifiers while preserving the selected field name.

Dynamic endpoint group collection imports recreate an exported group-folder tree and all dynamic groups contained in it. Select one destination tenant for a scoped collection and optionally select a destination parent folder. References between included groups are mapped automatically; resources outside the collection use the normal reference-mapping review. Static groups are not included in folder collections. A destination name conflict rejects the complete collection before any folders or groups are created.

Packages are not embedded in complete job bundles. Map package references to packages that already exist in the destination environment.

Required references must be resolved before import. Optional references can be cleared. Selecting a saved script for a JSON job import can reveal additional secret-parameter mappings required by that script.

For references used by a job task, the mapping row identifies the task position and step type first. It also shows a custom task name when one is configured. File-placement mappings include the stored file name and destination path, making it clear which local file must be selected. Expand Technical details when you need the JSON path or original source ID. This review is the same for JSON job definitions and complete job bundles.

Practical Guidance

• Import unfamiliar content into a test environment or folder first.
• Review bundled scripts, task parameters, variables, secrets, and file destinations.
• Confirm target permissions and scopes before assigning or running the imported job.
• Keep imported names descriptive so conflicts are easy to resolve.
• Large bundles can take time to upload, scan, and import. The review is not shown until included files pass scanning.