City of Phoenix
Migration from Oracle UCM to SharePoint
Phoenix is the fifth largest city in the United States of America and is the state capital of Arizona. The headquarters of numerous Arizona state government agencies are in Phoenix, many of which are in the State Capitol district immediately west of downtown. The website www.phoenix.gov provides news updates and information on the city services available to residents, businesses and visitors
Case Study Overview
City of Phoenix wanted to migrate its website from Oracle UCM to SharePoint with the aim of modernising their information management infrastructure.
The Complexities Of Migrating From Oracle UCM To SharePoint
- Over 50,000 items were stored in Oracle UCM content server. The content structure and site sections configuration in the Source system had to be analysed. This included documents, pages, forms and images.
- The forms and pages were to be differentiated based on the naming conventions and rules provided by the client.
- We had to factor in items that had discrepancies [in the websitesection(blank)] while working on the structure mapping and loading Pages to particular libraries within sub-sites so that the appropriate taxonomy could be assigned correctly.
- Each page had links to other pages, media assets and documents, which had to be redirected to new URLs created within the target SharePoint environment.
- Library settings had been set to “Require documents to be checked out”. Overriding this setting in every library was crucial for the client.
- Many assets had the Content Type set as “Web-Content” in the source Oracle UCM system. These needed to be changed to a “Document” Content Type without affecting the content types of other web pages.
Solving City of Phoenix’ Unique Challenges
Proventeq Migration Accelerator was the key technology solution used to extract, transform, cleanse & migrate content into the new target SharePoint environment.
Proventeq Discovery and Pre-Migration check tools helped to analyse all available items in Oracle UCM, identifying any inconsistencies in content and naming conventions.
Proventeq's rule-based scripting tool was used to cleanse anomalies in source content and transform consistently.
During the process of standardising the content and metadata, certain items were configured to be transformed and migrated while items out of scope were skipped.
Migration consultants defined a strategy and agreed on a migration plan with the client.
An ‘exception plan’ was devised to resolve any inconsistent source files.
A ‘Delta plan’ was also provisioned for any last minutes content changes while the migration was still in process.