Integrations & Developments
DO
Daisuke Okuda
·Posted in Integrations & Developments

Automation Features Migration: Is the guide sufficient for production & how to handle legacy coexistence?

Hi community,

We are currently preparing to migrate our monday.com Marketplace app from the legacy automation features to the new automation features, based on the official documentation below:

From our understanding, the migration guide seems to describe the required implementation steps.
However, we would like to confirm whether following this guide is sufficient for a complete and production-ready migration.

Since our app is already used by paying customers and relies heavily on automation functionality, we would like to clarify a few points regarding the transition period where both legacy and new automation features may coexist.

We are also proceeding with the migration in parallel.

We would greatly appreciate any insights from the monday team or partners who have already gone through this migration.

1. Discovery of the new automation feature

  • How will users discover and create automations using the new automation builder for our app?

  • Once implemented, will our new automation feature automatically appear in the Automation builder UI?

2. Migration path from legacy automations

  • How are users expected to migrate from legacy automations to the new automation version?

  • Will monday provide any UI guidance, recommendations, or migration mechanisms to support this transition?

3. UI behavior for legacy automations during the transition period

  • During the coexistence period, how will legacy automations be displayed in the UI?

  • Will they be marked as deprecated or hidden from new automation creation?

4. Creation of legacy automations going forward

  • Until when will users still be able to create new automations using the legacy automation mechanism?

Our goal is to ensure a smooth transition experience for our users and provide clear guidance during this migration.

Any clarification or additional documentation would be highly appreciated.

Thanks in advance!

Best regards,
Daisuke

api
api & sdk
automations
integrations
1