Migration from Public Cloud to Private Deployment
Migration Content
- Accounts [excluding external portal accounts, passwords will be reset to a fixed value]
- Departments
- Positions
- Reporting Relationships
- Applications and Application Configurations
- Worksheet Structures and Worksheet Configurations [Word print template files need to be uploaded separately]
- Workflows [excluding execution history]
- Statistics
- Roles
- Worksheet Row Data [excluding operation logs]
- Discussions
- Attachments
- Pending Workflow Messages (only unfinished ones)
💢 The collaborative suite data will not be migrated, including friend relationships, etc.
💢 To ensure compatibility between the data structures of the two environments, it is required in principle that the versions of the public cloud and the private deployment environment must match (correspondence: https://docs-pd.mingdao.com/version). If the private deployment does not yet have a version corresponding to the public cloud, it is strongly recommended to wait until the private version is released before migrating.
💢 About one week before the migration, evaluate the overall data volume based on the public cloud organization number (mainly attachments). If the data volume is large, the attachments will be migrated first in advance, and the incremental data will be migrated on the same day.
💢 The migration will take approximately 6 hours. Once the migration starts at the agreed time, any data generated by customers continuing to use the public cloud will not be migrated.
Operational Steps
-
Clear data in the private deployment environment (if there is existing test data)
-
Export relevant data files based on the corresponding public cloud organization number (
MySQL,MongoDB,File) -
Data Cleaning
-
Data Import
-
Clear Redis
-
Restart Services