Most of this is covered in the tutorial, however, why sift through that when it's right here?
UOCopy is used to copy one part of a map to another. For instance, you want to use the OSI dungeons with your custom map. When you open UOCopy, You will see this:
As always, make backups of maps when using tools like this.
Source: These are the paths to the files you are going to copy from. For a map copy, the map0.mul path must be valid. For a static item copy, the staidx0.mul and statics0.mul paths must be valid.
Destination: These are the paths to the files you are going to copy to. For a map copy, the map0.mul path must be valid. For a static item copy, the items.wsc path must be valid.
Copy Rectangle:
Min. X, Min. Y, Max. X and Max. Y defines the rectangle in the source map that is going to be copied. The Off X and Off Y is the absolute offset from (0,0) of the copied rectangle in the destination map. The Off Z is the relative altitude offset (original altitude is 2, Off Z is -5 -> altitude of copied tile or item is -3).
Copy Map (Button): This button will start the map copy.
Copy Statics (Button): This button will start the static item copy. Copied items are not directly added to a destination staidx0/statics0 file, but a file called "items.wsc" (by default, you can change the name) is created which includes all the items that were copied. You can use this file either to freeze the items with the programs Worldforge or MulTool or import it directly into SphereServer with the "import" command.