Exact Online Premium connection: changes in `timestamp` of sync tables

An update on how to connect to exact online premium would be much appreciated. Our company moved yesterday from PRO to PREMIUM.
We are unsure how we should update all our Invantive scripts and connections/settings.xml.

It seems the Sync APIs have been migrated but issues in the TIMESTAMP running QueryTool 25.0.209:

Found some partial findings:

The change to Premium impacted the timestamp in the SYNC APIs. Exact sales exec said no impact would occur, but this is wrong.

In case the division is moved to another database in Exact Online the timestamp values will be reset. Therefore, after a division is moved all data needs to be synchronized again in order to get the new timestamp values. To see if a division was moved, the /api/v1/{division}/system/Divisions can be used. The property DivisionMoveDate indicated at which date a division was moved and this date can be used to determine if it is needed to synchronize all data again.

Since the Exact Online database has been moved to another SQL Server database, there are changes on the sync APIs.

In this case it will mean that all Incremental tables will be completely reloaded. The counter behind timestamp is based on a database-specific implementation feature of SQL Server. A reload will take place automatically.

This reload will cause more API calls to be made the coming day(s) until the data set has been loaded into the incremental cache.