Deployment Unit fields available for bulk data import

Modified on Tue, 20 Jan at 10:26 AM

TABLE OF CONTENTS

Importing Deployment Unit Data from Excel
- Target Module Mapping
Available Deployment Unit Fields
Further Support

Importing Deployment Unit Data from Excel

Project administrators can import deployment unit information from a spreadsheet into ManagementStudio using the Excel data import feature. This article outlines the available fields for deployment unit imports and guidance for preparing your data.

For detailed instructions on importing data, refer to the Data Importer guide.

Note: When importing new deployment units, the target module must be specified in your spreadsheet. You can use either the ModuleId or the module name in the relevant column.

Target Module Mapping

ModuleId	Module Name
1	Applications
2	UserMigrations
3	Devices
4	Mailboxes
5	BespokeModule

Example: Use either 1 or Applications in the Target Module column.

Example spreadsheet of deployment units to import.

A sample spreadsheet containing new deployment units.

Linking spreadsheet fields to ManagementStudio fields.

Mapping spreadsheet columns to ManagementStudio fields during import.

Available Deployment Unit Fields

The following fields are available when importing deployment unit data:

Field Name	Description	Required?
Target Module	The target module for the deployment unit. Options: Applications, User Migrations, Devices, Mailboxes, BespokeModule. Can also use module ID.	Yes (when importing new deployment units)
Deploy Unit Id	Unique identifier for an existing deployment unit, assigned by ManagementStudio. Use this when updating records.	Yes (when updating existing deployment units)
Deployment Unit	Name of the deployment unit (e.g. "London Office").	Yes (when importing new deployment units)
Location	Location of the deployment unit (e.g. "London").	Yes (when importing new deployment units)
Start Date	Start date for the deployment unit.	No
All Day	Designate whether the deployment activity spans the entire day.	No
Process	Set the process stage for the deployment unit (e.g. "5. Migrating"). If not set, will default to "1. Identified".	No
Sub Process	Set a sub-category within the process stage, used in conjunction with `Process` (e.g. "Migrating Queue", "Migrating in Progress", or "On Hold" when process is "5. Migrating").	No
Process Status	Internal process status reflecting the deployment unit's current state.	No
Is Base Line Locked	Indicates if the baseline deployment plan is locked, preventing changes.	No
Is Signed Off	Whether the deployment unit has been signed off.	No
Priority	Priority level (e.g. Low, Medium, High), as defined by the project.	No
Created By	User who created the deployment unit.	No
Archived	Whether the deployment unit is archived. Archived units are moved out of the main view.	No
Locked	Indicates whether the deployment unit is locked. Locked records cannot be updated until unlocked.	No
Delegate 2	Specify users to delegate the deployment unit to.	No
Description	Description or additional details about the deployment unit (e.g. "Manchester Regional Office").	No

Note: All built-in custom fields are available for import if enabled under
Administration → Deployment Units → Grid Config.

Further Support

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