Firstly, not that it matters much, but you don’t need to have the ‘Expose as a public endpoint’ option checked - that’s only need if you’re triggering the workflow from an external source via the API.
Secondly, although it doesn’t really matter what name you give your keys, calling it ‘contactType’ could be confusing, as it relates to an individual ‘Contact’, not a contactType.
So I’d rename it, either ‘Contact’, or even something like ‘Contact To Change’. That way it will be clearer exactly what you’re doing, and be less likely to cause any confusion.
Then in the workflow add an action to ‘Make Changes to Thing’ and the thing to change is the ‘Contact To Change’ (referring to an individual contact).
The field to change is the ‘contactType’ (the new, currently empty, option set field).
You need to add an option from you option set here, so start with setting the value to
get an option; contactType; all options so you end up with
contactType = All contactType(More...)which evaluates to the full list of contactTypes…
Then you need to add a filter to match the specific contactType you need to the old text contact type value.
Assuming that your new ‘Option Set’ contactTypes have the same name (Display) as the old text values, then you just need to match an option set’s Display to the old text value…
So next add the filter, with the following constraint…
This contactType’s (referring to the option from the option set)
Display (the name of the option)
Contact To Change’s (the particular contact who’s record is being modified)
Contact type (the old ‘text’ value)
That will match the new Option that you want to set to the old text value.
Then you need to add ‘first item’ to make it into a single option…
Then you just need to run that workflow on your list of contacts.
The simplest way to do it is from your App Data tab, just select a view of your contacts and click the ‘Bulk’ button in the top right corner. Then you can run the workflow on your entire list of contacts (you’ll need to do it separately for the dev and live database, so you’ll need to make sure you publish the workflow to your live app before it’s available to run on the live database).
I’d run it on your dev database and check it has worked correctly before running it on your live data.