Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Data migration for Agile Studio

Updated on December 12, 2023


This content applies to On-premises, Client-managed cloud and Pega Cloud environments

Attention: This documentation has been moved to the new documentation site:
This documentation is no longer being maintained. It is out of date and pending deletion. Please update your bookmarks.

Agile Studio is included with Pega Cloud.  If you have been using Agile Studio with your source system, any Agile Studio data in the source environment must be migrated separately from the main Pega application data migration, because they use different databases.

If you have customized any of the rules in the Agile Studio application, then export those customized rules in a RAP, and import them into the Agile Studio node in Pega Cloud. If you have not customized your Agile Studio application, but are using it “out-of-the-box,” then it is not necessary to copy the application rules into Pega Cloud.   

Work with the Pega Cloud team to migrate your Agile Studio data into your Pega Cloud environment.  

IMPORTANT:  Stop using your Agile Studio system until the migration is complete.  Otherwise, changes to the data in the old system are not migrated and are lost.


Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us