Measurable Success «10 Checkpoints for Future-Proof Enterprise CMS» White Paper
Measurable Success - White Paper

Migrating to

Migrating to

Migrating an existing application so that it uses is easy and requires just a few simple configuration changes. You can try out the migration in your local development environment and deploy it to a staging server before taking it into production.

Prepare the application

You require a modern SDK version. Please upgrade to version 1.15 or later.

In order to allow interaction between and your website, your Content Security Policy needs to be adjusted. If you are using _headersCsp.json, add "https://*" to the frame-ancestors list. See how it’s done in the Scrivito Example App.

That’s it: Your application is now ready for

You can try it out by visiting Just put the URL of your application into the path. For example,

With a local development server, you may need to handle ‘‘mixed content’’ errors.

Redirect users to the new UI location

Once you’ve tried out and everything works fine, you should instruct your application to always use it. You can do this by adding the adoptUi: true configuration option to Scrivito.configure (Example).

This creates a redirect from the previous /scrivito URL to the new URL to make sure that no user inadvertently uses the old UI anymore.

Remove no longer needed configuration settings

Your application probably includes a few configuration settings that pertain to the old UI location. These are no longer needed, so you can simplify your application by removing them. As a nice side effect, the redirect mentioned is also performed faster, once these legacy configuration settings have been removed.

  • Remove copying of scrivito/index.html (Example)
  • Remove development rewrites for scrivito/* paths (Example)
  • Remove production rewrites for scrivito/* paths (Example)

That was it! You’ve now fully migrated your Scrivito app to Enjoy!