Methodology

Our tried and tested Methodology, which is central to Proventeq’s business, makes migration work harder for you.

Supported by Proventeq’s highly experienced team of consultants, we follow sound strategic processes that guarantee a seamless migration. Find out more about our Methodology...

A Sound Methodology

Our projects are underpinned by a sound and robust methodology. The Proventeq Content Migration Methodology follows the industry standard Data Migration ETL (Extract Transform and Load) principles. Crucially, our ETL approach separates the data extraction and transformation stages. This approach enables the migration rule development to progress, while the new ‘target’ system is under development.

And because our rule development process is iterative, rules are progressively refined to improve the quality of the content being loaded into the target system.

Our Methodology translates into a series of transparent stages, which create a comprehensive road map for successful content migration.

Discovery

Proventeq’s Discovery phase is designed to present a detailed picture of current content and systems. A series of  reports clarify the volume and type of content, and key areas such as security, access patterns and usage. These reports help the customer to understand and define the true scope of migration.

Analyse

Here we work with the customer to analyse both the source information and the target system design. The aim is to identify business requirements and protocols and convert them into migration rules which can be configured in the Proventeq Accelerator migration tool.

We will identify the scope for Migration into the target system, including rules for transforming the source content and rules for extracting information from source databases. We will also create the Metadata rules for target content items.

By the end of this phase we will have defined the Migration scope and set the rules for migrating content.

Capture & Conform

All the websites that are part of the migration scope will be captured and converted into a structured format. We will crawl the source pages and conform the unstructured HTML into structured XHTML. This will then be stored in the staging repository for the transformation phase.

Also during this stage, we will transfer data from the required fields of all content databases into the staging repository.

Extract

Using the migration rules set at the start of the process, we will split out the source XHTML into individual fields – such as Title, Summary, Body-Text – ready for loading into the target Content Management System.

We will also extract the Metadata, working with the database extraction rules and the Target Content Architecture we defined earlier. By the end of this stage, all extracted content will be stored in the staging repository.

Transform

All the extracted fields that have been stored in the staging repository will now be transformed into the target Content Management Structure. At this point we have a clear migration rules document to work from and the target content architecture is fully defined.

By separating the extraction and transformation of content from the load into the target system, we are able to develop the migration rules while the target system is under development.

Load

Now we are ready to load the transformed content into the target system, using the load adapter. This adapter connects to the target system and allows the migration to progress without having any impact on the target system while it is under development.

By the end of this stage, all content items will be loaded into the target Content Management System.

Enhance

Content migration isn’t just about moving your data from one source to another. It should also enhance and optimise your content. Using the Content management guidelines, we will now take the content loaded on to the new system and enhance it.