migrate from 2017 lts to 2019.1

i have a game made with 2017 LTS and now I want to migrate to 2019. What would be the best way, first migrate to 2018 and then to 2019 or migrate from 2017 to 2019 immediately ?

Whatever approach you take, just be sure to make a backup first.

I typically prefer to take small steps rather than doing everything at once. For example, if you go from 2017 to 2019 and something doesn’t work, it might be tough to figure out what or why. But if you go to 2018.1 first, you can often find more targetted information about things behaving differently in 2018.1. It’s more tedious to go step by step, but I’ve found it to be easier overall. In this case, I’d recommend 2018.1 first, then 2018.3, then 2019.1. You could throw 2018.2 in there, but I don’t remember that as being as significant a change as 2018.3 ended up being with its new prefab workflow.

2 Likes

When you migrate, be aware of assets that have moved to the Package Manager, such as TextMeshPro and ProBuilder. In each case, there are special instructions on how to convert these assets to the Package Manager version without breaking the GUIDs.

1 Like

I’d recommend something similar, though instead of 2018.1 and 2018.3, I’d go with 2018.1.9 and 2018.4.3 to pick up any post initial release bug fixes which may affect migration. 2018.1.9 is the last version of 2018.1, and 2018.4.3 is the latest version of 2018.3.