Best way to Migrate Sage 200 2011 SQL database without downtime?

Hello,

We are currently using Sage 200 2011 on a SQL 2008 R2 cluster (Windows Server 2012).

We will soon be upgrading Sage to 200 2016 which no longer supports SQL 2008. So I am building a new SQL 2016 Server (Windows Server 2016) and plan to migrate the databases to it.

I want either little or no downtime during this.

Options I'm thinking about:

Adding the new server to the SQL cluster, failing DB's over to it and removing other members. But I am assuming you cant add a SQL 2016 member to a SQL 2008 cluster.

Temporarily setting up the new Server with SQL 2008, add as a member to the cluster. Failover to it. Remove other members. Then an in place upgrade to SQL 2016

Migrating databases 1 by 1 (backup and restore) from the old SQL to new and re pointing the database to the new server in Sage configuration.

Using an alias somehow? I'm still...