Not logged in - Login
< back

Settings

Settings

List Item Settings

Note: The depicted version is a pre-release version.

The List Copy Settings feature provides the following functions:

Copy Views:

Allows for the replication of views associated with a list or library.

Create Lookup Lists:

When working with lists or libraries containing lookup columns, this function checks for the existence of the associated lookup list and creates it if necessary.

Fill Lookup Lists:

After creating a lookup list, this function efficiently imports items from the source site to the destination site, ensuring data consistency before starting the list import process.

Delete Destination List:

During list or library creation, a check is performed to identify pre-existing fields on the destination list that do not exist in the source. If such fields are found, they are removed. Caution is advised when performing this operation, as it carries risks, including potential data loss. Deleted fields and values cannot be recovered from the recycling bin. Please exercise care and consider the consequences when engaging in field deletion operations.

Item File Copy Settings

Note: The depicted version is a pre-release version.

The Item File Copy settings feature provides the following functions:

Skip Files

  • Copy All: -This Willoption notavoids checkchecking if item/filean item or file exists at the destination. ThisWhile it slightly speeds up the migration, howeverit may cause an error on the item/fileerrors if the item/fileitem or file already exists asand attempts to overwrite it may try and overwrite a file - but will fail unless(unless it matches the Unique ID.ID). RecommendedIt is recommended to only use this itemoption ononly during initial migrations.

  • Skip file/item if exists at destination -: This option will scanscans the destination list/library.list/library Willand skipskips items/files if they already exist at the destination.there.

  • Skip file/item if newer at the destination: -With Thisthis option will scanoption, the destination,system scans the destination and overwriteoverwrites existnigexisting item/fileitems/files if thetheir modified date is later at the source.

Match lookupLookup valuesValues byBy

  • By Id -: When matching lookups, it will match values onuse the itemsitem's ID.ID for comparison. This option shouldis besuitable used onfor new migrations,migrations howeverbut may not work correctly if the destination look uplookup list has differnetdifferent IdsIDs fromcompared to the source, it will not match correctly.source.

  • By Value -: When matching lookups, it will matchuse valuesthe item's displayed value, typically based on the items value. The value depends on the lookupslookup's display field (usually Title). ThisUse this option should only be used if you knoware certain that the ID'sIDs will not match.

Maintain itemsItems' Unique GUID?

In SharePoint, each item and file has a regular ID that's visible in SharePoint views. Additionally, there's a hidden Unique ID/GUID, which is hidden andID/GUID used for internal purposes. It's essentialcrucial to understand that when copying an item or file, if a duplicate exists in a different location (such as a different site or list), it will not be copied. However, if the duplicate is in the same location and has the same filename or title, the system will append versions to the existing file ratherinstead thanof creating a new copy.

As a rule of thumb, considerConsider the following:following guidelines:

  • If you are migrating to a new site in a different site collection from the source, it is advisable to leave this feature on.

  • If you are resuming a copy operation that has stopped, you should haveenable this feature on to ensure that existing files are appended.

  • However, if you are copying the source to a site within the same collection,collection or if you have already copied the site to another site in the same collection, it must be turned off to avoid issues with duplicate handlinghandling.

Retain All Versions

Selecting this option retains all versions, which can slow down migrations if there are many versions.

  • Number of versions to retain: Valid options are 0 to ∞. The fewer versions retained, the quicker the migration will proceed.

Publish Site Pages After Copy

When migrating site pages, minor versions may be created when updating and appending the web parts. Enabling this option ensures the final version is published. If a site page has no published version, it may not appear in the navigation.