Skip to content

Import and Export

The Import and Export workbook is the fastest way to create, update, review, and selectively remove many workspaces or jobs in one pass.

What the workbook contains

  • Workspaces worksheet: optional
  • Jobs worksheet: optional
  • at least one of those worksheets must be present

Storage Repositories and runners are not imported from the workbook. Job rows refer to those tenant resources by name first, with identifier fallback columns available when a name is not provided.

Action planning before apply

Validation no longer stops at field checks. It also plans the changes the workbook would make:

  • create
  • update
  • delete
  • unchanged

Deletion planning is worksheet-scoped:

  • if the Workspaces worksheet is present, workspaces missing from that worksheet are planned for deletion
  • if the Jobs worksheet is present, jobs missing from that worksheet are planned for deletion
  • if a worksheet is absent, that entity type is left alone

Excluding actions

After validation, the User Interface shows a review table before apply.

You can:

  • exclude all updates
  • exclude all deletions
  • exclude individual workspace actions
  • exclude individual job actions

This lets you use one workbook as a planning artifact instead of an all-or-nothing import.

Identity rules

MyGreat resolves workbook rows in this order:

  1. name, when the name field is present
  2. identifier, only when the name field is blank

This applies to:

  • workspaces
  • Storage Repositories referenced by jobs
  • runner pools referenced by jobs
  • dedicated runners referenced by jobs

Job names are unique within a workspace, so job identity uses the workspace target plus the job name before falling back to job_id.

The Jobs worksheet is ordered for editing, not for low-level field inspection. The most important import columns come first:

  • name
  • project_name
  • source_remote_name
  • source_path
  • target_remote_name
  • target_path
  • execution_mode
  • worker_pool_name
  • dedicated_worker_name
  • job_config_json

Identifier and reference columns remain available later in the sheet for fallback and advanced cases.

Trigger schedules between imported jobs

If one imported job should trigger another imported job, keep using:

  • job_reference
  • trigger_source_job_reference

Those reference columns are still the clearest way to describe relationships between two workbook rows before either row has a final persisted identifier.

Operator guidance

  • Start by exporting a current workbook from the tenant you want to change.
  • Keep Storage Repository, runner pool, and runner names stable before doing large job imports.
  • Review deletes carefully, especially when only one worksheet is present.
  • Use Validate Workbook first and apply only after the action plan looks correct.

See also