Skip to content
  • There are no suggestions because the search field is empty.

Migrate PBRS Schedule Definitions Safely

Use the PBRS export workflow to transfer a schedule definition through the REST API.

Review status: Draft for Development and Support review. Routes and models labelled validation required must be tested against the supported PBRS build before publication.

Scope and limitation

The public PBRS procedure states that the REST API export workflow works with all schedule types, but schedules must be exported one at a time. The documentation does not establish a bulk export contract.

Export a schedule

  1. In PBRS, open System.
  2. Select Export Schedules.
  3. Select the schedule and move it into the export selection.
  4. Select Next.
  5. Choose Use REST API for Export.
  6. Enter the PBRS API connection information requested by the wizard.
  7. Select Retrieve Token.
  8. Select Next.
  9. Review the selection and select Finish.

Before migrating between environments

  • Confirm that required Power BI or SSRS accounts exist in the destination environment.
  • Confirm destination folders and delivery accounts.
  • Identify environment-specific URLs, credentials, recipients, paths, and server affinities.
  • Use non-production recipients for the first imported or recreated schedule.
  • Record the source PBRS build and destination PBRS build.

Validate the migrated schedule

  1. Open the resulting schedule in the destination PBRS instance.
  2. Confirm its folder, name, type, enabled state, recurrence, report, filters, parameters, rendering, outputs, and destinations.
  3. Replace environment-specific values.
  4. Run a controlled test.
  5. Verify the generated content and destination.
  6. Record the migration outcome and any manual corrections.

Information Development must add

The final article needs the precise export direction, object format, import or destination behavior, included and excluded dependencies, overwrite behavior, duplicate-name handling, credential treatment, and response or log location. Those details are not established by the current public procedure.

API migration lifecycle

  1. Inventory: capture schedules, folders, account dependencies, parameters, filters, destinations and credentials.
  2. Transform: map environment-specific identifiers and secrets without copying production credentials into test.
  3. Stage: create a small controlled batch in the target environment.
  4. Verify: read back each schedule, execute it, compare artifacts and confirm delivery.
  5. Cut over: move workloads in waves with a documented freeze window.
  6. Reconcile: compare source and target inventories and execution results.
  7. Rollback: retain the source definitions until acceptance is complete.
  8. Retire: delete source schedules only after explicit approval and a validated delete contract.

The PBRS GUI export wizard is an administrator workflow and should be documented separately from API-driven migration.

Keep the two migration methods distinct

Method Use Known limitation
PBRS export wizard with REST API option Administrator-led transfer from the PBRS interface Published procedure exports one schedule at a time
Programmatic REST migration Repeatable inventory, transform, create/update and reconciliation workflow Full CRUD, dependency and bulk contracts require validation

Do not describe the GUI wizard as a bulk API or assume that it provides a portable, secret-free schedule definition. Confirm what the export includes, its destination behavior, duplicate-name handling and credential treatment.

Documentation standard: Record the PBRS build used for verification, test in a non-production environment, redact credentials and customer data, and confirm the saved PBRS state after every write.