Home /Getting Started /Best Practices/ Pilot Testing

Pilot Review Guidelines

This document is for customers who have engaged Transend to perform yourmigration as a Managed Service.

Your data has been migrated into a test account in the new environment. As partof the pilot group, it is time for you to review the migrated data to confirmfidelity meets expectations. If it does not, please provide feedback! Your ITteam has provided you with the new login credentials.

The following is a guide of recommended issues to check during your review. Itis not a comprehensive list, but a suggested starting point. You know yourdata better than anyone else and should make sure everything looks right to you.

If you notice any problems, please provide as much information as possible forthe migration team to review, including the item’s subject, date, sender,meeting time, etc. Screenshots comparing the source and target systems arealso very helpful. Please send that information to your IT team members who aremanaging the migration project. The Transend migration team will review and worktowards a solution.

Mailbox data

E-Mail

  • Folders/Labels: All folders (Microsoft) or labels (Google) should appearwith the correct names and structure, including nested folders/labels.Messages should appear in the appropriate location. Folder permissions willneed be reshared in the target.
  • System Folders/Labels: Messages should appear in the correct location(i.e.- Inbox, Sent Mail, Drafts or a personal folder).
  • Message Headers: Data in the To, From, CC and Subject fields should lookright and show the correct date and time.
  • File Attachments: Attachments should be visible upon opening messages.They should have the proper file name and extension. Any attachments thatexceed the size limit for the new mail system were detached during migrationand stored in your personal drive (i.e. OneDrive (Microsoft) or My Drive(Google)) or can be supplied to you after the migration.
  • Address Translation: For those who may have migrated to or from a mailsystem with a different address format or you are changing e-mail addresses,notice that the e-mail addresses in message headers have been translated foruse in the new mail system.

Calendars

  • Dates: Meetings, events, appointments, etc. should appear on the correctdates.
  • Times: Calendar items should appear with the correct time and time zone.
  • Recurrence: All repeating / recurring meetings should repeat as expectedon the new calendar.
  • Message Headers, File Attachments & Address Translation: (see above).
  • Unaccepted Invitations: Note that unprocessed calendar invitations willnot be migrated, only accepted events are migrated.
  • Meeting Links: Meeting links in migrated events will still point to theoriginal location, confirm access to them from your test account(s) in thetarget.
  • Shared calendars: Calendar sharing permissions will need to be recreatedin the target.
  • Rooms: If a room was reserved for a meeting, the room name should appear.

Contacts / Address Book

  • People: Names and e-mail addresses should be correct.
  • Groups: Personal groups or distribution lists should have the right namesand all of the recipients included with accurate e-mail addresses.
  • Address Translation: (see above).
  • Shared contacts: Shared contact folder permissions will need to berecreated in the target.

Tasks / To Do List

  • Data: Items should have the subject and description information.
  • Dates: Check the start and end dates (if applicable).
  • Status: Look for the status, whether active or complete.

Files in Drives

Files in User Drives

If a User drive migration is included in the project scope, confirm your Userdrive (OneDrive (Microsoft) or My Drive (Google)) was migrated. Please note thatonly files you own were migrated.

  • Files: Files should be visible, and you should be able to open them.Confirm links and formulas in migrated files work as expected. Note thatnative Google file formats (i.e. Docs, Sheets, Slides, etc.) that are migratedto other platforms as aCopy operation{target=”_blank”} are converted to Microsoft-equivalent file types. Ifmigrating between Google Workspace tenants, and theMove operation{target=”_blank”} was performed, native Google file formats should bepreserved in the target.
  • Folders: Files should be in the correct folders. Folder structure,including nested folders, should look accurate.
  • Permissions: If file sharing permissions were included, check to see ifusers have the appropriate access to read or edit files and to open folders.
  • Ownership: Confirm all files that exist in your source drive and are ownedby you, were migrated. Any file that was shared to you, but you are not theowner, was not migrated into your target drive. Instead, it was migrated intothe file owner’s target drive (if they are in the migration scope).

Files in Shared Drives

If a Shared drive migration is included in the project scope, confirm files inthe specific SharePoint document library (Microsoft) or Shared Drive (Google)were migrated.

  • Files: File should be visible, and you should be able to open them.Confirm links and formulas in migrated files work as expected. Note thatnative Google file formats (i.e. Docs, Sheets, Slides, etc.) that are migratedto other platforms as aCopy operation{target=”_blank”} are converted to Microsoft-equivalent file types. Ifmigrating between Google Workspace tenants, and theMove operation{target=”_blank”} was performed, native Google file formats should bepreserved in the target.
  • Folders: Files should be in the correct folders. Folder structure,including nested folders, should look accurate.
  • Permissions: If file sharing permissions were included, check to see ifusers have the appropriate access to read or edit files and to open folders.In most cases, files/folders in Shared Drives have permissions set by drivemembership.

File migration expected behavior

Learn moreabout expected file migration behavior as it relates to sharing permissions.