1. Support Latam
  2. BitTitan
  3. MigrationWiz

Menu

    This article explains which items are and are not migrated by MigrationWiz in common migration scenarios. It is important to note that environments are always changing, and updates may change which items are migrated.

    This article is organized by Source environment: for example, if you are migrating from G Suite, use the side menu to navigate to the G Suite section. There are a few items which depend on Destination however, so we also suggest navigating to the Destination section before you begin your migration.

    Note that many email and document migrations will migrate the same items regardless of Source. If you are performing an email or document migration, first navigate to the general section heading for an overview of migrated items before viewing your Source listing.

    Hybrid (Coming Soon)
    It is important to note that for the purposes of this article, Hybrid is a migration type. This section is not a list of items migrated from a Hybrid Exchange environment using a migration project type other than "Hybrid Migration". For specific items migrated, navigate to Exchange 2007+. However, the following information is important when planning your Hybrid migration.

    Migrated
    Use my source mailbox settings (if this is checked, options following are grayed out).
    Set mailbox quota (enter variable In GB numeric value only) Default 50GB
    IMAP (toggle on/off)
    POP (toggle on/off)
    Outlook Web Access (toggle on/off)
    ActiveSync devices (toggle on/off)
    Retention policy - litigation hold (toggle on/off)
    Not Migrated
    Inherited (non-explicit) mailbox permissions and permissions granted to objects that aren't mail enabled in Exchange Online are not migrated. You should ensure all permissions are explicitly granted and all objects are mail enabled prior to migration. Therefore, you have to plan for configuring these permissions in Office 365 if applicable for your organization. In the case of Send As permissions, if the user and the resource attempting to be sent as aren't moved at the same time, you'll need to explicitly add the Send As permission in Exchange Online, using the Add-RecipientPermission cmdlet.

    Exchange hybrid deployments support the use of the Full Access and Send on Behalf Of permissions between mailboxes located in an on-premises Exchange organization and mailboxes located in Office 365. Additional steps are required for Send As permissions. Also, some additional configuration may be required to support cross-premises mailbox permissions depending on the version of Exchange installed in your on-premises organization. See https://docs.microsoft.com/en-us/exchange/exchange-hybrid#exchange-hybrid-deployment-considerations for more information.

    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 vice versa.

    Exchange 2003 & 2007
    Migrated
    Public Folders; Subfolders

    Exchange 2010 SP1+ & Office 365
    Migrated
    Public Folders; Subfolders; User Permissions

    Mailbox
    This is not a comprehensive list. There are subsettings and some items which will also migrate which are not listed here. 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.

    Migrated General Email Properties
    Date/Time; Subject; Body; Importance; Sensitivity; Size; Item Class; Exceptions to recurring meetings; Color categories for calendars.

    Note: 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 Office 365. Any calendar colors on Google that are not any of the six (6) default colors on Office 365 (blue, orange, green, purple, red, yellow) will be converted to the default color on Office 365 (light red).

    Never Migrated
    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.); Custom items that do not inherit from the core system types; InfoPath Forms; calendar permissions; calendar notifications; modified description text & modified attendee lists for exceptions to recurring meetings; User-defined/custom fields for Contact items; Acceptance status for meeting participants; Personal distribution lists ("Contact groups" in Office 365); Server-based and dynamic distribution lists; Bounce notifications; RSS feeds, Mailbox sharing settings (aliases; delegates; client settings); Mailbox rules and folder permission settings (these are only supported from Exchange Server 2010 SP1+ and later to Exchange Server 2010 SP1+ and later) Personal Messaging Resource Management (MRM) Tags; Outlook Quick Steps; Client-side rules; Linked mailboxes; Color-coding for categories; Pictures that have been added within a Business Card, under Contacts.

    Notes

    Pictures are included in the migration for the migration scenarios with high fidelity, e.g., for Exchange to Office 365, and Office 365 to Office 365.
    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
    Exchange Server 2003 (Source Only)
    Migrated
    Inbox; Folders; Email; Contacts; Calendars; Tasks; Journals; Notes; Post (when the destination is Exchange or Office 365)

    Exchange Server 2007+
    Migrated
    Inbox; Folders; Email; Contacts; Calendars; Tasks; Journals; Notes; BCC Recipients; Post (when the destination is Exchange or Office 365)

    Exchange Server 2010 SP1+
    Migrated
    Inbox; Folders; Email; Contacts; Calendars; Tasks; Journals; Notes; Post (when the destination is Exchange or Office 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 Public Folders; System Public Folders; IPF; StickyNote folders

    Exchange 2003: Public Folders

    Exchange 2007: Public Folder Permissions

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

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

    Not Migrated
    Calendar Reminders, Appointments

    As Source

    Note: We can only migrate items that are visible through IMAP.

    Calendar Attachments (25MB and smaller); Calendar Reminders; Tasks; Chats and chat history; Google Groups for Business (including forums and collaborative inboxes); 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 Office 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 Office 365 for the calendar entries.

    As Destination

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

    Google Drive
    Notes:

    Google Shared Drives (also known as Team Drives) are not supported
    Personal Google Drive is not supported
    Free Google Drive accounts are not supported
    Migrated
    Forms; 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); Document History; Comments; File/Folder permissions; Items/folders in "Shared with Me”

    Note: “Shared with Me” folders must be added to the users “My Drive” and Moderate Mode must be used in order to migrate Items/folders in “Shared with Me”. See the https://help.bittitan.com/hc/en-us/articles/115008259248 article for more assistance.

    Office 365
    Migrated
    Inbox; Folders; Email; Contacts; Calendars; Tasks; Journals; Notes; Server-Side Rules; Folder Permissions; Post (when the destination is Exchange or Office 365); Calendar acceptance status emails

    Not Migrated
    Safe Sender/Block Lists

    Groups
    Not Migrated
    Notebooks

    Planner
    Not Migrated
    Data

    Other Environments
    GroupWise 7+ (Source Only)
    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
    Migrated
    Inbox; Folders; Email

    Lotus Notes 6.5+ - 9.0.1 (Source Only)
    Migrated
    Inbox; Folders; Email; Contacts; Calendars; Tasks

    Not Migrated
    Lotus Distribution Groups; Lotus Mail Groups; Journals; Items in the Trash folder

    Open Xchange
    Migrated
    Email; Contacts; Calendars

    POP (Source Only)
    Migrated
    Inbox; Email

    Zimbra 6+ (Source Only)
    Migrated
    Inbox; Folders; Email; Contacts; Calendars; Tasks

    Not Migrated
    Zimbra Tags

    Document
    This is not an exhaustive list. It includes only the typical Destinations. The complete list of supported Destinations can be seen under Destination settings when creating the project.

    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.

    MigrationWiz is a content migration solution. Our service does not perform any of the following:

    Migration of client-side settings.
    Provisioning of accounts.
    Active Directory-related object creations or synchronization.
    .NK2 file migration.
    Propagation of updates, deletes, or moves of items previously migrated from prior migration. passes,​ because we do not have “live” monitoring of changes (as with a sync agent), and we cannot handle scenarios such as conflict resolution without user interaction.
    Migration of version history for any system.
    Google Drive
    Migrated
    Folders; Shared Folders in your Drive; Permissions; G Suite native files (except Google Forms); Code Files; Documents; Images; Executables; Videos; Audio Files

    Box
    Note: Permissions are migrated from the Source Box environment.

    Migrated
    Folders; Shared Folders; Code Files; Documents; Images; Forms; Executables; Videos; Audio Files

    Not Migrated
    Box Notes; Box Bookmarks; Box Tags; Version history; Shared Links

    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.

    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; Version history

    File Server (Source Only)
    Migrated
    Folder structure; Files; Permissions

    OneDrive for Business
    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.

    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.

    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))

    Not Migrated
    Creation date (Creation date gets changed to the "date of migration" date); Document history; Version history; Links giving access

    SharePoint Online
    Migrated
    Document libraries; Permissions

    Not Migrated
    Site logos and customization; Task lists; Custom task; Newsfeed; Versioning; Metadata

    Archive Migrations
    Exchange
    Exchange Server 2003+ (Source Only)
    Exchange Server 2003 archives are not supported

    Exchange Server 2007+
    Exchange Server 2007 archives are not supported

    Exchange Server 2010 SP1+
    Migrated
    Folders; Email; Contacts; Calendars; Tasks; Journals; Notes; Server-Side Rules; Folder Permissions; BCC Recipients

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

    Google Vault (Source Only)
    Migrated
    Folders; Email

    G Suite (Destination Only)
    Migrated
    Folders; Email

    IMAP (Destination Only)
    Migrated
    Folders; Email

    PST (Source Only)
    PST Files from your own Azure storage.

    Migrated
    Folders; Email; Contacts; Calendars; Tasks; Journals; Notes

    PST BitTitan Storage (Source Only)
    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

    Collaboration Migrations
    All Team types
    Public
    Private
    Organization-wide
    Channels: All channels are migrated

    Conversations: Structure;Format; Root messages; Replies; Fonts; Bullets; Lists; Colors; Quotes; Emojis; Inline images and stickers; Code snippets; Hyperlinks; GIFs; Deleted message notifications; Mentions (as plain text to prevent duplicate notification after migration); Timestamps (in UTC)

    Files (except files in private chats): All files outside of private chats are migrated.

    Memberships: All memberships are migrated.

    Not Migrated
    Private chats; Private group chats; Files from private channels; Likes/Reactions; Links to files and meeting requests in conversation threads; File previews; Hyperlink previews; Calendar previews; User-specific settings (Favorites, Profile pictures, Status messages, and saved messages); Dynamic groups (the groups will be migrated, however, they will be migrated as static groups); Tabs (for example: Planner, Yammer, etc. No custom tabs will be migrated, either); Customized Team settings (these include team picture, member permissions, guest permissions, mentions, etc. New Teams will be created with the Default settings); Team list order (after migration, Teams will not appear on the Destination in the same order as on the Source. Users can drag and drop to reorder the list of teams); Wikis

    Powered by Zendesk