Prepare a Schedule Migration Inventory

Record the schedules and dependencies you need to move so you can prepare the destination and plan the transfer.

The outcome of this guide is a completed inventory. Schedule reads help inspect configuration; they do not produce a complete export or database backup. Use an ATRS-supported transfer method confirmed for your source and destination installations before attempting migration.

Before you begin

Identify the source and destination ATRS installations.
Record their installed versions and the schedules you intend to move.
Arrange access to the ATRS application and the required dependencies.
Choose the people responsible for testing and cutover.

1. Create the inventory

Copy this CSV header into a file named ATRS-Migration-Inventory.csv, then add one row per schedule. Quote values containing commas using standard CSV rules.

SourceInstallation,SourceVersion,ScheduleId,Family,ScheduleName,DestinationInstallation,DestinationVersion,TargetFolder,Owner,TableauDependencies,OutputSettings,DeliverySettings,ProcessingDependencies,CutoverPlan,TestExecutionId,ContentCheck,DeliveryCheck

Store the inventory in an access-controlled location. Keep passwords and tokens in their credential store rather than the spreadsheet.

2. Record each schedule

Inspect known schedules with SingleSchedule/Get or PackageSchedule/Get, and compare them with ATRS. Record settings missing from the response using the application’s configuration.

Area	What to record
Identity	Installation, installed version, ID, family and name.
Destination installation	Target version, intended folder and owner.
Tableau	Configured account, report/item ID, URL and required permissions.
Output	Parameters, rendering, format and filenames.
Delivery	Recipients, server-side paths and execution-account permissions.
Processing	Package members, data sources, driver, calendars, tasks and supporting files.

For example, a redacted row might describe schedule 101, family report, named “Regional Sales”, with an approved Tableau account/view, landscape PDF output and a test disk folder. Replace that illustration with the actual IDs, dependencies and destinations from your environment.

3. Prepare the destination

Configure the required Tableau accounts and confirm access to the selected content.
Prepare database drivers, connections, mail settings and supporting files.
Check output-folder permissions on every possible execution server.
Record source-to-destination identifier mappings separately.

An identifier from one installation need not identify the same resource on another.

4. Plan testing and cutover

For each schedule, record how to keep destination recurrence inactive, which controlled output will verify the result, and when source delivery will stop and destination delivery will begin.

Coordinate parent workflows, event triggers and applications that can submit work. A stopped scheduler alone does not prevent every externally triggered execution.

5. Review the completed inventory

Confirm every row has an owner, a destination dependency check, a test plan and a cutover plan. After a supported transfer, add destination IDs, test execution IDs and content/delivery results.

Continue with Verify Schedules After a Transfer for the post-transfer checks. Confirm the transfer method with Support first; this guide does not create an export file or prescribe an API import payload.