Migrating a SQL Server 2014 AG to a new 2017 AG
The plan sounds great. 
You just need to include a deep UAT (User Acceptance Test) as it is possible that the way that the new version interprets the sentences is a bit different.
For example, every version is going to be more strict with ending each sentence with ;
We made similar migration almost one year ago from 2008 to 2014 and the sentences like:

USE ProductionDB;
INSERT INTO Archive_DB.dbo.Archive_Tbl1 (Field1, Field2)
SELECT Field1, Field2 
FROM ProductionDB.dbo.Tbl1;


We had detected several issues because sometimes the DB was ommited and the new version made a different assumption than the old version. Fortunately we could fix all during the UAT.
Good luck !!!