Migrating resources from 1.x Remote services to Publishing Document Builder

In version 2.1.1 and later, the Remote services are deprecated. You can migrate your resources from the Remote services server to Publishing Document Builder after upgrading.

Before you begin

You must have administrator access to migrate resources. You can migrate the following resource types:
  • JavaScript files
  • snippets
  • style sheets
  • templates
Reference templates and document specifications must be migrated manually. Report schedules cannot be migrated but you can create new report schedules in Publishing Document Builder.

Resources owners are retained in Publishing Document Builder as long as the owner is a valid user in Publishing Document Builder. For example, if Requirements template from Remote Services 1.x is owned by the user Bob, this template is added to Publishing Document Builder with Bob as owner. If the owner does not exist in Publishing Document Builder, it will still be migrated with the same username. These resources can be migrated manually by the new owner.


  1. In the product banner, click Migrate resources.
    Tip: If you do not see this button, you can enable it by checking the ENABLE_ASSET_MIGRATION checkbox on the Runtime variables tab.
  2. Enter the URL to the Remote services application, for example https://server:port/rpews.
  3. Enter your username and password.
  4. Click Migrate.
  5. When the migration is complete, you can see the results of the migration. Any resources that failed the migration attempt are listed at the top.
    For resources that were not migrated, click the Download link to download the resource to your system. You can then add the resource to Publishing Document Builder manually on the Resources tab by clicking Upload resources.


You can also view previous migration results. This includes all migrations performed by any administrator in the same Publishing Document Builder instance. The migration results are deleted after 100 days.