Go Live Checklist (moving your workflow to production)

Complete all development and testing in the staging environment.
Conduct User Testing to confirm the workflow functions as designed and confirm the design that has been implemented is fit for purpose for actual end-users who will be using the workflow following go-live. Read: UAT guidelines
Export the workflow from Staging and begin the import process on Production.
The import wizard will request additional information such as defining user roles, asking to upload CSS attachments, stage document attachments, eSignature document attachments, or data sources for form fields and prepopulation rules. Complete these aspects of the import.
Keep your workflow open in a separate tab in Staging so it’s easy to gather or reference all this information for the import wizard.
After the import is complete, compare the Workflow-level permissions between the Staging and Production versions. You may need to recreate tenant-level Roles and Departments in Production as they appear in Staging in order to properly configure these permissions.
Verify everything else necessary for the workflow’s success is configured: User imports, Roles, Departments, environment-level permissions, dashboard views, data sources, and document library.
Publish your workflow!
Conduct sanity tests on the Production workflow.

Staging and production are two separate environments. To keep your workflows in sync all changes will need to be made in both.
Make all changes in staging, test thoroughly with multiple users and scenarios before moving to prod. This allows you to make updates without downtime in production.
If you make small changes in production (like fixing a typo or text change) you will need to do the same in staging.
Reminder: Any record in progress will not see workflow changes. Only new records initiated after the update will show the update.
When moving from staging to prod make sure all links, data sources, and APIs are pointed to their updated counterparts in Production.