We want to move fully from Connect on Forge to Forge before the end of this year.

We will try to make the migration as smooth as possible for users. Our intention is that customers should not have to rebuild their setup, learn a new process, or contact support, but given the differences between Connect and Forge, some changes may be unavoidable.

• Existing configurations working as they are.

• Workflow rules, validators, conditions, post functions and related settings unchanged.

• Post-function execution logs.

• We will try to keep core app behaviour the same for customers.

However, Connect and Forge have significant architectural differences. When it is not possible to keep things exactly as they are, we will first deprecate the affected modules and create new ones that are as close as possible to the originals. We will be transparent about every change: customers will be informed ahead of time and given enough notice before any deprecation or breaking change takes effect.

1. Review all current Connect on Forge features, data, configurations and logs.

2. Build Forge support for the existing configuration format before moving customers.

3. Test internally with real scenarios and edge cases.

4. Remove legacy dependencies only after the migration is confirmed as successful.

• Have a rollback and fallback options.

• Monitor configuration errors and workflow execution errors.

Keep the message simple and transparent: we are moving the app to Forge to improve long-term reliability. We will try to minimise the impact on customers, but some changes may be needed. When changes are necessary, we will communicate them clearly and in advance.

• All customers are migrated before Dec 31, 2026.

• All Connect app functions are migrated to Forge or replaced with equivalent Forge modules that are as close as possible to the originals.