MigrationWiz: Migrated and Not Migrated Items

Introduction

This articles covers a general overview of what items are and are not migrated for each environment when it is the source. However, every migration scenario is slightly different. MigrationWiz has different interactions with each supported environment based on connectors and permissions. As a result, the items migrated also differ by environment. 

As environment permissions and settings change frequently, and we are always adding new functionalities and options to MigrationWiz, we suggest checking back regularly to see if new items have been added.

This is not a comprehensive list. There are subsettings and some items which will also migrate which are not listed here. Scenarios which have specific item exceptions will have those exceptions noted in the migration guide. If you have questions or concerns about a specific item not listed here, Support can answer your questions and help you choose the best migration path.

MigrationWiz cannot migrate items that are not supported by the destination, although, in some cases, we can convert items from the Source to something that is accepted on the destination, e.g., Google Docs in Google Drive to Microsoft Word in OneDrive for Business.

Mailbox Items

Certain mailbox items are always migrated, regardless of source or destination. 

Always Migrated Never Migrated
Date/Time Items that do not match folder types, i.e. calendar responses within a mail folder. Important: If an item type is migrated into a folder of a different type at the destination, the item will not be visible.

Subject

Custom items that do not inherit from the core system types
Body InfoPath Forms
Importance Calendar permissions (Exception for Exchange sources outlined below)
Sensitivity Calendar notifications
Size Modified description text & modified attendee lists for exceptions to recurring meetings
Item Class User-defined/custom fields for Contact items
Exceptions to recurring meetings Acceptance status for meeting participants
Linked mailbox data (if accessible via EWS) Personal distribution lists ("Contact groups" in Office 365)
Pictures are included in the migration in migration scenarios with high fidelity, e.g., for Exchange to Microsoft 365, and Microsoft 365 to Microsoft 365. Mailbox rules and folder permission settings (these are only supported from Exchange Server 2010 SP1+ and later to Exchange Server 2010 SP1+ and later. The user prefix must match at both source and destination for permissions to migrate.)
  Bounce notifications
RSS feeds
Mailbox sharing settings (aliases; client settings; delegates e.g. SendAs and SendOnBehalf rights)
Personal Messaging Resource Management (MRM) Tags
Outlook Quick Steps
Client-side rule
Custom color coding for categories
Pictures that have been added within a Business Card, under Contacts.
Server-based and dynamic distribution lists
IPM and Report Mailbox Items
The following item types and message categories are exported from the source during migration.
  • IPM.Appointment
  • IPM.Contact
  • IPM.Note
  • IPM.Note.CommVault.Galaxy.Stub
  • IPM.Note.GroupMailbox.WelcomeEmail
  • IPM.Note.Microsoft.Conversation
  • IPM.Note.Microsoft.Conversation.Archive
  • IPM.Note.Microsoft.Conversation.Voice
  • IPM.Note.Microsoft.Missed
  • IPM.Note.Reminder.Event.2
  • IPM.Note.Rules.OofTemplate.Microsoft
  • IPM.Note.SMIME.MultipartSigned
  • IPM.Note.Receipt
  • IPM.Schedule.Inquiry
  • IPM.Schedule.Meeting.Notification.Forward
  • IPM.StickyNote
  • IPM.Task
  • REPORT.IPM.Note.CommVault.Galaxy.Stub.IPNNRN
  • REPORT.IPM.Note.Delayed.DR
  • REPORT.IPM.Note.DR
  • REPORT.IPM.Note.IPNNRN
  • REPORT.IPM.Note.IPNRN
  • REPORT.IPM.Note.NDR
  • REPORT.IPM.Note.Relayed.DR

The following item types and message categories are not exported from the source during migration.

  • IPM.AbchPerson
  • IPM.CalendarSharing.CalendarUpdate
  • IPM.CalendarSharing.EventDelete
  • IPM.CalendarSharing.EventUpdate
  • IPM.ControlFlowMessage
  • IPM.ControlFlowMessage.DocumentAnalyticsPropagation
  • IPM.ControlFlowMessage.GraphTransactionMessage
  • IPM.ControlFlowMessage.ModifyActionPropagation
  • IPM.ControlFlowMessage.SharePointItemMaintenance
  • IPM.ControlFlowMessage.SharePointItemRevokeAccess
  • IPM.ControlFlowMessage.SharePointItemSecurityUpdate
  • IPM.ControlFlowMessage.UserSubscriptionPropagation
  • IPM.DistList IPM.Document.Word.Document.12
  • IPM.File
  • IPM.File.Document
  • IPM.GroupMailbox.AddMemberRequest
  • IPM.GroupMailbox.JoinRequest
  • IPM.Outlook.Recall
  • IPM.Recall.Report.Failure
  • IPM.Recall.Report.Success
  • IPM.Schedule.Meeting.Canceled
  • IPM.Schedule.Meeting.Request
  • IPM.Schedule.Meeting.Request.AttendeeListReplication
  • IPM.Schedule.Meeting.Resp.Neg
  • IPM.Schedule.Meeting.Resp.Pos
  • IPM.Schedule.Meeting.Resp.Pos.SilentResponse
  • IPM.Schedule.Meeting.Resp.Tent
  • IPM.Sharing
  • IPM.TaskRequest
  • REPORT.IPM.Schedule.Meeting.Canceled.NDR
  • REPORT.IPM.Schedule.Meeting.Request.IPNRN
  • REPORT.IPM.Schedule.Meeting.Request.NDR
  • REPORT.IPM.Schedule.Meeting.Resp.Pos.IPNNRN
  • REPORT.REPORT.IPM.Note.IPNNRN.NDR
The destination may effect which items may be migrated. Not all item types will migrate to all destinations. For such special cases, read the migration guide for details on management.

Special cases in email migrations

Hidden folders

If a system folder exists on both the source and the destination, MigrationWiz will detect it and migrate items to that location. For example, Exchange stores attachments in a hidden system folder called 'Files'. If the destination also has this folded, MigrationWiz will automatically migrate the items. As these are hidden, it may appear they did not migrate.

If the content needs to migrate to a different folder, use folder mapping to specify the new destination folder. 

Encrypted Content

We migrate MIME content in an as-is state. S/MIME messages can be migrated and will remain encrypted at the destination. Viewing them on the destination requires the same certificate used to encrypt them, including its corresponding private key. 

Messages with Azure Information Protection will be migrated, but will not be viewable at the destination, as the source tenant policies will not be available on the destination. To migrate in a viewable format, decrypt these messages on the source and migrate the decrypted emails. To encrypt them at the destination (this is optional), simply recreate the security policies on the destination and then reapply the policies to the migrated messages. Our data retention and security policies can be reviewed at our BitTitan Data Security and Privacy Policy page.

Color Categories

The default colors will be maintained during migration. However, if additional color categories have been defined at the Source, other than those supported at the destination, they will not be migrated. Instead, they will be converted to the default calendar color at the destination. For example, Google supports more calendar colors than Microsoft 365. Any calendar colors on Google that are not any of the six (6) default colors on Microsoft 365 (blue, orange, green, purple, red, yellow) will be converted to the default color on Microsoft 365 (light red).

Calendar meeting links

Lync, Skype or Teams events will be migrated but will usually not work in the destination because the links are for the source environment. These events will need to be recreated at the destination. There are exceptions to this rule, but they are not consistent.

Microsoft 365

The items below are migrated when Microsoft 365 is the source environment.

Microsoft 365 Items

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Server-Side Rules
  • Folder Permissions
  • Post (when the destination is Exchange or Microsoft 365)
  • Calendar acceptance status emails
Not Migrated
  • Safe Sender/Block Lists

Groups

Not Migrated

  • Notebooks
  • For Groups documents: anything not in a document library (See SharePoint)

Microsoft 365 Archive

Migrated
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Server-Side Rules
  • Folder Permissions
  • BCC Recipients

OneDrive for Business

Permissions Migrations

When OneDrive for Business is configured as the source on a document migration, the only permissions migrated are for files and folders that are shared with specific people using Direct Access

Files or folders in OneDrive for Business can be shared in one of three ways:

  • With specific people
  • With anyone
  • With an organization

When files or folders are shared with anyone or with an organization, a link is generated for the items. These links are not accounted for by MigrationWiz and are not migrated to any destinations, including other OneDrive for Business accounts.

OneDrive for Business Items
Migrated
  • Folders
  • Shared Folders
  • Permissions
  • Code Files
  • Documents
  • Images
  • Forms
  • Executables
  • Videos
  • Audio Files
  • Original metadata and BitTitan migration metadata (author, editor, created time, modified time, name, filesize, type, MigrationWizId, MigrationWizPermissionId)
  • Document attributes (Created by (person) and (time)
  • Modified by (person) and (time))
  • Versions & Metadata migrations only: Creation Date

Not Migrated

  • Non-Versions & Metadata migrations:
    • Creation date (Creation date gets changed to the "date of migration" date) 
    • Version history
  • Links giving access
  • Shared permissions for files/folders with symbols in name

SharePoint

SharePoint Endpoint

The following items also pertain to Teams SharePoint migrations. However, only Document Libraries related to the Files tab will be migrated. 

SharePoint Items
Migrated
  • Document libraries
  • Permissions - individual folders and items only
  • Versioning
  • Metadata

Not Migrated

  • Site logos and customization
  • Task lists
  • Custom task
  • Newsfeed
  • Shared permissions for files/folders with symbols in name
  • Site Pages
  • Permissions at site or library level

SharePoint Online Endpoint

SharePoint migrations vary by endpoint combination and path followed. The following are an example of migrated items, but may not contain all items for your migration type. For specific migrated and not migrated items, see your migration guide. 

Migrated

  • Document libraries

    • Folders

    • Files

    • Permissions

    • Versions

    • Metadata (refer to the migration guide for more details)

Not Migrated

  • Site/Site collection

  • Site logos and customization

  • Task lists

  • Custom tasks

  • Newsfeed

  • Shared permissions for files/folders with symbols in the name

  • Site Pages
  • Any metadata referencing information from outside the document library (such as lists or other site-level data) is not migrated. For example: external data, managed metadata, lookup, retention policy tags/retention labels.

Teams

Important: MigrationWiz does not migrate private channels within Teams by default. If you have private channels you want to migrate, do so by adding the line TeamsMigratePrivateChannel=1 to the support section of the project's Advanced Options. Please note, users will not be added to the private channel on the destination. This needs to be done manually after the private channel migrates. Steps for this may be found in the Microsoft Teams to Microsoft Teams Migration Guide and FAQ

Due to Microsoft limitations, private channels are not migrated for GCC High Tenants. Private channel archives are never moved. 

To see what items are moved in Teams SharePoint migrations, see the SharePoint section. 

Teams Items

Migrated 

Teams: Migrated teams may not appear in the same order. User may drag and drop to reorder the lists.

  • Public
  • Private 
  • Organization-wide - these teams appear as public teams at the destination. Admin can change the privacy to organization-wide via the UI. 
  • Team picture
  • Team description

Channels:

  • Public
  • Private: via the Advanced Option listed above. This only migrates the conversations and documents. Adding users must be done via a PowerShell script.

Conversations:

  • 60 messages per team will be displayed in the destination team. Channel conversation history is downloadable as an HTML file in the Conversation History tab. 
  • Conversation structure
  • Root messages
  • Replies
  • Formatting - fonts, bullets, lists, colors
  • Quotes
  • Emojis
  • Inline images & stickers
  • Code snippets
  • Hyperlinks
  • GIFs
  • Mentions (as plain text)
  • Timestamps (in UTC)
  • Deleted message notifications - Messages will remain as deleted on the destination and show "Original message has been deleted."
  • Private conversations and files under the Chat tab
  • Private chats (Migrated via Mailbox migration flow and will only be visible in Outlook, not in Teams)

    • One-on-one chats

    • Group chats

    • Meeting chats

Files:

  • Files in public teams and channels
  • Files in private channels

Memberships:

  • Static memberships are migrated.

Team Settings

  • Team description
  • Team picture
  • Guest permissions - guest access on the source will be migrated if the guest exists at the destination and guest permissions are enabled prior to migration. This may be done via the Teams of Office 365 admin portal. 
  • Member permissions
    • Create and update channels
    • Create private channels
    • Delete and restore channels
    • Add and remove apps
    • Create, update, remove tabs
    • Create, update, remove connectors
    • Delete messages
    • Edit messages
    • Tag @team or @[team name] (this will send a notification to everyone on the team)
    • Tag @channel or @[channel name]. This will notify everyone who's shown the mentioned channel in their channel lists.
  • Guest permissions
    • Create and update channels
    • Delete channels
  • Other permissions
    • Enable Giphy
    • Enable stickers and memes
    • Allow memes to be uploaded
    • Filter inappropriate content

Channel settings (Public channels)

    • Channel moderation
    • New post permissions
    • Allow members to reply to channel messages
    • Allow bots to submit channel messages
    • Allow connectors to submit channel messages

OneNote: 

  • OneNote tabs

Planner

  • Tabs
  • Plans
    • Title
    • Owner
    • Settings (labels, descriptions, shared with)
  • Buckets
    • Title
    • Order: 1-1 mapping of order will not be present between delta-passes. See ‘Limitations’ section for more info.
    • Plan (which plan the bucket belongs to)
  • Tasks
    • Title
    • Assignees
    • Labels/Categories
    • Parent Bucket
    • Progress
    • Start Date
    • Due Date
  • Task Details
    • Notes
    • Show on Card
    • Checklist
    • Attachments*
    • Attachment preview
    • Description
    • Comments
    • Priority
  • Charts

*Only attachment links on the team's SharePoint site will be automatically remapped. 

  • Files that are uploaded directly at the task (files are eventually stored in the team's SharePoint site) will be automatically remapped.
  • SharePoint file links (links to files already in the team's SharePoint site) will be remapped.
  • No other links, including external links, will be remapped.

Not Migrated

Teams:

  • Team order - Teams may be manually reordered at destination via drag and drop. 
  • Tabs (Website tabs, Word, Excel, PowerPoint and PDF tabs, Document Library tabs, Wiki tabs, Microsoft Stream tabs, PowerBi, SharePoint page and list tabs, Custom tabs)

Conversations:

  • Tags
  • Likes & reactions
  • Links to files and meeting requests
  • Files previews
  • Hyperlink previews
  • Teams meeting invites in conversations
  • Calendar previews - Calendar is an attachment and the Graph API does not support sending messages with attachments. 
  • Teams recordings

Memberships:

  • Dynamic memberships - all memberships are migrated as static, user must recreate dynamic memberships.

Settings:

  • User-specific settings - favorites, profile pictures, status messages, saved messages
  • Allow members to upload custom apps
  • Team code
  • Channel settings: general/private. This is an API limitation. Default settings will be retained after migration. 
  • Global/organization-wide and custom Teams messaging policy is currently not supported. These policies are used to control which chat and channel messaging features are available to users in Microsoft Teams.

Other:

  • Wikis
  • Yammer
  • PowerBi reports
  • Other apps/tabs

Planner

  • Task Details (Microsoft Graph API limitation)
    • Created by
    • Created date
    • Last modified by
    • Last modified date
    • Completed by^
    • Completed timestamp
    • Assignee priority

Teams Private Chats

Migrated Not Migrated

Chat titles
(If there’s no title, participant names will be shown by default)

Reactions

Chat participants

Forms
GIFs Polly

Embedded images

Saved messages

File Attachments
(A completed OneDrive migration with necessary permissions is required for this to be successful)

Chats from deactivated users

Chats marked ‘Important’
(Email item will appear flagged as ‘Important’)

Chats on external tenants 
(i.e. You are the guest of that tenant)

Edited messages in a Chat

Links directly pasted into chats, including documents and images.

Praise (Icon/image not migrated)

 
Stickers  

Google Drive

Google Drive Items
Migrated
  • Folders
  • Folders you have shared
  • Permissions
  • G Suite native files (except Google Forms)
  • Code Files
  • Documents
  • Images
  • Executables
  • Videos
  • Audio Files
  • Templates (files that the template had been applied to are migrated)
  • Creation Date (Creation date gets changed to the "date of migration" date)
  • Scripts/Macros (Scripts are not converted to macros when going to documents)
  • Comments
  • File/Folder permissions
  • Items/folders in "Shared with Me”. These folders must be added to the user’s “My Drive” and Moderate Mode must be used in order to migrate these items/folders. 
  • Shortcuts (Migrated in Google Drive to Google Drive scenarios only.)
  • Google Shared Drives (also known as Team Drives)
    • Only when SharePoint Online is the Destination

Not Migrated

  • Personal / Free Google Drive is not supported
  • File/folder shortcuts

Google Vault (Source Only)

Migrated

  • Folders
  • Email

G Suite

Migrated - IMAP or G Suite (Gmail API) endpoints

G Suite Items
  • Inbox
  • Folders/Labels
  • Email
  • Muted Email (as regular email)
  • Contacts
  • Calendars (including links for Google Hangouts within calendar meetings)
  • Calendar Notifications 

Links for Google Hangouts are a new default feature added to Google Meeting. Microsoft 365 doesn't have the corresponding property to map. Therefore, when migrating to Microsoft 365, the links for Google Hangouts are added to the beginning of the meeting description body text on Microsoft 365.

Limitations

  • When migrating from G Suite as a source, contacts in Contact Groups (which look like subfolders of the Contacts folder) will migrate to the top level contacts folder on the destination. Folders will be created for each group but the contacts will not be sorted into those folders.
  • Calendars can have multiple Owners. An Owner is anyone with "Make changes and manage sharing" permissions, so shared calendars will be migrated to users with these permissions by default.

Not Migrated in Any Instance

  • Calendar Reminders
  • Appointments
  • Chat message attachments
  • Google Groups for Business (including forums and collaborative inboxes)

Not Migrated As Source

  • Calendar Attachments
  • Calendar Reminders
  • Tasks
  • Chats and chat history
  • Google Categories (i.e., the Google category flags: Social, Promotions, Updates, Forums)
  • Email attachments that are links to Google Drive
  • Some calendar colors

Note: All color category meta tags are transferred over, but Microsoft 365 does not have direct color mappings from Google G Suite, and so certain colors do not get mapped over, thus the colors are not displayed in Microsoft 365 for the calendar entries.

Not Migrated As Destination

  • Calendar Attachments
  • Exceptions of recurring appointments
  • Google Groups for Business (including forums and collaborative inboxes)

With Google API Endpoint at Source

With this endpoint, all items listed above migrate as before. However, utilizing the API endpoint enables migration of the following items as well. The following items are not migrated via the IMAP endpoint. 

Migrated

  • Google Categories (Category flags, i.e. Social, Promotions, Updates, Forums)
  • Snoozed and Scheduled emails - these are migrated like regular emails to custom destination labels. Their properties are not migrated.
  • Chat history - Chat messages are migrated to the destination as an email message (without subject) by using the support option MigrateChats=1

Google Shared Drive

Google Shared Drive Items

Migrated

  • Files
  • Folders
  • Permissions
  • Versions (up to 25)
  • Metadata
    • File/Folder name
    • Modified (based on the modified date of latest version migrated)
    • Modified by
    • Created (based on the created date of latest version migrated)
    • Description is migrated to ‘Title' column at destination. Migrated value is limited to the existing character limit of the 'Title’ field.
    • ‘Creator’ metadata is migrated but in some cases this value may not be accurate. This is a current limitation without a workaround.
  • Shortcuts are migrated as a .URL file to the destination document library - if the target file exists within same shared drive. Shortcuts are to be migrated as a subsequent migration step, after migrating all relevant documents & permissions.

Not Migrated

  • For some Google proprietary format files (e.g. Docs, Sheets, Slides), Google allows you provide a custom name for a version of the file. Such version names are not migrated.

GSD_1.png

  • Minor revisions available for Google proprietary format files are not migrated.
  • Google Sites, Maps, and Apps Script files are not supported.
  • Embedded video/hyperlinks in Google docs, sheets, or slides may not be migrated accurately when these Google proprietary files are converted to Microsoft 365 format.
  • .TMP files are not supported.
  • Shortcuts will not be migrated if target file doesn’t exist at the destination.
  • Versions are not supported for Google forms.
  • Versions of Google drawing files (converted to images) are not migrated accurately. All migrated versions may display the same content as that of latest version. This is due to a current API limitation. without a current workaround.
  • Migration of files greater than 15 GB is not currently support.

Exchange

Migrated items vary by version.

If Exchange is the Source, and an account exists in the destination that matches the UPN prefix of an account with Calendar Permissions in the Source prior to submitting a migration, Calendar Permissions will be migrated, except for Resource Calendars. Resource Calendars permissions are not migrated.

If Exchange is the Source, and an account does not exist in the destination that matches the UPN prefix of an account with Calendar Permissions in the Source prior to submitting a migration, Calendar Permissions will not be migrated.

Exchange Items
Not Migrated in Any Instance
  • Inactive mailboxes

Exchange Server 2003 (Source Only)

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Post (when the destination is Exchange or Microsoft 365)

Exchange Server 2007+

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • BCC Recipients
  • Post (when the destination is Exchange or Microsoft 365)

Exchange Server 2010 SP1+

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Post (when the destination is Exchange or Microsoft 365)
  • Server-Side Rules
  • Folder Permissions

Not Migrated in any Exchange Instance

  • Email templates
  • Email flags (if the destination is G Suite)
  • Safe Sender/Block Lists
  • Mail Settings
  • Standalone documents stored in Mailbox Folders or Public Folders (Example: IPM.Document item types)
  • System Public Folders
  • StickyNote folders

Not migrated in Exchange 2003: Public Folders, BCC recipients on email items or optional attendees of calendar entries (Microsoft Exchange Web DAV API does not return this information for items)

Not Migrated in Exchange 2007: Public Folder Permissions

Exchange Public Folders

Note: Public Folders can only be migrated to other public folders or shared mailboxes. We do not migrate Public Folders to individual user mailboxes or Microsoft 365 Group mailboxes or vice versa.

Exchange Public Folders Items

Exchange 2007

Migrated

  • Public Folders
  • Subfolders

Exchange 2010 SP1+ & Microsoft 365

Migrated

  • Public Folders
  • Subfolders
  • User Permissions
  • Mail-Enabled Security Group Permissions (Default and Anonymous User Permissions are not supported)

Exchange Archive

Exchange Server 2003 and Exchange Server 2007+ archives are not supported

Exchange Archive Items

Exchange Server 2010 SP1+

Migrated

  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Server-Side Rules
  • Folder Permissions
  • BCC Recipients

Dropbox

Note: When Dropbox is configured as the Source, shared folders and items are migrated to the destination but their shared permissions are not. Likewise, when Dropbox is configured as the destination, shared folders and items are migrated from the Source but their shared permissions are not.

Dropbox Items

Migrated

  • Folders
  • Shared Folders
  • Code Files
  • Documents
  • Images
  • Forms
  • Executables
  • Videos
  • Audio Files

Not Migrated

  • Dropbox shared folder permissions
  • Dropbox Notes
  • Dropbox Bookmarks
  • Dropbox Tags
  • Dropbox Teams
  • Version history
  • .paper files

File Server

(Source Only)

File Server Items

Migrated

  • Folder structure
  • Files
  • Permissions

GroupWise 7+ 

Groupwise 7+ Items

Migrated

If the destination is Exchange, or Office 365:

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks

If the destination is not Exchange or Office 365:

  • Inbox
  • Folders
  • Email

Not Migrated

  • Shared folders
  • Contact and Calendar items to G Suite destination(s)
  • Multi-user folders
  • Frequent contacts
  • Suggested contacts

IMAP & POP

IMAP & POP Items

Migrated

  • Inbox
  • Folders
  • Email

POP

POP (Source Only) Items

Migrated

  • Inbox
  • Email

Lotus Notes 6.5+ - 9.0.1 

Lotus Notes Items

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks

Not Migrated

  • Lotus Distribution Groups
  • All Documents view
  • Lotus Mail Groups
  • Journals
  • Items in the Trash folder
  • Resources field inside a Calendar event
  • Task alarms & reminders

PST Archives

PST Items

PST Files from your own Azure storage.

Migrated

  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes

Not migrated

  • Follow Up flags

PST BitTitan Storage 

PST Files uploaded to BitTitan Storage using the UploaderWiz tool.

Migrated

  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes

Amazon Storage

Items with the Storage Class "Glacier" - Items archived to cold storage by Amazon's retention policy - are not migrated

Zimbra 6+

Zimbra Items

Migrated

  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks

Not Migrated

  • Zimbra Tags
Was this article helpful?
2 out of 2 found this helpful