Skip to main content

Migration from Public Cloud to Private Deployment

warning
  • The versions of the public cloud and private deployment environment must match (see: https://docs-pd.mingdao.com/version). If the private deployment does not yet have a version corresponding to the public cloud, wait until the private version is released before migrating.
  • About one week before migration, evaluate the total data volume based on the public cloud organization number (especially attachments). If the volume is large, attachments will be migrated in advance, with incremental data migrated on the migration day.
  • Once migration begins, any data generated by customers continuing to use the public cloud will not be migrated.
  • Collaborative suite data (friend relationships, etc.) is not included in the migration scope.
  • Document preview may differ slightly due to differences between the private deployment and public cloud document preview components.

Overview​

Migrate data from a public cloud (SaaS) organization to a customer's private deployment environment. The migration is performed by the official technical team and takes approximately 6 hours. Data generated on the public cloud during the migration will not be synchronized.

Migration Content​

Organization Structure​

  • Accounts (excluding external portal accounts; passwords will be reset to a fixed value)
  • Departments
  • Positions
  • Organization Roles
  • Reporting Relationships

Application Configuration & Data​

  • Applications and application configurations
  • Worksheet structures and worksheet configurations
  • Workflows (excluding execution history)
  • Unfinished workflow pending messages
  • Workflow plugins
  • Application roles
  • Charts
  • Custom pages
  • API integrations
  • Worksheet row data (excluding operation logs and custom views)
  • Worksheet record discussions
  • Attachments

Operational Steps​

1. Clear Private Deployment Data​

After confirming the private deployment environment is fully deployed and accessible, clear existing data (if there is test data):

  • Clear MySQL
  • Clear MongoDB
  • Clear Redis
  • Clear Elasticsearch

2. Export Public Cloud Data​

Export relevant data files based on the corresponding public cloud organization number:

  • MySQL data export
  • MongoDB data export
  • File storage (attachments, etc.) export

3. Data Cleaning​

Process the exported data to ensure compatibility with the private deployment environment:

  • Reset all account passwords to a fixed value
  • Update organization ID binding
  • Remove configuration information bound to the public cloud environment
  • Resolve data structure incompatibilities

4. Data Import​

Import the cleaned data into the private deployment environment:

  • Import MySQL data
  • Import MongoDB data
  • Import file storage data

5. Restart Services​

Restart all microservices in the private deployment environment for the new data to take effect.

Post-Migration Verification​

After services restart, log in to the system via the private deployment access URL and verify:

  • Account login works (using the reset password)
  • Organization structure (departments, positions, roles, reporting relationships) is intact
  • Applications, worksheet structures, and data are complete
  • Attachments are accessible
  • Workflows can be triggered and executed
  • API integrations function correctly