Migrate from Classic
Last updated
Was this helpful?
Last updated
Was this helpful?
If you have any complex custom code in your Ucommerce Classic solution, we recommend contacting us before you start your migration. It's also important that your solution meets our prerequisites, which are listed .
First, you must upgrade your database to the latest version of Ucommerce 9. If you're already on a version of Ucommerce 9, this should be easily accomplished by upgrading your Ucommerce package and starting your application. If you're using a regular SQL Server for your database, make sure that your database has a SQL Server compatibility level of at least 130.
We recommend using our templates for easy installation of Ucommerce Next-Gen. Information on them can be found .
Once you've created a new project from one of the templates, make sure you add the connection string for your database. When this is done, you're ready to start the project and it will migrate the database for you.
After this, go to the Ucommerce backoffice at /ucommerce and verify that your data has been migrated.
To migrate custom logic, we recommend getting an overview of which parts of the solution are custom-built and then using our documentation to guide you on the changes needed.
The main differences between Ucommerce Classic and Next-Gen are how dependency injection works, application setup, database access, and pipeline registration. Some articles that might be of use to you are listed below:
N.B.: All custom logic must be ported from the .Net framework to .Net 8.