RELATED IDEAS
Migrate/merge environment
We have some customers that are using liquit in an on-premise situation.
But some of them are making the transition to the cloud and saas apps. After using liquit in some cases for 2 years some customers are ready to migrate now to the Liquit Saas Solution.
But a this moment it's not very easy to migrate from on-prem to Saas Liquit.
In our case a lot of rebuilding / work needs to be done, to get the same functions moved to the Saas solutions. As a consultancy partner it's nice to have some work in this, But from a customer point of view its very difficult to pay for this.
Hopefully you can think about this, so customers can easily move to the SaaS solution.
| Product | Application Workspace |
To export items, like the deployment (or packages), and import it to a different (or same) zone.
Add the function to sync other settings (especially deployments) via the Liquit Workspace Connector to an other zone.
By that process, pre-issuing a matter: not having the deployment set to the GUIDS of the packages, but resolveable by name (as the packages which are imported, would possibly get other GUIDS, but the same name as the other zone.