A migration from one database platform to another might work, but is not officially supported. We haven't tested such a migration, which means doing so could carry potential risks to your site.
One idea of how this migration could be possible is to transfer the data from one Sitefinity site to another via API usage. By creating a Sitefinity site with a MsSql backend database and then, using the Sitefinity API, get data from one site and make it available in the other site. This could be done by connecting the providers for modules and make them available in the MsSql-backed site.
For example, to connect the News module providers between the two sites:
1. Add a connection string to the MySql site by going to Administration > Settings > Advanced > Data > Connection strings and create new connection string "Test".
2. Go to Administration > Settings > Advanced > News > Providers and create new provider, copy the settings from the default NewsProvider and add two Parameters to the new provider:
and another parameter:
Value: Test (this is taken from step 1)
Restart the application and now the news module will have the data available from the other database.
With this to transfer the data from the other database to this one, by calling the provider. For example:
This will query the data from one provider, which you can then and transfer it to the other.
Revision history can also use the above approach. The manager class for working with revision history is VersionManager and also providers can be added from Administration > Settings > Advanced > Version.
Again I would like to mention that a scenario such as this has not been tested on our end.
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal
and vote to affect the priority of the items