Lists & library copy
Only what you select
Just the lists and libraries you tick, plus the permissions and SharePoint groups those lists need to work. The destination's navigation, theme and site settings are not touched. This is the scope for pulling three libraries out of a site rather than moving the site.
What it does
- Exactly which lists and libraries are in scope, because you ticked them.
- The permissions and groups the selected lists depend on come with them, so the copies are usable rather than inheriting whatever the destination happens to have.
- Each selected list can be Copy or Structure only.
How it runs
- Pick this scope. The source and destination sites are already chosen.
- Tick the lists. Search, drill into folders, and tick at whatever level you need.
- Confirm the selection. A dialog states exactly what was ticked before anything runs.
- It runs. Per-list progress with a live item list. Cancel offers Finish the current item, Stop now, or Keep running. Nothing is left half-written: an item is either done or not started.
How it works
The ticked lists go into the destination site as it stands: no subsite is created, and the site-level passes (navigation, site settings, theme, features) only run for the items you tick under SharePoint Items. Each pick is matched by title against the destination's lists. A list already there is left as it is and the content is copied into it; a list that is not there is created, with only the site columns and content types it actually uses. Ticking Site columns or Content types under SharePoint Items copies all of them instead.
A folder or file pick makes sure its library exists on the destination and then copies only the picked folders or files into it.
If a picked list has lookup columns, the lists they point at (and the lists those point at) are brought into the run too, copied in full, created empty, or not created, as you chose on the lookup options. With not created, the lookup column itself is left out, along with its values. A lookup target that already exists on the destination is bound to and otherwise left untouched: no columns, views, folders or items are added to it, and it is left out of the question about existing destination content.
What you need
- Site collection administrator on both ends. Reading a list's permissions needs more than read access to its items.
What it will not do
- No site navigation, theme or site-wide settings. Entire site copy is the scope that brings those.
- A site column the destination lacks is created as part of the list's schema, so a lists-only copy can still add site-level columns. It will not change anything else about the site.