Migrate Sequence Actions to Business Timing

Migrate existing Calendar Days sequence actions to Working Days or Business Hours timing while reviewing the proposed changes before you apply them.

Guided Selling v13 and later

Before migrating actions:

1. Review Configure Working Days and Business Hours and confirm the schedules Guided Selling will use.
2. Review Configure Business Timing so you understand the timing options available on each action.

Decide what to migrate

Existing sequence actions retain their prior timing after upgrading to v13. You can migrate gradually, and Calendar Days and Working Days actions can coexist while you transition.

Start with sequences where calendar-based timing is creating the most visible problems, such as actions becoming due on non-working days or outside useful working hours.

Choose a migration method

Use the Sequence Builder for a small number of actions. Use the migration API when you need to convert many eligible actions and want an audit file showing the proposed or completed changes.

Update actions in the Sequence Builder

1. Open the sequence in the Sequence Builder.
2. Open the action you want to update.
3. Change the action timing from Calendar Days to the appropriate Working Days or Business Hours option.
4. Review the delay.
5. Save the action.
6. Repeat for the remaining actions.

Review existing hour-based delays during this process. Some sequences may contain long hour delays that were originally used to push work into the next day.

Migrate actions with the API

The businessTimingMigration API supports a dry run before applying changes.

For an initial migration, scope the request to a small set of Sequence IDs and review the generated audit file before migrating additional sequences.

Run a dry run

1. In Salesforce, open the Developer Console.
2. Select Debug > Open Execute Anonymous Window.
3. Run the following Apex:

RDNACadence.Api api = new RDNACadence.Api();

Map<String, Object> result = api.call(
    'businessTimingMigration',
    new Map<String, Object>{
        'dryRun' => true,
        'workingDaysPreference' => 'Working Days Same Time of Day',
        'sequenceIds' => new List<Id>{ 'a0B...' }
    }
);

System.debug('Job ID: ' + result.get('jobId'));

Replace a0B... with the Sequence IDs you want to evaluate.

No records are changed during a dry run.

Review the dry-run audit file

1. Open App Launcher > Files.
2. Find the CSV file whose name begins with DRY_RUN_BusinessTiming_.
3. Download the file.
4. Review the proposed conversion for each action.
5. Identify any actions that require manual review before continuing.

Apply the migration

1. Open Debug > Open Execute Anonymous Window in the Developer Console.
2. Run the same request with dryRun set to false.

RDNACadence.Api api = new RDNACadence.Api();

Map<String, Object> result = api.call(
    'businessTimingMigration',
    new Map<String, Object>{
        'dryRun' => false,
        'workingDaysPreference' => 'Working Days Same Time of Day',
        'sequenceIds' => new List<Id>{ 'a0B...' }
    }
);

System.debug('Job ID: ' + result.get('jobId'));

A CSV file whose name begins with MIGRATED_BusinessTiming_ is saved to Salesforce Files as an audit record of the migration.

Understand how actions are converted

Review the dry-run CSV instead of assuming every action will receive the same timing configuration.

Migrate in batches

1. Start with a small set of sequences.
2. Run a dry run.
3. Review the audit CSV.
4. Apply the migration to those sequences.
5. Verify the resulting action timing in the Sequence Builder.
6. Repeat for additional sequences.

Actions already converted to Working Days or Business Hours are not reprocessed by subsequent migration runs.

For large orgs with more than 8,000 eligible actions, migrate in batches by using different sequenceIds lists.

Verify migrated sequences

1. Open each migrated sequence in the Sequence Builder.
2. Review several representative actions.
3. Confirm the selected timing mode and delay.
4. Confirm the applicable working days, business hours, and time zone are correct.
5. Review projected timing for participants before expanding the migration to additional sequences.

For schedule configuration, see Configure Working Days and Business Hours.

For details about how first actions and later actions calculate their timing, see Configure Business Timing.