User Migration fields available for bulk data import

Modified on Wed, 30 Mar 2022 at 07:49 PM

TABLE OF CONTENTS

Introduction
Available User Migration Fields
Further Support

Introduction

Some projects may have information about Users that are not captured by the main inventory source used by ManagementStudio. E.g. Users who are in a domain that is not been examined by the connector. In this case, project administrators can use an Excel source to manually import the information into ManagementStudio. This article describes the fields that can be used.

For further information on data imports, please refer to this article.

Available User Migration Fields

Field Names	Description	Required?
Migration Id	The Migration Id is a unique reference created by ManagementStudio when a user is imported into the ManagementStudio database. The use of this field will vary depending on the reason for the import: Creating a New User Migration: This field should be left blank when importing new users. ManagementStudio will allocate a Migration Id as part of the import process Updating an Existing User Migration: The Migration Id is required to ensure the details in the bulk data import are mapped to the correct user. Migration Ids can be exported from ManagementStudio and manually integrated with the bulk data import file using Excel: Switch to the User Migration (1) module in ManagementStudio Click the Select All button (2) from the toolbar to select all devices Click the Copy (3) dropdown arrow and select Export to Excel All (4)	Yes, when updating an existing user migration
First Name	This is the name of the user. For example John	Yes, when importing a new user migration
Last Name	This is the last name of the user. For example Blogg	Yes, when importing a new user migration
Sam Account	This is one of the attributes defined for security principles (users, groups, and computers) in Active Directory. For example Ta00001	Yes, when importing a new user migration
Domain	This is the domain the user migration belongs to.	Yes - If matching on SamAccount
Process Status	This is the internal Process status of the process the user migration is in.	No
Process	The User Migration process can be set during the import process. For example, if the user is already in Scheduling, this could be added to the import file to enable ManagementStudio to change the Process from the default value of 1. Identified to the current status of 5. Scheduling.	No
Sub Process	The User Migration sub-process can be set during the import process. This should be used in conjunction with the Process section above to ensure the correct sub-category is selected. For example, if 5. Scheduling is selected as the Process, the Sub-Process should be set to Scheduling Queue, or On Hold.	No
Start Date	This refers to the start date of the deployment unit, the user resides in.	No
Deployment Unit	This is the name of the deployment unit, the user is in.	No
DU Location	Deployment Unit location that the user belongs to
Migration Slot Start	The User migration start date and time.	No
Migration Slot End	The User migration end date and time.
Email	The email address of of the user. For example Jblogg@demo@managementstudio.com.	No
Phone No	The Phone number of the user.
Priority	The priority of the device can be recorded using the Priority field. Out of the box, an administrator can choose from Low, Medium and High. This field is often used to record the importance of a device.	No
Self Schedule Is Locked	This field is used to know where a self schedule link has been sent out to the user.	No
Employee Id	This is a unique numeric identification code for the user. For example 5487546	No
Assigned To	Which engineer have you got assigned to the user migration within the project.	No
Migration Type	This is the user migration type. For example, VIP.	No
Status	The status of the User Migration.	No

Further Support

If you require further support, please visit ManagementStudio's Service Desk to search the knowledge base or create a new support ticket.