Migrating Between Modules of Odin Automation > Migrating from Linux Shared Hosting to WebHosting Linux > Known Limitations

Known Limitations

• If FTP username conflicts occur during migration, the names of such FTP users will be changed to the ones suggested by the system (for example, k100010). Initial user names will not be restored after a reversion.
• Migration cannot be performed to a web server or cluster that does not have any websites with access over FTP.
• Migration of parked domains cannot be performed to a web server or cluster at which there are no parked domains.
• To prevent the loss of application data during migration, the source and target service templates must use the same resource types for SaaS applications.
• Instances of the ‘Service Automation for Web Presence’ (centralized) SaaS application cannot be migrated.
• After migration, the content of HTTP and HTTPS directories of the migrated subscriptions will reside in separate directories, even if the target service template has the “Separate HTTP/HTTPS directories” parameter set to “No”.
• Unsupported services ('MS FrontPage', 'FTP Anonymous access', 'AWStats Web Statistics', 'Urchin Web Statistics Service' and legacy WebApps‘MS FrontPage support’ and ‘anonymous FTP access’) will be unprovisioned from subscriptions before migration.
• If FTP access by exclusive IP addresses is not available after a reversion, ensure that /usr/local/etc/proftpd.conf.pem contains an INCLUDE directive for every virtual host configuration file in /usr/local/etc/proftpd_vhost_confs_pem/. For example: INCLUDE /usr/local/etc/proftpd_vhost_confs_pem/8.
• PHP is always switched on after migration from Linux Shared Hosting to WebHosting Linux hosting.
• Backups can be migrated only if they are stored on a Linux-based server.