Valid for versions 12.5.0+
If you follow our best practices when working with ONE Web Application, there is typically no need to migrate entities between different environments. The recommended approach is that end-users interact with a single instance of ONE Web Application that is usually deployed in a production environment. The lifecycle of individual entities in this environment is managed through entity workflows and versions. Another instance of ONE Web Application should also be available on a non-production environment and is intended for administrators and IT staff for testing upgrades, patches, and any changes in the application configuration before applying any updates on the production environment.
However, if needed, certain entities, for example, only rules or only projects, can be migrated using the ONE API. The migration process is typically handled through an IDE plan calling the API (JSON Call step) and it covers specific migration requirements, such as handling the permissions of migrated objects, resolving conflicts, determining whether to migrate dependent entities, entity history, associated comments, and more.
Admin users can access the list of available API calls from the ONE Web Application. For more information about working with the API, see ONE REST API Reference.