There are documents about the changes from previous versions.
Generally not a lot of things get unsupported in Base SAS. Other modules may have procedures replaced/consolidated/expanded or have some defaults change.
Strongly suggest before any migration that things that are stored in CATALOGS that you may use can be recreated with code or prepared for export so that they may be imported into a later version. Examples are Format catalogs. Without the code or data sets created with Proc Formats Cntlout option may be extremely difficult to recover across version boundaries.
The Boston Area SAS Users Group is hosting free webinars! Next up: Lisa Mendez & Richann Watson present Get Tipsy with Debugging Tips for SAS® Code: The After Party on Wednesday Jul 16. Register now at https://www.basug.org/events.
Is your SAS server architecture and the OS it's running on changing? Are you changing user interfaces - SAS IDE, SAS Enterprise Guide, SAS Studio? Any changes here ae likely to have way more impact than any language feature changes.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.