MIGRATION PROJECTS – SHAREPOINT

Info@binaryrepublik.com | www.BinaryRepublik.com 

CONTENTSSharePoint Migration....................................................................................................................... 1

Introduction................................................................................................................................. 1Tools......................................................................................................................................... 1

Project: USAmeriBank.....................................................................................................................2Migration – SharePoint 2007 to SharePoint 2013.........................................................................2

Introduction.............................................................................................................................. 2Requirements........................................................................................................................... 2

Project: SJHC – Capital Budget Approval Process............................................................................3Custom Migration......................................................................................................................... 3

Introduction.............................................................................................................................. 3Requirements........................................................................................................................... 3

Project: Just Energy......................................................................................................................... 4Intranet Migration from SharePoint 2007 to SharePoint 2013.....................................................4

Introduction.............................................................................................................................. 4Requirements........................................................................................................................... 4

Project: Quanex............................................................................................................................... 5Redesigning & Re-Migrating to SharePoint 2010 as per best practices.......................................5

Introduction.............................................................................................................................. 5Requirements........................................................................................................................... 5

Project: Palm Beach Country Schools (PBCS)..................................................................................6SharePoint 2010 to SharePoint 2013 Migration...........................................................................6

Introduction.............................................................................................................................. 6Requirements........................................................................................................................... 6

Project: Lee County Electric Cooperative (LCEC).............................................................................8TFS Server Migration.................................................................................................................... 8

Introduction.............................................................................................................................. 8Requirements........................................................................................................................... 8

Project Server Migration..............................................................................................................9Introduction.............................................................................................................................. 9Requirements........................................................................................................................... 9

Project: Tamarac........................................................................................................................... 10Exchange Migration...................................................................................................................10

Introduction............................................................................................................................ 10Requirements......................................................................................................................... 10

1

2

SHAREPOINT MIGRATIONINTRODUCTION

SharePoint migration decisions have become more complicated due to the rapidly expanding volume of enterprise content and evolving user needs and expectations. Trends like social media, mobility and cloud computing have influenced enterprise collaboration and content management, prompting new features in SharePoint 2013 and making SharePoint Online an appealing option for some workloads.

While companies may find that SharePoint 2010 meets their content management and collaboration needs, some are considering SharePoint 2013, while others have questions about migrating content from third-party content management systems to SharePoint environments.

Others are considering SharePoint Online, the cloud-based version of the platform. It can reduce maintenance and management headaches and ease the experience for remote workers or third-party contractors. But migrating to SharePoint Online can also break site customizations, so user beware.

No matter the type of migration, concerns about SharePoint architecture, data integrity, governance and performance remain important. The growing significance of metadata as a way to categorize information and make it more findable adds another layer of complexity to any SharePoint migration.

TOOLSWe have used the following approaches and tools to migrate:

1. Content Database Migration- Migration of content database from source to destination.- This is the most preferred option for migration

2. PowerShell scripts - “stsadm” – Backup – Restore method- Another automation scripting tool to perform migration

3. ShareGate GUI & ShareGate scripts- Third-party tool for migration

4. Metalogix GUI & Metalogix scripts- Third-party tool for migration

5.

1

PROJECT: USAMERIBANKMIGRATION – SHAREPOINT 2007 TO SHAREPOINT 2013

INTRODUCTIONA leading independent bank serving Florida and Alabama with more than $2 billion in deposits, USAmeriBank is highly capitalized to ensure tremendous financial stability and provide the flexibility to offer solutions that are beyond of the capabilities of rigid regional or national companies. Their current environment was SharePoint 2007. USAmeriBank current environment was SharePoint 2007. We migrated it to SharePoint 2013.

REQUIREMENTSWe performed a content migration for USAmeriBank from SharePoint 2007 to SharePoint 2013.

Before migration, we performed a health-check on both, their current SharePoint 2007 and their new SharePoint 2013 environment.

We used ShareGate and custom PowerShell scripts for the migration.

The above screenshot is their SharePoint 2007 environment. We migrated it to SharePoint 2013.

2

PROJECT: SJHC – CAPITAL BUDGET APPROVAL PROCESSCUSTOM MIGRATION

INTRODUCTIONSJHC (South Jersey Hospital Company) is a nonprofit health care organization with four multi-specialty health centers and a total of more than 60 locations. The network, which traces its roots to 1899, comprises three hospitals, a comprehensive cancer center, several multi-specialty health centers and a total of more than 100 locations. These include urgent care; outpatient imaging and rehabilitation; numerous specialty centers, including sleep medicine, cardiac testing, digestive health and wound care; hospice and home care; and more than 30 primary and specialty physician practices in Gloucester, Cumberland, Salem and Camden counties. For SJHC, we migrated the custom workflow from SharePoint 2007 to SharePoint 2013.

REQUIREMENTSSJHC had their intranet developed in SharePoint 2007. So, they wanted to migrate SJHC environment to SharePoint 2010. Later, when SP 2013, was released, we migrated from SharePoint 2010 to SharePoint 2013.

They had their state-machine workflows, currently in-progress (in SharePoint 2007) and they wanted to have that in the same state only. Moreover, their content was too huge.

To achieve this, we chose the content-DB migration as the migration approach. The main reason, was to have the custom workflows migrated, along with their current stage and running instances. So, for 2010 and later, from SharePoint 2010 to SharePoint 2013, we chose this approach for migration.

3

PROJECT: JUST ENERGYINTRANET MIGRATION FROM SHAREPOINT 2007 TO SHAREPOINT 2013

INTRODUCTIONJust Energy is a leading provider of natural gas, electricity and green energy. We were established in 1997 and as a publicly traded company, serve more than 2 million customers across North America. Along with electricity and natural gas supply, we offer green energy product options and energy efficient programs that let customers support a cleaner environment. Just Energy stands by its vision to be the gold standard in retail energy delivering stability, value and innovation in every customer, shareholder, employee and community relationship. Our vision serves as the framework for every aspect of our business.

REQUIREMENTSJust Energy wanted their intranet migrated from SharePoint 2007 to SharePoint 2013.

We migrated their intranet portal from SharePoint 2007 to SharePoint 2013. The approach was content database migration, along with ShareGate and custom PowerShell script.

They also had many custom solutions deployed on their SharePoint 2007 environment. We migrated these custom solutions also, from SharePoint 2007 to SharePoint 2013, using Visual Studio 2008 and Visual Studio 2013.

4

PROJECT: QUANEXREDESIGNING & RE-MIGRATING TO SHAREPOINT 2010 AS PER BEST PRACTICES

INTRODUCTIONHeadquartered in Houston, Texas, with locations around the world, Quanex Building Products Corporation is an industry-leading manufacturer of engineered materials and components for building products sold to Original Equipment Manufacturers (OEMs). We design and produce energy-efficient window and door products, systems and solutions, as well as kitchen and bathroom cabinet components.

REQUIREMENTSQuanex had their intranet setup in SharePoint 2010. But, they wanted us to have it done in the approach where the best practices are maintained.

They had 3 environments – Staging, Dev and Production. Also, they had K2 servers in all the 3 environments. With this, they had their intranet portal with no proper site structure. We analyzed their current environment and redesigned the environment. Based on that, we migrated the content.

We migrated the contents using PowerShell “stsadm” backup-restore method. Also, using the same approach, we migrated K2 servers.

5

PROJECT: PALM BEACH COUNTRY SCHOOLS (PBCS)SHAREPOINT 2010 TO SHAREPOINT 2013 MIGRATION

INTRODUCTIONThe School District of Palm Beach County is the eleventh largest in the nation and the fifth largest in the state of Florida with 185 schools, serving more than 183,000 students who speak 150 languages and dialects. As the largest employer in Palm Beach County, the school district has nearly 21,000 employees, including more than 12,000 teachers.

REQUIREMENTSFor PCBS, we performed the migration from SharePoint 2010 to SharePoint 2013.

We had huge database to be migrated. So, we decided to go for content database migration. This migration had many content DBs and 2 web applications.

They had also used another 3rd party solutions, and deployed it on their environment. Along with their custom WSPs. We migrated that too, using Content Database migration approach.

The other solution was their support site.

6

For this, we had performed the content migration, along with some branding issues and performance issues fixed.

7

PROJECT: LEE COUNTY ELECTRIC COOPERATIVE (LCEC)TFS SERVER MIGRATION

INTRODUCTIONLee County Electric Cooperative has been serving Southwest Florida’s energy needs since 1940. LCEC was created to deliver power to cooperative members. The principle on which we were founded – service to local community. LCEC currently serves nearly 200,000 customers in Lee County and parts of Collier, Hendry, Charlotte, and Broward counties.

REQUIREMENTSLCEC team was using TFS 2010 to manage all their projects. They want to migrate their TFS server 2010 data to TFS server 2015.

Their architecture had 2 application server and 2 Build Servers for TFS. Each had multiple project collection having the database sizes to 10 GB each (Server).

We installed and configured the TFS in each of the new servers. Then, after configuration, we perform the Content database migration for each of the servers so as to get all the data in the same position as that in the current environment.

8

PROJECT SERVER MIGRATION

INTRODUCTIONLee County Electric Cooperative has been serving Southwest Florida’s energy needs since 1940. LCEC was created to deliver power to cooperative members. The principle on which we were founded – service to local community. LCEC currently serves nearly 200,000 customers in Lee County and parts of Collier, Hendry, Charlotte, and Broward counties.

REQUIREMENTSLCEC also wanted to migrate all the existing projects from Project Server 2010 to Project Server 2013. We have completed this migration using content database migration and PowerShell scripts.

Their architecture had 3 application servers for Project server. Each had multiple site collections having the database sizes to 5 GB each (Server).

We configured the Project server Service application in each of the new servers. Then, after configuration, we perform the content-db migration for each of the servers so as to get all the data in the same position as that in the current environment.

9

PROJECT: TAMARACEXCHANGE MIGRATION

INTRODUCTIONIdeally situated in western Broward County, Tamarac provides access to highways, railways, airports and waterways, and a wealth of cultural and sports activities. Tamarac covers a 12-square mile area and is home to more than 60,000 residents and approximately 2,000 businesses. Since its founding in 1963, the median age of the residents continue to grow younger and they are becoming more culturally diverse; all attracted to the neighborhoods, parks and recreation, and business opportunities that make Tamarac “The City for Your Life”

REQUIREMENTSTamarac was using Exchange 2003 for their inbound and outbound mails.

They wanted a migration to the latest Exchange servers i.e. - Exchange 2013. We performed this migration using a third party tool - CodeTwo. CodeTwo Exchange Migration enables direct migrations from Exchange

10

2003 to 2013, at the same time reducing the amount of time and number of pre-configuration tasks required to complete the job.

They also wanted Cross Forest Migration of current Windows Active Directory 2003 to an existing Active Directory 2008 R2. This was a bit of a typical requirement as it was 2003 and that too cross-forest migration from 2003 to 2008 R2. Still, we used Active Directory Migration Tool 3.2 (ADMT 3.2) to perform this migration. ADMT is a free utility that allows you to migrate objects (users, computers, groups, etc.) from one Windows Server Active Directory domain/forest to another.

11