Yes to both questions.
In Microsoft Designer, you can use the Set Variable action (or similar actions) to retrieve the "UI Version" Property of the List Item. Then use the If any value equals ... action to validate if the version ends with ".0", see the following screenshot:
In a Power Automate built Flow, you can do something similar by using a ...
I got this working by registering the workflow service with a new scope for instance:
Register-SPWorkflowService -SPSite "http://my.sharepoint.com" -WorkflowHostUri "https://myworkflowhost.com:12290" -scope "SharePoint01" -AllowOAuthHttp -Force
Re-register SharePoint Workflow with -Force Key on existing URL on the workflow member server,
Register-SPWorkflowService –SPSite "http://my.sharepoint.com" –WorkflowHostUri "https://my.sharepoint.com:12290" –AllowOAuthHttp -force
Check AAM settings, any reference for the old url present?? Only place for the workflows to get the url would be from the AAM ...
For restore an earlier version of workflow, you can use SharePoint designer. Find your workflow with issues, and restore it to an earlier version.
Go to the folder All Files in SharePoint designer (use SharePoint
Designer 2010 if connecting with a SharePoint 2013 farm or you'll
get a server busy error), when you have opened your site
Open Workflow folder
Per my test, when we create a new enterprise wiki page in SharePoint online, by design the version of this page is 2.0 instead of 3.0. As the below picture shows:
I think that's why the workflow doew not get fired. As a workaround, you could delete the condition If current Item: Version not equals 2.0 in your workflow.
If else condition will be the best choice in designer workflow while nested if condition may be complicated if you have more conditions. If you have access to Flow, there are much easier way to do it with a switch condition to handle occasions like this.
As far as SharePoint content database migration is concerned using the detach and attach method it will migrate everything - all designer workflows along with infopath forms. And we can not migrate directly from SharePoint 2010 to 2019. The sequence is 2010->2013->2016 ->2019
Few key points to remember:
Complete all running workflows in SharePoint 2010 ...
A better but more complicated way is to create site workflow, that will start every day and will do the calculation of days till subscription date and then (if 7 days and status eq unpaid) send email.
An easier way is to create list workflow and set pause until subscription date minus 7 days, then check status and send email.
The third way is to use ...
If you don't need to restore the archived data (list items) in SharePoint and need archiving purely to comply company's data retention or other compliancy policy look at the 3-rd party tool called Listman.io.
Depending on your requirements it could auto archive list items once per day based on some filtering criteria, download attachments, delete/modify ...