Jira Align asynchronous sync lag during zero-downtime migration

The goal is to cut over a small application from Jira Software to Jira Align without downtime while the connector keeps bidirectional synchronization running.

Jira Align maps Features, Stories, and other work items to Jira Software issue types through an asynchronous connector. Updates in Jira Software may take time to appear in Jira Align depending on the sync interval, and simultaneous edits to the same mapped field in both systems can cause data overwrites. The available research does not state whether the connector enforces a maximum lag, a read-only cutover mode, or a conflict-resolution policy for linked issues during migration.

It is also unclear whether sync intervals can be adjusted for a single program, or whether synchronization can be paused for one team without stopping the connector entirely.

Does the Jira Align connector document a maximum asynchronous sync lag for linked Jira issues?

During simultaneous updates, does Jira Align or Jira Software take precedence for a mapped field?

Can bidirectional sync be paused for a single program or team without stopping the connector?