Articles in this section

Walkthrough - Copy Content

Updated
Follow

Copy Content allows you to migrate content to the desired destination. You can copy documents, list items, folders, and document sets in SharePoint or Microsoft 365.

Prerequisites

  • You have Full control permissions on your source and destination list or library.
  • You have term store admin permissions on your source and destination if you have managed metadata (Terms, Term sets, Term set groups) in your migration scope.

Note: We recommend having Site Collection admin permissions since they are required to run your migration in Insane Mode.

Index

How-To

  1. Click Copy.
  2. Select Copy Content Only.
  3. Add your source credentials.
  4. Click Connect.
  5. Select your source site, and select the list or library lists-and-libraries-copy-structure.png you would like to copy the content from.
  6. Click Next.
  7. Add you destination credentials.
  8. Click Connect.
  9. Select your destination site, and select the list or library lists-and-libraries-copy-structure.png you would like to copy the content to.
  10. Click Next.
  11. Select the content you would like to copy from the source. You can copy all content from your list or library. This includes:
    • Folders folder.png
    • Site Pages and Master Pages site-page.png
    • Documents word-doc.png
    • Excel Files excel-doc.png
    • Web Part Galleries web-part-gallery.png
    • Images image.png
    • Markup Files markup-file.png
  12. Drag and drop the content into the destination, or click start-copy.png in the bottom right corner. See Copy Options if you need to apply specific parameters.
  13. Once the action is completed, the migration report will show any successes, warnings, or errors. See Migration Report for more details.

Tip: You can use property mappings, copy options, or Excel to modify your metadata during the migration.

Migrating to a destination that contains workflows

If the destination list or library has any workflows enabled, we strongly suggest to disable them before your migration in order to prevent all workflows from being triggered during migration. You can re-enable them once the migration is complete.

Related articles