Migrating Settings Between DayBack Instances

In this article:

Migrating Settings in Salesforce


DayBack allows administrators to migrate DayBack settings between Salesforce instances where DayBack is installed, typically to move settings between a sandbox and production org.

How Settings Migration Works

Migration flows from one org to the currently signed-in org and will overwrite all DayBack settings in the currently signed-in destination org with those from the source org.

Important Note!

Salesforce uses 18-digit Org IDs for API communication, although it still displays the older 15-digit Org IDs for existing orgs. To use the API (which DayBack relies on), you must use the 18-digit Org ID for settings migration.

You can view your full 18-digit Org ID within DayBack when migrating settings, as shown in the image below.

Once enabled, this process copies the same collection of settings as DayBack's Configuration Snapshots. Learn more about the included and excluded settings here: Configuration Snapshots.

Migration Token and Multiple Deployments

You can migrate into any org where you have entered the same migration token; the token contents are up to you, but we recommend treating this as a long, complex password. You'll find this on the Tools tab of Admin Settings.

Migrating Settings in FileMaker


To migrate settings in FileMaker, follow these steps:

  1. Create a Unique Token:
    • Generate a unique token and enter it into the "Migration Token" field in both the source and destination groups.
    • The token should be non-guessable. While there's no strict requirement for its content or length, it's recommended to use a complex string of letters and numbers, at least 12 characters long.
    • Note: The same token must be used for any other DayBack group you plan to migrate settings with.
  2. Enter the DayBack Group ID:
    • Copy the DayBack Group ID from the source group and paste it into the destination group where you want the settings to be applied.

Related Articles