TABLE OF CONTENTS

• Introduction
• Available User Migration Fields
• Further Support

Introduction

In some projects, information about users may not be captured by the main inventory source used in ManagementStudio. For example, users within an unmanaged domain may not be identified by the connector. In such cases, project administrators can manually import user information into ManagementStudio using an Excel source. This article describes the available fields for user migration imports.

For more information on data import processes, refer to the Data Importer article.

Available User Migration Fields

The table below lists the fields that can be used when importing or updating user migration records in ManagementStudio.

Field Name	Description	Required?
MigrationId	A unique reference generated by ManagementStudio for each user migration. The usage of this field depends on the import scenario: Creating a New User Migration: Leave this field blank when importing new users. ManagementStudio will automatically assign a Migration Id. Updating an Existing User Migration: The Migration Id is required to map the data import to the correct user. To obtain Migration Ids: 1. Navigate to the User Migration module. 2. Select all required records using the Select All button on the toolbar. 3. Click the Copy dropdown and choose Export to Excel All.	Yes, when updating an existing user migration
FirstName	The given name of the user. For example, John.	Yes, when importing a new user migration
LastName	The surname of the user. For example, Blogg.	Yes, when importing a new user migration
SamAccount	The user’s sAMAccountName attribute from Active Directory. For example, Ta00001.	Yes, when importing a new user migration
Domain	The domain associated with the user migration.	Yes, if matching on Sam Account
ProcessStatus	The internal process status for the user migration.	No
Process	The user migration process stage. Can be set during import, for example, 5. Scheduling if the user is already in this process. If omitted, ManagementStudio sets the value to the default (1. Identified).	No
SubProcess	The user migration sub-process. Use in conjunction with the Process field to specify the appropriate category, e.g. if 5. Scheduling is set for Process, set Sub Process to Scheduling Queue or On Hold.	No
StartDate	The start date of the deployment unit the user belongs to.	No
DeploymentUnit	The name of the deployment unit associated with the user.	No
DULocation	The location of the deployment unit.	No
MigrationSlotStart	The start date and time for the user migration.	No
MigrationSlotEnd	The end date and time for the user migration.	No
Email	The email address of the user. For example, Jblogg@demo.managementstudio.com.	No
PhoneNo	The user’s phone number.	No
Priority	The priority assigned to the migration. Default values are Low, Medium, and High.	No
SelfScheduleIsLocked	Indicates whether a self-scheduling link has been sent to the user.	No
EmployeeId	A unique numeric identifier for the user, e.g. 5487546.	No
AssignedTo	The assigned engineer for the user migration.	No
MigrationType	Specifies the user migration type (e.g., VIP).	No
Status	The status of the user migration.	No

Further Support

For additional assistance, visit the ManagementStudio Service Desk to search the knowledge base or to raise a new support ticket.