o
The contents of this guide are intended for Comalatech customers who have decided to migrate Comala Document Management to cloud and explains where to start with your Comalatech app migration.
If you haven't made a decision about your migration, read this article for more information.
| Panel | ||||
|---|---|---|---|---|
| ||||
Confluence CloudThe benefit of a cloud environment is that your cloud app will always have the most up-to-date features available. It's also less demand on your own IT infrastructure support needs. More information on benefits of using the Atlassian Cloud platform can be found on Atlassian's Why Cloud? As we progress through the cloud journey, we will continue to work toward feature parity between our server/data centre apps and our cloud apps. In the meantime, not all features available on our server apps are available for cloud. Please
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
In October 2021, Atlassian announced their intention to retire their self-managed server offerings as they move their platform to the cloud. Atlassian intends to complete this journey by 2024 which means existing customers that want to continue to use Atlassian's products, will need to migrate to their cloud or data centre platforms |
FAQ Migration Planning
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
The migration journey
Get familiar with Comala Document Management for Cloud
As there are differences between our Server / DC and Cloud products, we recommend that you create a test Cloud instance and install a free trial of Comala Document Management to understand the capabilities...
Comala Document Management for cloud has the following workflows available for you to get started right away:
You can also build custom workflows using the Workflow builder.
Migrate
Follow the migration process steps to
- plan for migration
- prepare your cloud site including installing the Comala Document Management app
- use the Confluence Cloud Migration Assistant to migrate your content
- recreate custom workflows in JSON markup in your cloud site and apply to your content
You should allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.
Last step, initialize your content
The final step in migration is to confirm the content workflow state for document and any other configuration tasks you identified in planning the migration. You can initialize the state for al the content in each space or by individual document. This is needed to update the document state correctly for those pages that you have not visited yet. Otherwise, the state displayed for these documents in the Workflow Report will be listed as “not initialised”.
Unfortunately we are only able to migrate the current state for content. This is added as an attachment to each document in cloud. If you need a record of the workflow history for each document for audit and compliance, the recommended solution is to maintain your server instance in read-only mode.
Find directions here.
A feature comparison list for all our Comala Document Management Family of apps can be found in our Feature Matrix for Comala Document Management Server and Cloud apps.