Product Features

Top  Previous  Next

CopyMove was designed with the following mindset:

It must be easy to install, upgrade and uninstall the product.
It must look nice and be easy to use.
It must provide seamless integration with the SharePoint Web user interface.
It must work exclusively through the official SharePoint object model (.NET API).
It must work fast and perform copy and move tasks without making the user wait longer than necessary.
It must never alter any configuration settings in document libraries and lists like adding a new content type because it is missing in the destination.
It must be extensible.

The following table outlines the features included in the product.

Feature

Description

Copy and Move documents

Enables users to copy and move selected documents across folders, lists, sites and site collections within the same farm.

Copy and Move list items

Enables users to copy and move selected list items across folders, lists, sites and site collections within the same farm.

Copy and Move folders

Enables users to copy and move complete folder structures including all content. However, users are prevented from performing a move in the event that the folder contains one or more items and/or sub-folders with unique permissions preventing the current user from deleting them.

Copy and Move Web part pages

Enables users to copy and move Web part pages including any Web parts.

Copy and Move Wiki pages

Enables users to copy and move Wiki pages including contents and Web parts.

Copy and Move publishing pages

Enables users to copy and move Publishing pages including contents and Web parts.

Copy and Move document sets

Enables users to copy and move complete document sets.

Copy and Move across site collections

Enables users to copy and move content across any accessible site collections within the same farm.

Export and Import documents

Enables users to export documents to a ZIP archive and import them again to a new location in any SharePoint farm with CopyMove installed. The document version history, Meta data and item permissions are all recorded to a file named manifest.xml on export. The import function relies on this manifest.xml file to import the documents again with full fidelity. However, the import function also recognizes plain ZIP archives that was not created by the CopyMove export function. This is handy to quickly import multiple new documents and folders to SharePoint from a local hard drive or a shared folder.

Export and Import list items

Enables users to export list items to a ZIP archive and import them again to a new location in any SharePoint farm with CopyMove installed.

Export and Import folders

Enables users to export and import complete folder structures.

Export and Import document sets

Enables users to export and import complete document sets.

Version history preservation

CopyMove can preserve the full version history for files, folders and list items unless version history has not been enabled for the destination location.

Meta data preservation

CopyMove preserves all Meta data for files, folders and list items including the created date, last modified date, created by user, last modified by user, content type, other system properties as well as all custom properties. Managed Meta data is also supported.

Item permissions preservation

Unique permissions on files, folders and list items can also be preserved .

Unique Document ID preservation

Move operations will preserve any assigned document id's while copy operations will assign new id's to the document copies.

Limit access by permissions

Site collection administrators and site owners can limit access to the CopyMove functions using the standard permissions model in SharePoint.

Enforce required fields

CopyMove will enforce required fields when copying or moving items to another library or list with additional required meta data columns. The user is in case asked to supply values for the missing columns on the source items.

Warning on file overwrite

Warns users if they are about to overwrite any files in the destination location.

Warning on loss of version history

Copying, moving and importing files and list items from lists with version history enabled to another list without versioning, implies that the version history is lost. In this situation, CopyMove issues a warning to the user before the transaction is started.

Warning on loss of Content Type information

Copying, moving and importing files and list items associated with Content Types that do not exist in the destination list, implies that this information is lost. In this situation CopyMove issues a warning to the user before the transaction is started.

Warning on loss of Metadata

Copying, moving and importing files and list items associated with custom Meta data in list columns that do not exist in the destination list, implies that this information is lost. In this situation CopyMove issues a warning to the user before the transaction is started.

Cross browser support

CopyMove has been tested with Internet Explorer 7, 8 and 9 plus FireFox and Google Chrome.

Seamless integration

Users can access the Copy, Move, Export and Import functions directly from the Ribbon in list views.

Administrators can configure transaction limits

Moving and copying large volumes of data in one transaction can be very time consuming and resource intensive leading users to believe that the application has entered a deadlock. Consequently, CopyMove enforces a limit on the number of files and the total MB that each user is allowed to select for one transaction. The limit can be configured by SharePoint administrators from SharePoint Central Administration - but only up a ceiling of 2000 files / 2 GB for users and 10000 files / 10 GB for site collection administrators.

Administrators can configure farm wide settings for CopyMove

CopyMove has several configuration options that SharePoint administrators can configure for CopyMove throughout a SharePoint farm.

Site collection administrators can override farm settings

By default CopyMove operates with the farm wide settings. But site collection administrators can choose to override most of these settings for anyone or their site collections. However, the transaction limits cannot be overridden by site collections - the limits specified by the SharePoint administrator always applies to CopyMove throughout the farm.

User profile integration

For SharePoint Server 2010, CopyMove includes special support for My Sites and Followed Sites in the destination selection tree.

PowerShell Cmdlets

Extensive and feature rich collection of CopyMove PowerShell cmdlets from copying, moving, exporting and importing SharePoint content. All configuration settings in CopyMove are also managable through PowerShell.

Workflow integration

CopyMove 2010 also installs a custom workflow action to enable workflow designers to use the Copy function in SharePoint Designer workflows.

.NET API

For server-side programmatic access to the Copy and Move functions.

JavaScript Plug-in API

Client side API for interacting with the CopyMove UI and CopyMove transactions.

SOAP Web Service

For remote programmatic access to the Copy and Move functions.

REST Web Service

For remote programmatic access to the Copy and Move functions.

Logs transactions to the Audit log

CopyMove automatically logs all transactions to the SharePoint audit log if it has been enabled for the site collection in question.

Support for custom list templates

The CopyMove item actions are also available in lists created from custom list templates that leverages the Ribbon control. That is, the CopyMove actions are registered for specific Ribbon locations regardless of list type.

SharePoint 2007 support

CopyMove is still available and working on site collections that have not been visual upgraded to SharePoint 2010 yet.

Some of the features mention that CopyMove validates Copy and Move transactions before executing them and this is indeed true. The pre-validation protects users from inadvertent loss of data and it also minimizes the risk that the transaction will fail half-way. CopyMove specifically issues a warning when it finds one or more of the following conditions to be true:

The user copies, moves or imports a file that already exists in the selected destination folder. The file will on approval of the warning, be overwritten.
The user copies, moves or imports items from a list with version history enabled to another list where version history is not enabled. The version history will on approval of the warning, be lost in the transaction.
The user copies, moves or imports items associated with a content type that does not exist in the destination list. The items will on approval of the warning be associated with the default content type in the destination list.
The user copies, moves or imports items with custom Metadata columns that are not present in the destination list. The items will on approval of the warning loose all Metadata values for the missing columns.

Then there are also the conditions where CopyMove simply aborts the transaction with a validation error:

The user copies, moves or imports a file that already exists in the selected destination folder and is checked out.
The user copies, moves or imports a file that already exists in the selected destination folder and the file has special permissions that does not allow the user to overwrite it.
The user moves a folder that contains one or more files or sub folders that the user is not allowed to delete.
The user copies or moves items to a location where the resulting URL would exceed 256 characters. SharePoint does not support longer URLs than that.
The user is trying to initiate a transaction larger than the administrative limit, which is by default 250 items or 250 MB. SharePoint administrators can increase the limit to a maximum of 2000 items and 2000 MB.