Difference between revisions of "MTK CSV Files"

Latest revision as of 16:22, 26 June 2017

[edit] CSV Files

A note on CSV files: The Migration ToolKit is just that a bunch of tools that let you connect two similar but different email systems together. Something like the old manual telephone switchboards of the early days of telephony. The CSV file contains the data points you need to connect one system to the other. In other words, it let's you run the patch cords from the old system to the new. Once the connections are set the data will flow. It is just that getting the connections placed first are the most challenging parts.

[edit] CSV data headers

dn = GW/eDir Distinguished Name

organization = GW/eDir Organization

organizationUnits = GW/eDir Organizational Units

cn = GW/eDir Common Name

domain = GW/eDir Domain

postOffice = GW/eDir Post Office

firstName = GW/eDir First Name

lastName = GW/eDir Last Name

displayName = GW/eDir Display Name

uuid = AD/EX Universal Unique Identifier

phones = GW/eDir Phone Numbers

email = GW/eDir Email

department = GW/eDir Department

destinationEmail = AD/EX Destination Email

upnLogon = AD/EX User Principal Name Logon

samAccountNameLogon = AD/EX User Logon Name (pre-Windows 2000)

gwUserID = GW/eDir GroupWise User ID

delegateRuleId = AD/EX Delegate Rule ID

destinationContext = AD/EX Destination Context

destinationDN = AD/EX Destination Distinguished Name

mailboxDB = AD/EX Mailbox Database, specify if not default

nicknames = GW/eDir Nicknames

office365License = O365 License

disabledPlans = O365 Disabled Plans

usageLocation = O365 Usage Location, two character country code

password = AD/EX/O365 Password

destinationGUID = AD/EX Destination Global Unique Identifier, created by AD

language = AD/EXLanguage

faxNumber = GW/eDir FAX Number

ngwExternalNetId = GW/eDir External Entity

type = GW/eDir Type, User or Resource

resourceOwner = GW/eDir Resource Owner

[edit] CSV Editor

Having a good CSV editor is important. LibreOffice is good as it will edit CSV files directly.

We have had many cases where companies change domains or email address policies that they will do at the same time as they migrate email systems. This makes things more complex but is completely doable.

For example, you might have user zk@gwava.com in GroupWise who has been here since the beginning, but as part of the migration you need to enforce an email addressing policy to match current standards: Zefram.Komtrain@microfocus.com.

ProTip: Altering a few destination emails manually in the CSV file is not a big deal but if all of the users need changing then you need to do something else. You can copy the first name and last name fields to a new spreadsheet. Create a domain column and enter the new domain as fill down. Create a formula in the next column where you combine them.

For example, if column A contains First Name, column B contains Last Name and column C contains the domain name, you can use the spreadsheet function Concatenate to combine them into a single field.

 =CONCATENATE(A1;".";B1;"@";C1)

Once the destination email is how you want it, copy the column and paste the values and not the formula.

Return to Retain_Migration_Toolkit