General information for a cloud migration
Prerequisites for a cloud migration
Limitations and obstacles to a cloud migration
Open Documentation Menu
How do I prepare for the document migration?
Overview
The section will show you how to prepare for a document migration. You will learn the necessary steps and prerequisites.
Prerequisites
A cloud tenant with d.velop documents has already been purchased and you have access to the tenant.
You know the prerequisites for a cloud migration and the limitations. You have ensured that your system environment meets the prerequisites.
You have finished the basic configuration of the cloud tenant (guide).
Necessary components
Component | Version |
|---|---|
Cloud migration toolkit | None |
Latest version | |
Migration API (cloud) | None |
d.3 server in the source system | 8.x or higher |
This is how it works
Preparing to configure the repository
Once you have ensured that the prerequisites are met, prepare to configure the repository with d.velop cloud migration toolkit.
To do this, upload the current d.3 backup file (master data, master data export). If not all users are contained in the backup file, you can provide the missing users in the toolkit using a CSV file.
Note
To avoid errors in the migration, all users in the system should be included in the mapping. Include all users, even those who are listed as editors or creators in documents, for example.
Mapping the users
Mappings are used to link the users from the source system to the users in the cloud.
In the toolkit, select User and group management > Edit user mappings.
Map the users from the source system to the corresponding cloud users. All documents whose owners or editors are on-premises users are mapped to the corresponding cloud users during the migration.
Save the user mappings.
If you cannot map a user from the source system to a cloud user, you can set up a fallback user in the cloud system. When carrying out mapping, you can enter this fallback user for the remaining users so that documents are migrated to the fallback user. This procedure may be necessary if there are users who were active in the source system in the past but have since left the organization, for example.
Note
We recommend mapping all users from the source system. Otherwise errors may occur during the document migration.
Creating a user to use the d.velop documents migration API
Define a user who is permitted to use the migration API. A guide can be found in the following KB article: https://kb.d-velop.de/s/article/000002002
Enabling the export API
Enable the export API (guide).