SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have 2 questions regarding stsadm -o import

  1. My site has custom content types, but these are activated at site collection level. So Should I first install the WSP package on target server, then activate features prior to running an -o import command?

  2. Do I need to first create a web application and site colllection on target? Prior to an import, and then assign the import url to the url of the newly created site collection? Or do I let Sharepoint create the site collection, and then manually change the address as required?

share|improve this question
up vote 1 down vote accepted

If I understand the question right:

  1. You will want to install the WSP on the target first. You may be able to get away with not activating the features, but you may as well go ahead.

  2. Yes, you will want the target site collection to exist before issuing the import command.

My assumption is that you are building out a site from the WSP and then importing content after via the stsadm command? If this is SharePoint 2010, it is preferred to use PowerShell over STSADM.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.