TABLE OF CONTENTS

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 NamesDescriptionRequired?
Migration IdThe 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 NameThis is the name of the user. For example JohnYes, when importing a new user migration

Last NameThis is the last name of the user. For example BloggYes, when importing a new user migration

Sam AccountThis is one of the attributes defined for security principals (users, groups and computers) in Active Directory. For example Ta00001Yes, when importing a new user migration
DomainThis is the network the user migration belongs to.
No
Process StatusThis is the internal Process status of the process the user migration is in.
No
ProcessThe 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 DateThis refers to the start date of the deployment unit, the user resides in.No
Deployment UnitThis is the name of the deployment unit, the user is in.No
DU LocationDeployment Unit location that the user belongs to
Migration Slot StartThe User migration start date and time.
No
Migration Slot End
The User migration end date and time.

EmailThe email address of of the user. For example Jblogg@demo@managementstudio.com.No
Phone NoThe Phone number of the user.
PriorityThe priority of the device can be recorded using the Priority field.  Out of the box, an administrator can choose from LowMedium and High. This field is often used to record the importance of a device.
No
Self Schedule Is LockedThis field is used to know where a self schedule link has been sent out to the user.No
Employee IdThis is a unique numeric identification code for the user. For example  5487546No
Assigned ToWhich engineer have you got assigned to the user migration within the project.
No
Migration TypeThis is the user migration type. For example, VIP.
No
StatusThe status of the User Migration.No



Further Support

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