Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - Release Notes

All Editions

Automatic Updates

Description

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

AND

§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.  

408256

License Key

Description

Issue ID

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

423063

Multi-factor Authentication

Description

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.

389424

SharePoint Modern Team Sites

Description

Issue ID

If you are using Web Browser Authentication and try to connect to or load in the Console an SPO private modern team site for which you are not a Site Collection Administrator, the error You need permission to access this site displays in the login browser.

WORKAROUND:  

·Make sure the account you are using to connect is a Site Collection Administrator for the private modern team site

OR

·Use Office 365 ADFS authentication to connect.

402033

 

SharePoint Edition

Migration to SharePoint Online

Description

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.  

251718

·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.

417247

·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.

426597

·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.

420126

·File migration fails when migration is done via Azure SPO 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.

204168

·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 Azure Pipeline.

180924

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

194826

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

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

AND

§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.  

408256

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

417164

Migrations from SharePoint Online to SharePoint On Premises

Description

Issue ID

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

408023

Locked Site Collections

Description

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.

115704

Modern Team Sites

Description

Issue ID

·The theme of a modern team site is not preserved when migrated from an "old style" team site.

WORKAROUND:  Filter out Home.aspx page from the migration.

397817

·If the name of a subsite is changed on the Site Options tab, the site is created on the target modern team site with the default name.

414281

·When data is migrated from one modern team site to another, landing page are not migrated (i.e., the page on the target is blank).

410789

·Unlicensed users in a SharePoint Online tenant are migrated as Office 365 Group Members and not as Office 365 Group Owners.

414364

·There is an intermittent issue with Modern Team Site migrations failing.

427062

Community Site Migration

Description

Issue ID

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

232167

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

232176

·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.

233345

·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.

233278

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

232168

·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.

233283

·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.

233290

·'PostedBy’ column value is not preserved for target as SPO (AZURE) when target is a Community Site.  

WORKAROUND:  Migrate using CSOM only.

233554

Blog Site Migration

Description

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"

180900

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

282870

Publishing Portal Migration

Description

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.

203983

MySite Migration

Description

Issue ID

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

176692

·“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.

179036

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

179060

·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.

420301

SharePoint Permissions Migration

Description

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.

178568

·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.

181193

·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.

179750

·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.

419520

·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.  

178409

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

427061

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

427061

Alert Migration

Description

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.

181067

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

427061

Content Type Migration

Description

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.

182147

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

274505

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.

424447

·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.

420167

Document Set Migration

Description

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.

204343

·When migrating Document Set Snapshots (versions) over a CSOM or Azure 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.

284465

·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.

--

General List, Folder, and Item Migration

Description

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.

245657

·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.  

171550

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

WORKAROUND:

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

OR

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

181170

·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.

176588

·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.

203766

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

181383

·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.

179625

·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.

311332

311682

·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.

201631

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

27687

Access Request List Migration

Description

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.  

180492

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

179462

Task List Migration

Description

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].

194778

·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.

194730

Survey List Migration

Description

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.

181216

Page Migration

Description

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.

182519

·(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.

WORKAROUND: Use the NWS connection for migrating 2007 Wiki Libraries.  

171548

·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.

194745

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

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

179198

·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.

181072

·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.

203876

·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.

178382

·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.  

204252

Settings Migration

Description

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.

179058

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

179060

Managed Metadata Migration

Description

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.”

124696

·Migrations return different results for document migrations with the Managed Metadata and GUID Mapping options enabled, when migrating using the CSOM adapter or the Azure 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 over Azure, 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 over Azure or CSOM will look slightly different, and can sometimes result in the terms migrated over Azure having a red line under them, indicating that the terms may not be valid.

271320

Column Migration

Description

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.

307507

·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.

180869

·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.

281741

·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.

413746

OneNote Notebook Migration

Description

Issue ID

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

420302

InfoPath Migration

Description

Issue ID

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

204356

·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.

256779

·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.

310825

310826

Workflow Migration

Description

Issue ID

·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.

404724

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

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

99326

·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.

WORKAROUNDS:

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

OR

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

283742

273643

·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.

204376

·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.

204377

·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.

420167

·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.

252485

·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.

253468

·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.

254006

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

419875

·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

AND

§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.  

408256

Web Part Migration

Description

Issue ID

·Connected web parts are lost after migrating to O365.  (Work Item )

WORKAROUND:  This is due to current limitations of Microsoft's Client Side Object Model API. After migration, connections between web parts should be manually re-created on the O365 site.

102229

·Due to a bug in SharePoint 2010, the Calendar web part (with summary view) is not migrated to the destination from SP2010 DB to SP2013 OM.  

WORKAROUND:  

1.On the source, browse to the page with the affected web part.

2.Confirm that you are not editing the page

3.Click the arrow in the top-right of the web part

4.Click Edit Web Part

5.Change the view to the desired one.

6.Click OK

7.Re-run the migration.

178682

·Web parts in a wiki page are not migrated when content approval is in-place at the target.  

WORKAROUND:  Disable content approval of the wiki pages library before migration.

·When migrating web parts from SP 2010 to SPO, any contents/settings inside a “Wiki Content web part” are not preserved. (Work Item 258370)

NOTE:  This issue is specifically for using NWS/CSOM as a source or target adapter. The NWS/CSOM APIs do not have access to fetch or write these values, and as a result Content Matrix cannot set them (or if using NWS/CSOM on the source, it can’t read the values).

WORKAROUND:  To resolve the issue of reading the values from a source, users can use the DB, OM, or MEWS adapters instead. For the target, the OM or MEWS adapters are recommended. In the case of migrating to a SharePoint Online target (SPO) there is no current workaround.

204321

·When migrating web parts from a SP 2010 source using a NWS connection to SPO using a CSOM connection, any contents/settings inside a “Wiki Content web part” are not preserved.

NOTE:  The NWS/CSOM APIs do not have access to fetch or write these values, and as a result Content Matrix cannot set them (or if using NWS/CSOM on the source, it can’t read the values).

258370

·Web parts not migrated when added inside wiki page having draft with minor version enabled from SP 2010 (MEWS) to 20103 (CSOM).  

NOTE:  This issue is only encountered when using the Paste Site Content > All Site Content option. The issue does not occur when migrating and pasting as a Site Collection.

180285

·When migrating MySites froma 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.

420301

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

NOTE:  This behavior has been observed with Team Sites as well.

282870

·Some XSLTListView web parts do not migrate from SharePoint 2010 to SharePoint 2013 when using the Database Adapter for the source connection.

WORKAROUND:  Use 2010 MEWS or OM source and the XSLLISTVIEWWEBPARTS will migrate successfully. Continue other aspects of migration using the database adapter if needed.

203857

·When migrating “list view” web parts from SP 2007, they are added as “list view” web parts in SP 2013 instead of converting them to “XSLT list view” web parts. In addition, there are also some web part settings on the source that that use different default values on the target, and Content Matrix does not currently change these values (for example, the Base ID value).  

WORKAROUND:  There is a configuration setting in the Content Matrix “ApplicationSettings.xml” file that can be modified to convert standard “list view” web parts into “XSLT list view” web parts. This must be used in conjunction with a Transformer to correctly set the other web part settings (like the Base ID value). A KB article on this WORKAROUND can be found on the Support Knowledge Base portal.

194742

194814

·Due to some SharePoint API limitations, when migrating to a SP 2013/SP 2016/SPO target, the web part ‘Miscellaneous’ option for ‘Display Search Box’ is being enabled.

264911

·After a Media web part is migrated, the wrong URL for the media content is set.

418147

·A Choice Filter web part may lose its filter values and connections after migration.​

419403

Incremental Migration

Description

Issue ID

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

181984

·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.”

176629

Distributed and Self-Service Migration

Description

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

352855

·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.  

409813

StoragePoint

Description

Issue ID

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

427061

PowerShell

Description

Issue ID

·When running a PowerShell script created in a release prior to 8.1, an error is thrown if you try to connect to the Jobs or Distributed database using SQL authentication.

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

220248

·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

181226

·When using a Content Matrix version that is earlier tha 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.

258931

Blogs and Wikis Edition

Special Characters

Description

Issue ID

·Page title prefix gets omitted when the page title starts with a special character.  

NOTE:  The special character only is omitted, and is a character that would be illegal in SharePoint regardless. This is by design to ensure proper SharePoint naming standards.

181782

Resized Images

Description

Issue ID

·Resized images are not rendered on page at target for Blogs and Wiki >> SP 2010 publishing site

194862

·Metadata of Resized images (Authorship Information, Modified by, Modified Date, and Page Name) are not preserved when migrating from Blogs & Wiki Edition for SP 2010/2013/SPO using OM/CSOM

194864

MediaWiki Source Connection

Description

Issue ID

·When connecting to a MediaWiki environment, Redirect pages will not be displayed.

NOTE:  When connected to MediaWiki environments, Content Matrix does not populate redirect pages in the ‘Explorer View’ tab. This is because they are not ‘content’ pages and have no equivalent pages/concepts in SharePoint.

300492

eRoom Edition

Deleted Items Report

Description

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.

181954

Custom Field Value Migration

Description

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.

203891

eRoom Permissions Migration

Description

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 .

181083

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

182312

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

182340

·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.

OR

§Rename current content with unique name.

182341

Distributed Migration

Description

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.

426642

Related Documents