Know what the update changes
Read the developer's release notes for the version being installed. A routine maintenance update and a major version change may have different effects on plug-ins, file formats and system requirements. If an application is essential for a deadline, schedule the change when you have time to test it.
Use the application's built-in updater, official website or system store. Avoid installing an update from an unexpected pop-up on an unrelated page. On a managed computer, follow the organization's update process.
Check whether required extensions or plug-ins support the new version. A compatible main application can still leave a particular workflow incomplete if an add-on has not caught up.
Save the settings that would be tedious to rebuild
Use a supported preferences or workspace export if the application provides one. Include templates, custom shortcuts, dictionaries and other local resources that matter to your work. Do not assume signing into an account synchronizes every customization.
Take screenshots of a few important settings when no export exists. They are useful reference material, though they are not a replacement for backing up actual project files. Keep account credentials out of those screenshots.
Back up representative projects before the update. If the new version changes a file format when saving, retain an untouched original until you know whether an older version can still open it.
Update, then run a complete task
Close the application normally after saving work and allow the update to finish. Restart if the installer requests it. Do not launch multiple copies while installation is still in progress.
Open a copy of a familiar project, check the workspace and perform the steps that matter: import, edit, save, export and reopen. An application starting successfully does not prove that its whole workflow still works.
Verify any device connections, fonts or plug-ins used by that project. If a setting has changed, restore it through the application's supported controls rather than copying undocumented files from an old installation.
Keep a clear recovery route
If the update causes a problem, record the exact version and symptom before making further changes. Consult the developer's known issues and rollback instructions. Some newer project formats may not be compatible with an older application, which is why the untouched copy matters.
Do not uninstall the application impulsively if it stores local data or custom resources. Check what its uninstall process removes and whether you have those items elsewhere.
Once the updated version has handled normal work reliably, keep the useful settings export with your backup records. It can help with the next update or a future move to another computer, turning a one-time precaution into a reusable recovery aid.
