# Migrate user field to assignee field **URL:** \ **Category:** Get Help\ **Created:** [March 25, 2022, 10:40am UTC](https://community.fibery.io/t/migrate-user-field-to-assignee-field/2663 "2022-03-25T10:40:53Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![uniquelau](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/uniquelau/32/3836_2.png) [@uniquelau](https://community.fibery.io/u/uniquelau)\ **Post date:** [March 25, 2022, 10:40am UTC](https://community.fibery.io/t/migrate-user-field-to-assignee-field/2663/1 "2022-03-25T10:40:53Z")
Hello, We have a bunch of entities that are associated with a **user**. I would like to migrate the **user** field to an **assignees** field. The “Run now” function of automations is ideal for this type of manual migration work. However, it looks like **assignee’s** and **user** do not mapping nicely to each other. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/749572d7a90fe20ab769977db4a56b83aac7bcaf.png) I am wondering do I need to but the single user into an array, and set that against the assignee’s? I’ve had a dig around the formula documentation, but couldn’t find a way to do this. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [March 25, 2022, 10:54am UTC](https://community.fibery.io/t/migrate-user-field-to-assignee-field/2663/2 "2022-03-25T10:54:26Z")
Yeah, you’re on the right track. User field is a many-to-one relation, but Assignees are many-to-many, so you need the formula to return a collection. I think the best way to do it is using a query formula. Something like this should work: `Users.filter([Public Id]=[Step 1 Time log].User.[Public Id])` It returns a collection of Users, limited to only those whose ID matches the ID of the User for this Time log. Which will be a collection of 1 user 🙂 ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [March 25, 2022, 10:57am UTC](https://community.fibery.io/t/migrate-user-field-to-assignee-field/2663/3 "2022-03-25T10:57:51Z")
I did note however that you had a filter for only those logs for a specific user. If that was you’re intent, you could just use Add Assignees with a _Named user_ (or Assign to me, if that’s appropriate) ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/bee4aece30296db6b9d8f9b785bd8ede0bb6b76c.png) ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/911832e3883faefcfebaadc03c3ad3baf6f89f3f.png) ---
**Author:** ![uniquelau](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/uniquelau/32/3836_2.png) [@uniquelau](https://community.fibery.io/u/uniquelau)\ **Post date:** [March 25, 2022, 11:12am UTC](https://community.fibery.io/t/migrate-user-field-to-assignee-field/2663/4 "2022-03-25T11:12:45Z")
Hi Chris, That is helpful thank-you Re: assigned to me - yes this was on purpose, I am the test case 😉 Re: the above - what I have discovered, is my automation actually does work with no changes. However, the automation must **take a while** to run, as I’ve come back to Fibery and I have A LOT of notifications. (It would be very nice to be able to mute those notifications, otherwise, the users will get hundreds of notifications.) ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [March 25, 2022, 11:42am UTC](https://community.fibery.io/t/migrate-user-field-to-assignee-field/2663/5 "2022-03-25T11:42:44Z")
Unfortunately, it’s not possible to disable notifications for when a user is assigned. We have plans to improve the notifications subsystem, but for the time being, there’s no easy fix, sorry. ---
**Author:** ![uniquelau](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/uniquelau/32/3836_2.png) [@uniquelau](https://community.fibery.io/u/uniquelau)\ **Post date:** [March 25, 2022, 11:59am UTC](https://community.fibery.io/t/migrate-user-field-to-assignee-field/2663/6 "2022-03-25T11:59:55Z")
No problem, it’s straight forward enough to use a relation field instead. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [December 12, 2024, 4:09pm UTC](https://community.fibery.io/t/migrate-user-field-to-assignee-field/2663/7 "2024-12-12T16:09:37Z")
It’s now possible to choose whether notifications are enabled for the Assignee field (or any other ‘People’ field) > [@October 10, 2024 / takeout\_box Search in basic text/email/phone Fields, People Field, Space Setup 2.0, and more](https://community.fibery.io/t/october-10-2024-search-in-basic-text-email-phone-fields-people-field-space-setup-2-0-and-more/7512): > > Today’s release has many quality of life improvement and one major experimental change for creators. Search in basic text/email/phone Fields Special for @cire12, @Matt_Blais, @JoelH, @Eugene_Vabishchevich, @JMaynier, @uniquelau and so many other people. Now search supports all basic text fields, including Basic Text, Email, Phone and URL. It unfolds some new use cases: Search for people by Phone or Email, useful for Hiring and any other CRM process. Search for specific identifiers, like UUID…