A global financial services company modernized its intranet platform that supports approximately 5,000 U.S. financial advisors. The company intranet receives about two million page views per month and is the most widely used communication and knowledge-sharing vehicle for the company, servicing nearly 15,000 associates across more than 2,300 locations.
Customers
Content Migration
Challenge
- The company needed to transition from a highly customized content management system to SharePoint 2010 with minimum impact to end users and content authors.
- Their SharePoint architecture required invoking JavaScript to ensure that SharePoint form fields were complete and consistent.
Solution
- Kapow Katalyst allowed the company to both crawl the content of the Vignette system and use its database connector to capture additional metadata.
- The team was able to build repeatable automated extraction, transformation and upload workflows to move content from legacy systems into the new SharePoint taxonomy and platform.
Results
- The Katalyst automation-led approach enabled this customer to migrate 8,000 pages of content in only 4 weeks.
- Katalyst also transformed all content to exploit advanced SharePoint features such as Web Part Pages – without developing any code.
The Ministry of General Affairs for The Netherlands migrated content from 9 diverse systems into their new CMS with no coding required.
Challenge
- As a part of their Central Government Communication New Style project, they needed to consolidate 16 websites from 13 different departments into 1 new website, www.rijksoverheid.nl.
- The content from the 16 websites was stored in 9 different content management systems, with over 125,000 unique content items.
Solution
- Kapow enabled the migration and consolidation of this content into a new system, centralized on the Hippo CMS platform.
- No coding was required.
Results
- Dramatic reduction in the cost and time required to migrate each page.
- Completion dates could be fixed because the process ran on a reliable schedule.
- No content freeze was required on the existing systems during the course of the migration.
Codan, the third largest insurance company in Scandinavia, went from legacy to SharePoint CMS in a few weeks.
Challenge
- Codan needed to migrate approximately 2,000 pages of content from 2 legacy systems into Microsoft SharePoint.
- Manual and scripted approaches did not meet their time and resource requirements.
Solution
- Kapow was used to extract source content from legacy systems and transform it for loading into SharePoint.
- No coding was required.
Results
- After a 3 day POC and 5 days of basic robot development, Codan was able to complete the rest of the migration within a couple of weeks.
- Nearly 100% of content was migrated automatically.
Kaiser Permanente saved 60% of costs by migrating content automatically with Kapow.
Challenge
- Kaiser needed to migrate content from multiple sites, stored in various formats (including static HTML) into TeamSite CMS.
Solution
- Using Kapow, they were able to migrate content automatically.
- Content migration required no coding and no content freeze.
Results
- Cost savings of 60% over manual effort.
- Zero data conversion errors.
Lenovo, the fastest growing of the top 5 PC manufacturers, chose Kapow for fast and effortless content migration to Interwoven.
Challenge
- Lenovo needed to migrate legacy content from a variety of sources and formats to Interwoven.
- This required access to content in Quest DB, Domino DB, static HTML and custom .NET applications.
Solution
- Using Kapow, they were able to migrate content automatically.
- Content migration required no coding and no content freeze.
Results
- Dramatic time and cost savings compared to scripting or manual approach.
- Zero data conversion errors.
Lexmark, a leading provider of printing and imaging products, migrated content from 50+ country sites to Vignette.
Challenge
- Lexmark needed to migrate their entire set of websites (50+ country sites) from Vignette into Documentum.
- Traditional content migration methods were too costly and time consuming.
Solution
- Using Kapow, they were able to migrate content automatically.
- Content migration required no coding and no content freeze.
Results
- Dramatic time and cost savings compared to scripting or manual approach.
- Zero data conversion errors.
Santa Clara County saved 5 months and 50% of cost by automating content migration with Kapow.
Challenge
- Migrate content between internal and external portals and between different versions of Vignette CMS.
- Eliminate manual data conversion.
- Enable portal consolidation and content integration.
Solution
- With Kapow, content was automatically migrated between internal and external portals and between different versions of Vignette.
- No coding was required.
Results
- Cost savings of over 50% compared to internal estimates.
- Project was completed in 3 months vs. 8 months projected for manual effort.
- Improved data quality through automated cleansing.
Red Hat saved 67% in time and cost by using Kapow for content migration to eXo.
Challenge
- Red Hat needed to migrate about 5,000 pages of static HTML into an open source CMS called eXo.
- Accenture estimated it would take nearly 3,000 man hours to do this project manually.
Solution
- Using Kapow, they were able to migrate content automatically.
- Content migration required no coding and no content freeze.
Results
- Over 67% projected savings in time and cost compared to manual method.
- Zero data conversion errors.
The ASPCA's content migration to SiteCore was completed in less than 3 week, a huge time savings over a manual or scripted approach.
Challenge
- The ASPCA needed to migrate content from Convio to SiteCore CMS.
- Traditional content migration methods were too costly and time consuming.
Solution
- Using Kapow, they were able to migrate content automatically.
- Content migration required no coding and no content freeze.
Results
- Kapow work was completed in 2-3 weeks.
- Huge savings over manual or scripted approach.
Progress Energy, a Fortune 500 energy company, chose Kapow because it could handle content migration to Interwoven without disrupting business operations.
Challenge
- Progress Energy needed to migrate web content to Interwoven without disrupting business operations.
- They needed to automate their internal website and file system inventory.
Solution
- Using Kapow, they were able to migrate content automatically.
- Content migration required no coding and no content freeze.
Results
- Using Kapow, they performed file system and website inventory in a matter of days.
- No content freeze was required, enabling successful content migration with no disruption to business operations.
With Kapow, content migration was complete in 2 ½ weeks.
Challenge
- The Department of Labor needed to migrate 3,500 pages of content from their intranet portal (Labornet) into Oracle WebCenter.
- The content included ASP, HTML pages and 14,000 assets, including images, Word, PDF, PowerPoint, MP3 and WMV files.
Solution
- They evaluated a “black box” approach, but ultimately chose the Kapow automated solution because it provided the most effective way to extract metadata and binary content without the need for extra coding.
- Kapow was able to crawl the file system directly for content and loop through all the source data, including “orphaned” content.
- Content was loaded directly into Oracle WebCenter through the web front-end.
Results
- They spent 5 days on development.
- The migration was complete in 2.5 weeks.
With Kapow, the U.S. Department of Health and Human Services completed their content migration in one-tenth the time.
Challenge
- The DHHS had multiple public-facing websites and portals, each with its own look and feel. They wanted to migrate content to a unified Hyperwave CMS.
- Traditional content migration methods were too time-consuming and costly based on initial estimates.
- As part of content migration, they wanted to detect and correct issues such as broken links.
- As they changed standards, they wanted an automated way to make the changes across all content in the CMS.
Solution
- Using Kapow, web assets and portals were turned into JSR-168 portlets and brought into a single portal, providing a central location to view all DHHS assets.
- Web assets were transformed to promote a common look and feel.
- Content analysis and updates were automated.
- A single search mechanism performs a federated search across all DHHS portlets. Search result links are clipped into a portlet with the same look and feel of the DHHS central site, so links don't take users off the central site.
Results
- 90% reduction of resources and time for content migration.
- No UI redesign was needed.
The U.S. Forest Service is saving 40,000 hours of manual effort by migrating content to their new CMS with Kapow.
Challenge
- They need to migrate 100+ individual forestry websites, comprising 45,000 pages of content, onto a single platform driven by Oracle WebCenter.
- Manual content migration would require an estimated 40,000 hours.
Solution
- Using Kapow, content migration is automatic.
- Content migration requires no coding and no content freeze.
Results
- Content migration will be complete in 4-6 weeks.
- No risk of data conversion errors.
The U.S. Navy migrated content from 22 portals and thousands of websites into Oracle CMS using Kapow.
With Kapow, ZFS completed content migration to their new CMS in 10 weeks.
Challenge
- ZFS needed to migrate 3 different sites into their new CMS.
- The old sites were based on Gauss, FrontPage and Lotus Notes.
Solution
- Using Kapow, they were able to migrate content automatically.
- Content migration required no coding and no content freeze.
Results
- The migration was done in about 10 weeks.
- A comparable manual effort for 6 employees would have taken 26 weeks.
With Kapow, Orange County completed content migration to their Vignette portal in 6 weeks.
Challenge
- They needed to migrate content from a variety of county websites into a Vignette portal.
- Traditional methods were too costly and time-consuming.
Solution
- Using Kapow, they were able to migrate content automatically.
- Content migration required no coding and no content freeze.
Results
- The entire migration was completed in approximately 6 weeks.
- Zero data conversion errors.
With Kapow, content migration to a new CMS took less than 8 weeks for the world's largest humanitarian organization.
Challenge
- They needed to migrate content from various sites into a new EPIServer CMS.
- The content was on multiple sites and in 3 languages.
Solution
- Using Kapow, they were able to migrate content automatically.
- Content migration required no coding and no content freeze.
Results
- Migration took 6-8 weeks.
- Zero data conversion errors.