Skip to content
Sojournby CloudAlgo Request early accessEarly access Request early access
Release 1 in development, 15 of 15 sprints done. Early access is open. 15 of 15 sprints done · Join early accessJoin early access
Guide

Move settings between orgs

Export Sojourn settings from a sandbox as a file, check the import in production, then apply it.

Salesforce admin About 10 minutes Since release 1

Set Sojourn up once in a sandbox, then move the settings to production, or to another sandbox, as a file.

What the file carries#

  • Tracking enabled and the default business hours.
  • The Live values window, the three limits Sojourn leaves for your own automation (queries, rows, and CPU), and the days before Day rows become Month rows.
  • The Omni-Channel statuses that start agent work.
  • The three Health thresholds: open errors for amber, open errors for red, and the hours after which a job is late.
  • The Dashboards settings: the Tracked field, period, and hours a new dashboard opens on, the owners, Trend values, and Longest open rows the charts show, what the print preview starts with, and the dashboard, chart, and summary row limits. The Tracked field may be one the file itself tracks.
  • Each Tracked object with its settings, including:
    • the lookup to fill on each Interval and the History backfill records per chunk;
    • which owners get an Interval, and whether a move between members of one queue keeps the owner's stay;
    • the records to track;
    • business hours by record type.
  • Each Tracked field, with the values that do not count, its value groups, its value colours, what an Interval keeps, and the field its goals are split by.
  • Each goal, with the split value it is for.
  • Queue business hours.
  • Get started: whether Sojourn Settings opens on the guide first, and the two steps marked done by hand, each with who marked it and when. A mark whose user is not in the org you import into keeps its date; the step then reads "Marked done on" the date, without a name.

Each setting is written as it applies in your org, so one you never changed is written as its default. The red Health threshold has no default: when it is blank the file says never, and an import of never leaves red blank in the other org. Retention, the archive, the purge part size, and each object's own retention are not in the file: production keeps what you chose there.

Business hours are written by name, and queues and record types by developer name, because record Ids differ between orgs.

Export#

In the org you are copying from, open Sojourn Settings, then Data, then Export settings, and choose Export. Sojourn saves the file, named like sojourn-settings-2026-10-12.json, to your Files and opens it. Download it from the preview.

Check the import#

In the org you are copying to, open the same screen and choose Choose file. Sojourn reads the file and lists What the import will do: each Tracked object, Tracked field, goal, queue, and setting it will create, update, turn off, or skip, and why. Nothing has been changed yet.

  • An object or field this org does not have stops the whole import, and nothing is written. So does a field that records to track or a split goal names and this org does not have. Add the field, or remove it from the source org, and export again. A Name field or Snapshot field you cannot read in this org stops the import too, with "You cannot read" and the field's name, because Sojourn copies those values to everyone who reads Intervals; give yourself read access to the field, or choose another in the source org, and export again.
  • A queue or business hours this org does not have is skipped, with the reason; the rest still imports. Business hours by record type is skipped whole when one of its business hours or record types is missing.
  • A setting the screens would refuse is skipped with the reason the screen gives, and the rest still imports. For example:
    • a number outside its range, or a red threshold that is not a whole number or never;
    • an Omni-Channel status this org does not have, or a lookup that does not point to the object;
    • on the Free plan, a changed History chunk, changed Omni-Channel statuses, or a changed Dashboards setting;
    • a new dashboard's Tracked field that is not one of the Tracked fields, in this org or in the file;
    • an owner choice the Values tab does not offer, or a condition the Records tab would refuse;
    • a value that does not count that is closed, or that the field does not have;
    • a value in two groups, or a colour other than Tide, Harbor, Slate, or Mist;
    • keeping only the change on the status field or the field Closed when reads, or on a field with goals;
    • a split field that is not a picklist or checkbox.
  • A skipped setting stays as it was in this org. Sojourn never writes part of a setting.
  • A goal the Goals screen would refuse is skipped with its reason: a goal on a value that does not count, a goal on a field that keeps only the change, or a split value the split field does not have.
  • When the file changes the field a Tracked field's goals are split by, goals for the old split values that are not in the file are turned off, as on the Goals screen.
  • A Tracked object whose new status field, or Closed when field, keeps only the change is skipped with the reason.
  • A file from before these settings were carried leaves them as they are.
  • A file that is not a Sojourn settings file, or is from a later format, is refused.

Apply#

Choose Apply. Everything in the list is written together, or nothing is.

Turn on Replace what is here before checking to make this org match the file: Tracked fields and goals that are not in the file are turned off. Nothing is deleted, and Tracked objects that are not in the file are left as they are.

You are done when

  • Choosing the same file again lists nothing to change.

Updated in release 1 This page changes in the same pull request as the feature it describes.