I have a number of sentence builder action blocks that do not migrate due to unsupported fields. I can create something equivalent or better with the Automation Block feature. However I am seeing speculation or assumptions that if we don’t use the migration wizard on our side that somehow end users when the eventual migration process for them come out won’t be able to migrate recipes directly.
I don’t want to create inferior versions based on the limits of the old sentence builder if I don’t have to. I’d rather create one version that replaces a half dozen variations previously needed. But if we need a one-to-one relationship, that won’t work and I will be forced to create automations that look like duplicates and will be confusing.
Question
Is use of the migration wizard required?
+1
That’s a good point and we’re also going to be cleaning up a lot of automations because the new system supports optional fields and field dependencies.
I was under the impression that all the migration does is re-create automation blocks, recipes and custom fields for you, and that was it. We then delete / update the created app features to fit.
Knowing whether or not there’s a link between the old automations and the new one that would allow customers to migrate is important.
Hey,
Existing automations will keep working on the old infra.
The migration wizard only migrates the integration to the new infra - meaning the existing old infra automations are kept untouched.
If you have the capacity we strongly recommend creating a better experience with the new capabilities of the new infra (like optional fields that you've mentioned).
Regarding the migration of existing automations - this is something that is currently in very early research, it's a very complicated matter & we're researching how best to tackle this.
Rest assured that this is something we're aware of and want to address properly.
+1
That future end user migration is probably going to require us devs to provide mapping patterns from the old blocks to the new blocks - including which fields to leave unfilled when combining. I can’t fathom any way to automate the mapping for a transition. May just be better to have a pointer to which block replaces it - and leave filling in the fields to the customer. My two cents that last solution seems to be the most likely to succeed.
Login to monday.com
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.