Is Your Migration Bigger than a Breadbox?
I just posted an article on the Axceler blog that further explores the strategic considerations outlined in my ECM Connection article on SharePoint migration planning. Here’s my main point: even small deployments (based on the number of sites or size of your content databases) can have great complexity. Migrations are rarely simple, so until you do some discovery and planning, don’t commit to a project delivery date.
Some things to think about as you consider your pending SharePoint migration:
- How many sites need to be migrated?
- How much content is there? What is the size of your content database(s)?
- What needs to happen with versions?
- What needs to happen with metadata?
- Do you need to move custom features?
- Are there line of business application integrations?
- Do you need to move custom designs/look and feel?
- Is it a straight dump of content, or does the content need to be transformed?
Answering these questions will help you properly scope your project, and reduce the risks associated with your SharePoint migration.
One of the most compelling stories for SharePoint is its sheer extensibility. There is no such thing as a homogenous deployment – SharePoint is build-to-suit. It’s a platform, which can make migrations very complex. You need to understand the end goal of your migration. Read the rest here.
