We’re Here to Help!!

Find A Solution, Learn Best Practices & Get Support 24x7

Migrating the User Object


The process of migration of User object has some specifics, which are discussed here. When migrating user records the following considerations should be taken into account:



The User object has a unique value across all orgs for field – Username -  which must be generated automatically by Dataplier if new user records are created.


Usually the number of users on each org is limited, and this limits the number of records that can be migrated


Note that users cannot be deleted (although they can be deactivated), so it’s necessary to be careful when migrating User records.


Below is a detailed description of how to use Dataplier to migrate the records of User object. During migration the following window could appear, allowing you to set some options controlling the process of migration: 



Dataplier performs the mapping of users from one org to another by Name field. If it meets the situation when these sets of users are different, then it proposes how to generate the references to user records absent on the other org.


Option1. Use mapping – in this case Dataplier will use a mapping of users and replace the references on the other org with mapped lookups. For unassociated users all lookups on them will be replaced with lookup to user who performs the deployment.

Option2. Deploy new users – in this case Dataplier will create new user records. It’s necessary to choose the profile which will be associated with new users and the role. The Username field in these records should be unique across all orgs, and Dataplier uses the following algorithm to generate it:

Extract FirstName and SecondName from existing user records and concatenate them with any suffix string provided by user (must be entered into appropriate input field).



Source  org

Generated values in destination  org

Suffix provided by user:


John Smith

John Smith







By default, Dataplier always performs an Upsert using FullName field as the key for the “User” object (this condition has been added to eliminate possible errors and avoid explicit duplicate user records).




Print Friendly and PDF
Was this article helpful?
0 out of 0 found this helpful