FYI. Based on the documentation, the migration path from SharePoint (SP) 2013 to SP Subscription Edition (SE) is to go to SP 2016 and then you can go to SP SE.


However, I discovered something very interesting by accident. I was practicing the migration in a development environment and for one of my content databases, I forgot to do the SP2016 upgrade. I was able to run mount-spcontentdatabase on a SP2013 content database and it upgraded successfully.

I didn't notice any major issues after doing so.

If SP SE didn't have the migration code to upgrade the SP 2013 content database, I would think that the Mount-SPContentDatabase powershell would display an error indicating the schema version is too old. It appears that SP SE has the migration code to upgrade from SP2013 content dbs (upgraded to recent SharePoint CU versions).

  1. Has anyone else tried migrating a content database directly from SP2013 to SP SE?

  2. Any recommendations on whether we should or should not take the shortcut of migrating the content database directly from SP2013 to SP SE?

1 Answer 1


reasons I should take the extra time upgrading the content db to SP2016 before migrating to SP SE?

Supportability from Microsoft when something goes wrong.

  • That's the obvious answer. Modified the question slightly to see if anyone else has tried the direct upgrade approach. I am going to ask Microsoft directly, as well. For production, I'll likely take the extra time do go to SP2016 first unless Microsoft changes the documentation indicating the SP2013 to SP SE path is supported. Dec 2, 2022 at 1:49
  • The PG has been firm on N-2 for upgrades since the pre-betas of SPSE.
    – user6024
    Dec 2, 2022 at 4:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.