Export to different name

Jun 1, 2009 at 9:49 PM

I'm thinking to use this tool to duplicate my existing site in the same server. (Same structure/children/content/workflow, different name)

Is it possible to use this tool beyond backup/restore?

Jun 3, 2009 at 7:19 AM


Yes, you certainly can use the tool in this way - I'd say it's better suited to scenarios like this than backup/restore (since in several places I note - "The following content does not get captured by the Content Migration API - alerts, audit trail, change log history, recycle-bin items, workflow tasks/state").

In your scenario, you should export the content you wish to duplicate, then on the import enter the parent web URL in the 'Import web URL: textbox, and do not select 'Retain object IDs and locations'.



Jun 4, 2009 at 3:12 PM

Thanks chrisobrien,

By your advise, assume that original site URL is "https://spserver/sites/original", and new site URL is "https://spserver/sites/copy".
I successfully export "https://spserver/sites/original" into cmp file(s).

Before I do Import, should I create "https://spserver/sites/copy"? If so, what kind of tool(Sharepoint? IIS?) I use to create?
I got error, "Unable to contact site..." inputting "https://spserver/sites/copy" on Site URL.

Next, "parent web URL" that you menstion is "https://spserver/sites/original", right?

Thanks again,


Jun 7, 2009 at 5:52 PM


Yes, you need to create the site first, using either the SharePoint UI screens/STSADM -createsite/whatever you normally use to create site collections. Importantly, the site should be created with the blank site template for import to be successful.

If you then use https://spserver/sites/copy as your value in the 'Import web URL' textbox, I'd expect that to work.



Jun 8, 2009 at 1:25 PM
Edited Jun 8, 2009 at 1:26 PM


I've got the same situation. We want to copy the content as whole from a development site to a production site. The sites are physically on the same farm and server. However due to the size of content, I can't use ordinary templates or other tools.

I tried with this tool, PRIME, and found that I liked it. But I'm having trouble trying to follow your steps Chris o Brien.

I've Exported the site successfully, by using site url as https://<server>/sites/<devsite>. When I try to import the site using Site Url https://<server>/sites/<NewSite> and import web url as https://<server>/sites/<devsite>, it runs fine, the log says it has succeeded, but when I refresh the new site it's still a blank site.

I've followed the instructions as this:
-Created a site using the Blank site template. 
-Ensured the account I'm using to export and import has rights to both sites.
-I've not ticked the 'Retain object IDs and locations' box.
-I've included all security, and all user infos.

FYI I had to use multiple files option. 

What am I doing wrong, Chris?

Jun 11, 2009 at 8:46 PM


Ah, you're using the 'Import web URL' parameter wrong - this value is used if you are importing to a subweb of the site collection. In your case, you are importing to the root of https://<server>/sites/<NewSite> so you should leave the 'Import web URL' value *empty*.

Then you should import to this site successfully.