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

We have our SharePoint sites in the following tree structure:

    +--- Division A
         +--- Department 1
         +--- Department 2
         +--- Department 3
    +--- Division B
         +--- Department 1 
         +--- Department 2 
         +--- Department 3

I have a number of metadata columns that are defined at the Division A level because they're used across all three department sites. Our Corporate Governance team recently chose to prohibit custom columns at the Division level, limiting that customization to the Department level. So I need to move some columns.

Let's say I've got a "NumberOfEmployees" column at the Division A level. Right now, I'm thinking that I'll need to do the following:

  1. Create three NumberOfEmployees-Temp columns; one at each of the Department levels.

  2. Copy & paste the metadata from NumberOfEmployees to NumberOfEmployees-Temp in each Department's data.

  3. Delete NumberOfEmployees from the Divison A level.

  4. Rename NumberOfEmployees-Temp to NumberOfEmployees in each of the three Departments.

Is there a less painful way to do this?

share|improve this question
up vote 0 down vote accepted

I'd be asking WHY the governance team is restricting custom columns at a given level.

A good process should allow for exceptions when justified.

Otherwise I'd be looking towards a Powershell script to migrate the data to save that manual step at the least.

share|improve this answer
I'm asking those same questions, believe you me. I just wish someone would answer. :) – dwwilson66 Aug 13 '12 at 16:18

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.