if you haven't already, install sync it migration Demo Application DA Organization
Be sure that the Demo App is installed - the Demo version only allows for this app to be migrated
No, Sync iT is recommended by OutSystems and must adhere to specific rules. One such rule is the exclusive use of the OS_RUNTIME database user, which lacks the permissions to disable constraints. While Sync iT maintains the relationships between entities, it does not guarantee that the primary key values will remain the same. However, this setup ensures that no additional permissions are required to operate the tool.
Unfortunately, only the data from OutSystems applications is eligible for migration.
No, within OutSystems, a null date is represented by the default date 1900-01-01. Using NULL values does not align with OutSystems best practices.
Yes, this is feasible only if the data model remains consistent across both versions.
Yes, migration is feasible under the following conditions: - OS 10 to OS 10 - OS 10 to OS 11 - OS 11 to OS 11
No, these are System Entities, which are not covered by Sync iT's migration capabilities. The only exceptions are Users and related entities such as Group and UserGroup, along with BPT entities.
No, Sync iT is solely designed to migrate application data.
Yes, there is an option available to migrate not only open processes but also completed ones.
No, such a migration is not supported.
Yes, it is feasible to select specific tenants for migration.
No, real-time synchronization is not currently supported.
As of now, this is not possible. The current process involves deleting the entities at the destination at the start of the process and then migrating all the data.
Data is securely migrated from the Destination to the Source over a HTTPS connection, following a compression and serialization process at the Source.
Yes, Sync iT includes a feature that allows data masking to protect sensitive information.
No, exporting data to a file is not supported by Sync iT.
No, it is not necessary to take applications offline. However, it is recommended to perform migrations during periods of low or no usage to minimize the risk of data inconsistencies.
Yes, you have the option to either migrate all users or only those users associated with specific roles of the applications being migrated.
No, all entities that have relationships with the selected entities are also migrated to ensure referential integrity, regardless of whether they were specifically selected.
No, the snapshot feature is intended to support specific use cases such as demos or training and is designed to back up only the data of the entities included in the defined plan. It is not suitable for storing large amounts of data, and the snapshot data is stored within the OutSystems database.
Yes, it is possible to modify a migration plan until it runs once. Subsequently, you should utilize the clone migration plan feature to make any adjustments.
The Destination environment connects to a REST API in the Source environment. API requests are restricted by a code and a token defined in the Source and configured in the Destination.
For licensing reasons, Sync iT initially migrates new users from the source environment as INACTIVE. However, this behavior can be overridden via a SiteProperty, if necessary.
Yes, Sync iT supports the use of integration APIs, allowing you to incorporate the execution of a migration plan into your CI/CD DevOps pipeline.