Chat now with support
Chat with Support

Metalogix Content Matrix 9.2 - Release Notes

All Editions



Issue ID

·After installing all editions and running cmdlets related to User Mappings, the mappings are performed in the wrong edition.

This issue occurs because after all editions are installed, the path to the snap-ins of the last edition installed are registered in registry.

WORKAROUND: Change the path for the snap-ins to the edition that you are currently using in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft


·After upgrading to version 9.0, migrations from Blogs and Wikis or File Share Edition using PowerShell fail.

NOTE:  Blogs and Wikis and File Share Editions are no longer available as of version 9.0.  If you want to continue using an older version (including to perform migrations using PowerShell), uninstall these Consoles from the current server then re-install them on a different server.


Automatic Updates


Issue ID

·The error 407 Proxy Authentication required is logged when you try to download the latest version of Content Matrix from within the Console if:

§Content Matrix is using a proxy that has been imported from Internet Explorer


§the proxy server is configured as "Permit Only" with Username/Password authentication.

WORKAROUND:  Run the "Proxy Login Automator" script as described in the '407 Proxy Authentication' article located in the Metalogix Content Matrix section of the Quest Support Knowledge Base.  


License Key


Issue ID

·When a license key exceeds its limit, valid information about the license no longer displays in the About box.


Multi-factor Authentication


Issue ID

If a non-MFA (Mult-factor Authentication) user who has created SharePoint  Online site-level connections is converted to an MFA user, when the connections are refreshed via the Content Matrix Console, they remain active instead of being disconnected.

WORKAROUND:  Relaunch Content Matrix and re-run the migration.


SharePoint Edition

Migration to SharePoint Online


Issue ID

·403 error is thrown when creating Site Collection at tenant-level

WORKAROUND:  Keep the tenant open in Internet Explorer, restart the Console, and perform migration.  


·When performing a migration using a SharePoint 2013 database connection to a SharePoint Online tenant, some list/library content may become encrypted/corrupted at the target.

WORKAROUND:  Use a MEWS source connection.


·Large document (50MB or greater) fail to migrate to SharePoint Online only when the Content Matrix Console is installed on client (non-SharePoint) machine using a SharePoint 2013 or 2016 database connection.


·While migrating a site from SharePoint 2016 (using an OM or CSOM connection) to SharePoint Online, an Index was out of range error is logged.


·File migration fails when migration is done via the Import Pipeline  and file is already present at destination when copy list or copy folder is executed.

WORKAROUND:  Delete existing items on target, and re-migrate. Or, if the existing items have not been changed, the error can be disregarded because the rest of the migration will complete successfully.


·When migrating items with versions from an Issue Tracking list the version numbers are not preserved. While all of the versions and metadata are migrated, the version numbers are slightly off.

NOTE:  This is due to a current bug in the Import Pipeline.


·Custom Content Types on "Folders" do not get applied on the target, when migrating to SharePoint Online (SPO) using the Import Pipeline. By default all folders get tagged with the "Folder" Content Type instead.


·The error 407 Proxy Authentication required is logged when you try to migrate using the Import Pipeline if:

§Content Matrix is using a proxy that has been imported from Internet Explorer


§the proxy server is configured as "Permit Only" with Username/Password authentication.

WORKAROUND:  Run the "Proxy Login Automator" script as described in the '407 Proxy Authentication' article located in the Metalogix Content Matrix section of the Quest Support Knowledge Base.  


·Content Matrix is showing incorrect logs if a user is trying to migrate a list which contains corrupted attachments to a SPO site using the Import Pipeline.


·When migrating a list with checked out items using the Import Pipeline, a fatal error occurs for those items because Content Matrix is attempting to migrate them as the latest version.


Migrations from SharePoint Online to SharePoint On Premises


Issue ID

·Migrations from SharePoint Online using a CSOM connection to SharePoint On Premises failing with "Unable to obtain SharePoint Online authentication cookie" message.


Locked Site Collections


Issue ID

·A locked source site collection won’t allow a migration to complete when set to “No Access.”

NOTE:  This is by design as SharePoint will not allow access to the content.


Community Site Migration


Issue ID

·The migrating account always gets added to a Community Site Members list at SPO target when a CSOM connection is used.


·Members of a Community Site Member list are not copied on SPO when a CSOM connection is used.


·Map missing user Option is not updating metadata for Member list of Community Site when mapping multiple source users to a single target on Community Sites.

NOTE:  Should multiple source users be mapped to a single target user when migrating a Community Site, the metadata values of that user in the target Member List will not concatenate the total metadata values from the source. This will only reflect the user with the most recent migration.


·Metadata will always get copied with Member List with Community Sites.  

NOTE:  When migrating ONLY the members list from a source Community Site to the target, the metadata for the list is set (even if the relevant Discussion list is not migrated). This is a narrow scenario. The workaround is to migrate the Member List as part of a larger migration.

WORKAROUND:  migrate the Member List as part of a larger migration.


·Gifted badge values are not getting migrated properly in a community site Member list.


·Best Reply inside discussion list is not migrated on target when migrating from SharePoint 2016 Community Sites.  

WORKAROUND:  Migrate the Member List as part of a larger migration.


·Duplicate replies are created inside discussion list in case of incremental migration of Community Sites.

WORKAROUND:  Delete the Discussion List from the target and re-migrate.


·When using the Import Pipeline, the 'PostedBy’ column value is not preserved when target is a Community Site.  

WORKAROUND:  Migrate using CSOM only.


Blog Site Migration


Issue ID

·Warning Mapped template '301' to 'CustomList' as '301' does not exist on the target is logged when migrating blog sites with "Clear Default features on Target" option when migrating to SharePoint Online.  

WORKAROUND: Do not change the default selected option which is "Preserve default Features on target"


·Closed web parts are migrated as open on target wiki page in Blog Site (and in some cases internal contents are changed).


Publishing Portal Migration


Issue ID

·Unable to create or paste a Public Publishing Portal template (EHS#2) as Site when migrating to SharePoint Online.

NOTE:  This template is unavailable in SharePoint Online.


MySite Migration


Issue ID

·Copying MySite Social Collaboration "Note Board" Web Part is not supported in SharePoint 2013 to SharePoint 2013 migrations.


·“Access is denied” error observed during the MySite Migration from SharePoint on premises to SharePoint Online when trying to update a read only content type.

NOTE: During the first 24 hours after user creation, this error will not occur. However, after that time, admins should enable the 'Allow Users to run Custom Scripts' setting in SharePoint Admin Settings.


·Theme setting are not migrated to the Tenant with ‘Paste as Site Collection’ option.


·When migrating MySites from a 2013 or 2016 source to a 2016 or 2019 target, the error Server was unable to process request. ---> The system cannot find the file specified is logged for web parts of default lists/libraries.


SharePoint Permissions Migration


Issue ID

·Exception 'Value does not fall within the expected range' when replacing a single Site Collection Administrator with another during migration.

WORKAROUND:  Add a new Site Collection Administrator before removing the first one.


·The exception message You cannot customize permission levels in a web site with inherited permission level is logged.

NOTE:  Content Matrix does not currently support permission level migrations over the CSOM or SPO/Tenant connection types.


·Permission inheritance not always preserved for item level permissions on incremental copy.

WORKAROUND:  Perform a permissions-only migration (e.g. Paste Site Objects > Permissions) after the incremental migration completes.


·When performing a "Paste as Subsite" migration to SharePoint 2019 CSOM target connection, the message You cannot customize permission levels in a web site with inherited permission level is logged for custom permissions levels.


·Permissions for items in an Access Request list are duplicated when running a Paste Site > All Site Content migration for the second time.

WORKAROUND:  When running a “Paste All Content” migration, set the “Migration Mode” tab to use the “Custom Copy” option with the “Preserve existing” checkbox selected, instead of using the “Full Copy” option.  


·Permissions will not be migrated from a SharePoint 2016 source using an OM or MEWS connection if Optimized mode is enabled.


·The User Profiles "is site searchable" property will not be migrated from a SharePoint 2016 source using an OM or MEWS connection.


Alert Migration


Issue ID

·Migration of alerts using Paste Site Objects > Alerts action are skipped when there are users mapped for other sites.

WORKAROUND:  Remove the mappings and recreate them for the target in order to migrate.


·Alerts will not be migrated from a SharePoint 2016 source using an OM or MEWS connection if Optimized mode is enabled.


Content Type Migration


Issue ID

·When copying a list, if the configuration option "Apply new content types" is selected, the content types that are not present on source get hidden on the target.


When migrating custom content types from SP 2007 or 2010 into SP 2013 and later, columns from the custom content type may added to the “Document” content type on the target.  


When copying a content type resource file, resource folder, or resource folder for list to a SharePoint 2019 target, an Exception: Server was unable to process request error is logged.


·While migrating data containing custom content types, custom columns, and SharePoint Designer workflows, the error Exception: An error occurred during the operation of a service method: You must fill out all required properties before checking in this document is logged.


Document Set Migration


Issue ID

·Document Sets are not migrated correctly when the Document Set Features is not enabled.  

WORKAROUND:  Activate the feature at the target and re-migrate.


·When migrating Document Set Snapshots (versions) over a CSOM or Import Pipeline connection to the target, there are some metadata fields that are not preserved. These include: People and Group fields, Lookup fields and MMD fields.

NOTE:  This is a current limitation of the SharePoint APIs.


·The migration account user is not added inside the Document Set Version History metadata when there is no user mapping for the actual user account.

NOTE:  When migrating Document Set snapshots (versions), if the user account in the snapshot metadata has not been mapped and the user account cannot be found, then Content Matrix will not default to the migrating account.
Instead Content Matrix will try to apply the user account using the “Migrate missing AD user” methods for SPO targets.


Records Center Migration


Issue ID

·When migrating a Records Center to SharePoint Online:

§For a Classic Team Site with Record Center features activated, an error for the RCConsole.aspx page may occur, preventing the the [Submit a Record] button on home page from working on the target team site.

§Content Organizer Folder partitioning settings only work for the root folder of a library/list, not for subfolders within it.

§Record Center Quick launch links are not migrated.



General List, Folder, and Item Migration


Issue ID

·Content Matrix Jobs get inconsistently stuck in the "copying document" action for migrating documents and document libraries.  

NOTE:  This is typically caused by a corruption in the document itself. If you try to manually upload the same file to the new SharePoint environment, you will also see a delay in the upload. For Content Matrix, it looks like the migration job is ‘stuck’ but the job is actually waiting for SharePoint to respond before continuing the rest of the migration.


·When trying to migrate a folder with the “Copying Folder” option, the message Unable to add folder 'This operation can only be performed on a file' error is returned.

NOTE:  This is an issue with "_files" which are special folders in SharePoint. These types of folders get created when you export an HTML page using IE. IE will save all the dependent files in a "_files" folder. If the user then uploads the HTML page to SP, IE will also automatically pick up the dependent files in the “_files” folder. These folders become hidden and you cannot access the files via the SharePoint OM calls.  


·'Copy Folder Permissions' is disabled in the List Content Options when copying/pasting a custom SharePoint 2007 list via the Paste List Action.  


§Run the migration using the Copy/Paste Site action.


§Run a separate permissions copy action after the "Paste List" action has been completed.


·List item versions created before the approved version are missing after migration from 2010 using a Database connection to 2013 using a local object model (OM) or client side object model (CSOM)

WORKAROUND:  Use an OM or MEWS connection for the source.


·When migrating from SharePoint 2016, version settings are not being preserved on the target when a CSOM connection is used.

WORKAROUND:  Manually change the version settings on the target.


·When migrating from SharePoint 2007 (using the MEWS connection) into SharePoint 2013/2016 (MEWS or CSOM connections) or SharePoint Online (SPO) there are some cases where version metadata values can be lost. This mainly seems to occur when the items/documents are using a custom content type and have versions.

WORKAROUND:  Ensure that the custom content type that is used on the exists on the target before the item/document migration has been run. (You may also need to select the 'Apply new content type during copy' option in the in the job configuration.)


·Custom List Forms created in SharePoint Designer are not being migrated on list or site copy when using a database connection.

WORKAROUND:  Use an OM or MEWS connection.


·Documents with versions that have an invalid hex character in the Title or another metadata property field are failing to migrate from a CSOM source connection.

WORKAROUND:  Use a DB or OM/MEWS source connection.



·Document versions fail to migrate when author/editor are not mapped (DB to tenant).  

NOTE:  The user accounts that populate the 'Created By' and 'Modified By' fields for document versions must be mapped to the appropriate target SPO user accounts in order to migrate these values correctly. If the user accounts are not mapped to the target, the values will not be preserved.


·Moderation status values are not preserved when migrating Video files from a SharePoint 2007 Publishing Library to SharePoint 2013 or later.


Access Request List Migration


Issue ID

·User Name value for the first message of an Access Request list's conversation history is not preserved.  

NOTE:  This is behavior is observed only for the first message in the conversation history. All the other conversations after that bear correct name which is same as that of the source.  


Access Request Items are not migrated in Subsites when running a migration using the Paste Site Content > All Subsites option.


Task List Migration


Issue ID

·Unable to migrate a Task list from SharePoint Online (SPO) to SP 2013 when a child Task has an earlier ID than the parent Task.

NOTE:  While not directly restricted to SPO > SP 2013 migration, the issue is that in the task list there is a Parent Task that has a higher ID then it’s child Task. This isn’t possible through the normal SharePoint UI and is the result of either a modification or a custom template change.

For example, If the parent Task has an ID value of 7 but the child Task has a ID value of 4. The parent typically needs to exist before the child, so users should never be able to create this scenario without direct modification.

When a migration of Tasks in this state occurs it returns the error message:
Exception: AddListItem - No ObjectXml [The list item could not be inserted or updated because invalid lookup values were found for the following field(s) in the list: [Parent ID].


·After migrating a SP 2010 Tasks list to SP 2013, users are unable to select the Task list in the drop down for Timeline Web Parts.

NOTE:  In SharePoint 2013 there are two types of Tasks lists, and each uses a different Template value. They are: Tasks (template = 107) and TaskWithTimelineHierarchy (Template = 171). In this case the SP 2010 Task list is migrated using the 107 template, but on the target, the users is trying to use the 171 template.

WORKAROUND:  It is possible to use a Transformer to catch and convert the template type that is being used, so the Task list is added as the TaskWithTimelineHierarchy template instead.


Survey List Migration


Issue ID

·The “Allow multiple responses” setting value turns from “Yes” to “No” after survey migration.  

NOTE:  The “Allow Multiple Responses” setting value for Survey Lists is not currently supported.


Page Migration


Issue ID

·Migrating an out-of-the-box Master Page that has been modified to have versions from a SP2007 source to a SP2013 or later target fails with an error on fetching the version metadata.

WORKAROUND:  Copy Master Pages with versioning turned off.


·(SP 2007 OM/MEWS/ DB sources only) The first Wiki page fails to migrate for chained Wiki pages and returns the error message Cannot complete this action. Please try again.


·Wiki Pages and Web Part Pages that have been customized using SharePoint Designer (SPD) are not displaying their Page contents on the target after migration.  

NOTE:  When migrating Wiki Pages, Content Matrix use the “WikiField” sub-section to migrate content, and for Web Part Pages the “Web part zones” sub-section is used. Both of these are inside the “PlaceHolderMain” section of the page. If the “PlaceHolderMain” section, or the “WikiField”/”Web part zones” sub-section(s) are removed from the page during the customization, then Content Matrix will not be able to migrate the page contents to the target.


·Custom master page migration is not supported for 2010/2013 DB source.  

WORKAROUND:  Use an OM/MEWS connection when migrating custom master pages.


·When using a Database source connection, Page Layouts for pages that have custom page layouts are not preserved at destination.  

WORKAROUND:  Use an OM or MEWS connection.


·Page layout migration across versions of SharePoint is not supported, but the UI allows for this to be selected. This results in the layouts not being migrated.


·After migrating a Site Collection, Theme Pages like DesignGallery do not load for Site Owners from the root.

NOTE:  Starting with SharePoint 2013, the migrating account needs access to the Master Page Gallery to change the 'look' of a page.


·When migrating from SharePoint Online source to a SharePoint Online target and the ”Copy Customized Form” or “Copy List Form” option is selected,, the error 'Object reference not set to an instance of an object on server. The object is associated with property ModifiedBy. Is thrown.  


Settings Migration


Issue ID

·When using the CSOM adapter to migrate to SharePoint 2013 on-premises, “Launch forms in dialog?” settings are not migrated.

WORKAROUND:  Use OM/MEWS as the target adapter.


·Theme setting are not migrated to the Tenant with ‘Paste as Site Collection’ option.


Managed Metadata Migration


Issue ID

·Empty MMD Field value in versioned list migrates as non-empty value for all open xml file formats.

WORKAROUND:  This is due to property promotion behavior in SharePoint for MMD columns. This can be bypassed by checking the option “Disable SharePoint Document Parsing” under “List Content Options.”


·Migrations return different results for document migrations with the Managed Metadata and GUID Mapping options enabled, when migrating using the CSOM adapter or the Import Pipeline options on the target connection.

NOTE:  When migrating Managed Metadata (MMD) over a CSOM connection, SharePoint will return information to Content Matrix if the terms are valid or not. When migrating MMD using the Import Pipeline, SharePoint doesn’t have a way to return information on if the terms are valid or not to the container.

This means that the logging and end results of migrating MMD using the Import Pipeline or CSOM will look slightly different, and can sometimes result in the terms migrated using the Import Pipeline having a red line under them, indicating that the terms may not be valid.


Column Migration


Issue ID

·When migrating a SP 2010 list that contains a BCS column an “Error: AddListItem – No ObjectXml” message is returned.

NOTE:  This is cause by Content Matrix trying to fetch the data from a Database table, but a different column is set as the “Identifier” column.

WORKAROUND:  Please see the Support Knowledge Base Article.


·When performing the operation "Custom Copy"-> Preserve Lists -> Update Fields, while migrating BDC fields, the error An error occurred. Administrators, see the server log for more information is logged.  

WORKAROUND:  Delete the target list and re-migrate it.


·When web parts are added to a page after column validation settings have been activated, the web parts conflict with the validation settings and the error is thrown.  

·Lookup column referencing the same library in which it is present does not migrate. (Work Item 182112).

NOTE:  This is only applicable for Document Libraries and is not supported in that instance.


·While migrating data containing custom content types, custom columns, and SharePoint Designer workflows, the error Exception: An error occurred during the operation of a service method: You must fill out all required properties before checking in this document is logged.


OneNote Notebook Migration


Issue ID

·Out-of-the-box One Note Notebooks are created o the target with the source site's title.


InfoPath Migration


Issue ID

·When copying a site that has browser enabled InfoPath forms there is an exception migrating to SharePoint Online.


·Authorship Metadata is not preserved when migrating Customized Info Path forms.

Because the relevant files live at the root, they will always be created with the currently logged in user (the connecting user account in Content Matrix) and they cannot be updated.  This is a SharePoint limitation.


·Migrating InfoPath lists that use UDCX (Data Connection Files), the link correction is not properly updating the link inside the data connection file.  

WORKAROUND:  After migration, manually open the Data Connection File and enter the correct web URL and list ID for the list/library that the InfoPath is referencing.



Nintex Forms Migration


Issue ID

·Nintex Forms are not migrating to SPO for default content types of Asset Libraries.



·A 429 (Too Many Requests) error is thrown when attempting to publish Nintex Forms on an SPO target for some of the content types.


·"StatusCode: 500, ReasonPhrase: Internal Server Error" is thrown when Copying Nintex Forms while migrating with a multi-factor authentication user account using Web Browser Authentication.


·Responsive Nintex Forms cannot be migrated from SharePoint On Premises to SharePoint Online.

WORKAROUND:  Create Classic Forms.


·Nintex Form does not appear on a SharePoint 2019 target document library when both "Copy Customized Form Pages" & "Copy Nintex Form" options are checked.

WORKAROUND:  Uncheck the Copy Customized form Pages before running the migration


Workflow Migration


Issue ID

·Workflow Histories are always migrated for SharePoint 2010 and never migrated for SharePoint 2013 and later, regardless of whether workflow instances are also migrated.  This is also true of Nintex workflows, regardless of whether the option "Preserve Nintex Workflows instance history" is checked.


·Renamed list and web workflows fail to migrate when workflows are renamed with the Console open.

WORKAROUND:  Re-launch the Console after renaming the workflows.


·Out-of-box 2007 workflow association cannot be opened after migration in SP 2013.  

WORKAROUND:  Activate 2007 workflows on the target as described in the following Microsoft technet article: 011/02/23/moss-2007-workflows-no longer-available-visible-when-weupgrade-from-2007-to-2010-databaseattach-method.aspx


·When migrating a SP 2013 SPD workflow from a CSOM source connection to a Site Collection that is set to “Read Only”, the migration fails.


§Switch connection types on the source and use the Local (OM) or Remote (MEWS).


§Manually turn off the “Read Only” setting on the source.



·The Workflow status column for SPD reusable and SPD globally reusable workflows with versions and workflow instances is changed to name of first version of SPD workflow after migration.


·SPD Global Reusable workflow migration not supported with Copy Site > Paste All Site Content,

WORKAROUND:  Use the “Paste as Site Collection” action, which is encouraged for these types of migrations.


·While migrating data containing custom content types, custom columns, and SPD workflows, the error Exception: An error occurred during the operation of a service method: You must fill out all required properties before checking in this document is logged.


·An exception is thrown when performing copy site -> paste as subsite/all site content second time and Nintex app is present on target site.  

WORKAROUND:  Content Matrix cannot currently delete a SharePoint site while it contains any SharePoint App/Add-In.


·Nintex workflows having the Calculate a Date activity with the option “Use date when action is executed” do not migrate from SharePoint 2007 to SharePoint Online.


·Nintex workflows containing custom variables in the “Pause For” activity do not have the variables migrated to SharePoint Online.

NOTE:  This is currently not supported and the variables are being tagged as comments instead.


·When Nintex workflows are migrated using a DB source connection and a MEWS target connection, the Nintex Workflow image is not displayed.


·The error 407 Proxy Authentication required is logged when you try to migrate Nintex workflows if:

§Content Matrix is using a proxy that has been imported from Internet Explorer


§the proxy server is configured as "Permit Only" with Username/Password authentication.

WORKAROUND:  Run the "Proxy Login Automator" script as described in the '407 Proxy Authentication' article located in the Metalogix Content Matrix section of the Quest Support Knowledge Base.  


Incremental Migration


Issue ID

·Custom folder content type Metadata is not migrated during incremental migration from SharePoint 2010 to a target that uses a CSOM connection.


·Blog Sites cannot support incremental copies to Office 365 /SharePoint Online.  

NOTE:  This limitation exists because Blog sites automatically start with a blog item already created, and that blog item ID cannot be changed by Content Matrix.

WORKAROUND:  Copy blog sites at the end of the full migration as follows:

a)Perform an initial Copy with Blog sites filtered out:  On the Configuration Options > Filter Options tab, Apply filter on Lists and Libraries using the filter WebTemplateID NotEquals 9.”

b)Re-run the migration on the same object(s) using the filter WebTemplateID Equals 9.”


Distributed and Self-Service Migration


Issue ID

·If a Self-Service Workstation was previously a full install of Content Matrix, old connection will still be visible in the Explorer View unless the old ‘ActiveConnections.xml’ file is deleted.

WORKAROUND: After closing the Workstation console, manually navigate to the ‘ActiveConnections.xml’ file (located at: C:\Users\<USER>\AppData\Roaming\Metalogix\Content Matrix Console - SharePoint Edition) and delete the file. Then restart the Workstation


·If a migration is performed from SharePoint On Premises to SharePoint Online and a proxy is configured using both IP address and username/password, the message Unable to obtain SharePoint Online authentication cookie is logged.

WORKAROUND:  Run the "Proxy Login Automator" script as described in the '407 Proxy Authentication' article located in the Metalogix Content Matrix section of the Quest Support Knowledge Base.  




Issue ID

· When a 2013 or 2016 Database connection is used on the source, StoragePoint Options can be selected, but the migration of StoragePoint data will fail.

WORKAROUND:  Use OM or MEWS as the source adapter.


·StoragePoint may not work properly with a SharePoint 2016 source.




Issue ID

·An error is thrown when running Content Type migrations using PowerShell 2.0 when mapping term stores - 2010 OM to 2013 MEWS or SPO.  

WORKAROUND:  Install PowerShell 4.0


·When using a Content Matrix version that is earlier than 8.3, PowerShell scripts that have the “Azure” options set to “False” will be set to “True” even for On-Premises migrations.

WORKAROUND:  Re-create the PowerShell script using a later version of Content Matrix.


eRoom Edition

Deleted Items Report


Issue ID

·Deleted items report is not generated when you connect a web application from a URL that is not the root to a site collection.  

WORKAROUND:  Reconnect using the root site collection URL.


Folder Migration


Issue ID

·URL invalid error occurs with Copy Folder operation.


Custom Field Value Migration


Issue ID

·Custom fields values using the Document Content Type are not migrated at target after mapping the column.  

WORKAROUND:  Choose a different Content Type.


eRoom Permissions Migration


Issue ID

·When migrating eRoom permissions and groups user that are present in custom groups are added in the SharePoint custom groups, as well as inside SharePoint Out of Box (OOB) groups instead of just getting added inside the Custom group .


·Additional permissions are given directly to users that belong to custom or OOB groups (eRoom > SP 2010/2013).


·Permissions to users are given both via their respective group and directly, resulting in redundant/duplicated permissions for users on the SharePoint target.


·User and Group permissions are appended instead of overwritten if they already have permissions on the target and the 'Use Existing content' collision option is selected.

WORKAROUND:   Use another collision option for migration; either:

§Overwrite existing content with same name.


§Rename current content with unique name.


Distributed Migration


Issue ID

·When we perform the migration from eRoom source for Remote migrations, and the logged in user is different on Agent and Controller, the error occurs migrating the data.


Public Folder Edition

Exchange Server - MAPI and/or Redemption Connector


Issue ID

Exception "A text field contains invalid data"  is thrown in Public Folder Edition while migrating some data using MAPI and Redemption connectors


Migration Using SPO Containers


Issue ID

After re-running Paste Exchange Folder job, Items are duplicated on target when job is configured selecting overwrite and unchecking Use SPO Container O365 Upload option.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating