Kevin, You shouldn't have to use SQL scripts to move your data from old to new. MS supplies a new upgrade toolkit with each minor and major release. Those toolkits include all the migration scripts. There are exceptions. When you create your table extensions(one for each modified base table), you need to move the data from the modified tables to the extended table. I would do this in code. We have a generic codeunit that does that. It uses RecRef, FieldRef. This allows you to use the same methodology for moving data for each company, table field etc... SQL Scripts are one time use and may not seem like a problem, but after performing hundreds of upgrades over the past couple decades, I've seen nightmares with SQL scripts. They are un-maintainable and largely for one time use. Perhaps my opinion is biased because it's coming from a Partner perspective where repeatability is huge.There is currently one upgrade toolkit for the latest, BC19 that upgrades you from BC14 to BC19. If you're going to SaaS, it's a button push to replicate. To quantify the work you need to perform prior to your next upgrade, look at your modified objects in Object Designer, which still exists in BC14. The count of the modified base objects (the objects that aren't yours, i.e., MS's, ISV's) will be the count of new objects needed that you will put those customizations and subscribe to events to execute the code as it was before. Once you've done that, you are ready to upgrade.
If you've found this thread useful, dive deeper into User Group community content by role