0

We have an on-premises SharePoint 2013 and we want to migrate/upgrade it to SharePoint 2016. so which approach we need to follow? Migrating the farm or upgrading it and why?

Second question, if we have Farm solutions (including Event Receivers) & Sandbox solutions inside SharePoint 2013 will they work as-is inside SharePoint 2016?

Thanks

Improve this question

2 Answers 2

Reset to default
1

You would be better off upgrading to SharePoint 2019 or even SharePoint Server Subscription Edition.

Mainstream support for SharePoint 2016 ended in 2021 and the extended support ends in 2026.

Improve this answer
2
  • the customer might consider this in the future.. my question is about moving from 2013 to 2016 .. and i am asking if we should consider upgrading or migrating?
    – John John
    Dec 5, 2022 at 12:11
  • 1
    My advice is not to migrate/upgrade to a version of SharePoint that is out of mainstream support. Upgrading between versions of SP is usually better, since database migrations usually have a much higher percentage of success (usually 100%) where as file migrations can involve more errors.
    – Callum Crowley
    Dec 5, 2022 at 14:30
1

From my experience is always better to migrate. For one particular reason, it will give you a clean slate.

No software product is perfect, and same goes for OS, having a fresh clean install of OS and SP Binaries goes a long way of clearing many small issues that are happening on OS patched over long time.

I tried only one in place upgrade and had a lot of issues, and switched to migration in the end.

Improve this answer
3
  • but is doing migration the more standard way? so we do not have to worry about any issues and redeployment of the custom solutions?
    – John John
    Dec 6, 2022 at 12:52
  • You will always have to worry about custom solutions (and it doesn´t matter if you are doing in place or migration), You will need to either upgrade them or make them work in compatibility mode.
    – Marek Sarad
    Dec 6, 2022 at 15:24
  • We are currently migrating large custom solution from SP2013 to SP2019 and it took us 1FTE 2 months to rebuild it.
    – Marek Sarad
    Dec 6, 2022 at 15:27

Your Answer

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

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