When you plan to migrate on-premises vaults to M-Files Cloud, contact M-Files.
Before you create a replication package to cloud storage, read these requirements and restrictions.
Requirements
The minimum software requirement for the on-premises M-Files Server is M-Files 2015.1. We recommend that M-Files Server uses the latest available version. For more information, refer to M-Files version compatibility regarding API and Replication.
Important: Do not update M-Files Server to the latest available M-Files version
if you have purchased a long-term support (LTS) service for M-Files Cloud. Refer to
our release notes for information about the latest available LTS version.
The TLS 1.2 protocol must be used in the on-premises environment.
All scripts and custom code must be disabled in the vaults. Custom code is automatically removed from
replication packages during import. The removed code includes
these components:
- Calculated values of property definitions (VBScript)
- Validation scripts of property definitions (VBScript)
- Advanced preconditions and postconditions for workflow states (VBScript)
- Workflow state scripts (VBScript)
- Workflow state transition scripts (VBScript)
- Event handlers
Tip: After the migration to a shared M-Files Cloud environment, you
can install signed vault applications and custom vault applications and scripts that M-Files has validated.
Restrictions
These components cannot be transferred with replication:
- Vault applications and UI extensions
- Settings stored in Custom Vault Data
- Advanced Vault Settings
- External mail sources and file sources
- Data exports for reporting
- Login accounts
Server-level configurations are not supported and cannot be migrated to M-Files Cloud. Server-level configurations can include these components:
- Microsoft Windows registry settings
- PowerShell scripts
- Microsoft Windows Task Scheduler tasks
- Custom Open Database Connectivity (ODBC) drivers
- Software installed to the local Microsoft Windows server
