If you should come to the point where your Pure contract with Elsevier ends and you need to migrate data to another system, you will need a migration strategy. The primary goal of the migration strategy is to extract your data and to ensure that your data is no longer in Elsevier's possession following the termination of your Pure contract. In addition, it is important that the data can be migrated to another system, and that the whole process is controlled by you.

This document gives you an overview of the tasks and timelines needed. Please note that you will need toassess and investigate on your own how to perform the migration strategy with the resources and skills of your local team or a third party contractor.

Overall Process

The overall process of an exit plan is comprised of the following steps:

1. Extract data from Pure in a structured format.
2. Store data at your controlled storage.
3. Shutdown and delete any Pure system hosted for you by Elsevier.
4. Transform data to the desired ingestion format for your new Research Information Management System (RIMS).
5. Ingest data into the new RIMS.

To accomplish this, Pure comes with a web service able to extract data, and Elsevier provides support via our online Pure support system for the duration of your Pure contract. The actual extraction and transformation of data is your responsibility.

Extract data from Pure

Pure comes out-of-the-box with a web service . Therefore you can extract data at any time during your Pure contract. Many Pure clients use the Pure web service to extract and feed data into an internal data warehouse, a reporting engine, internal or external staff web pages, or another campus system.

Data is extracted using the Pure web service, enabling you to extract both metadata and file data in XML and JSON format. The choice of format usually depends on the format for ingestion into the new RIMS. For example, if the new system requires XML, then extracting data from Pure in XML is preferred.

Using a web service requires either an ETL (Extract, Transform, and Load) tool or programming skills and some experience in working with web services. For an experienced programmer with a general understanding of web services, extraction will take from one to a few days work to create the program, and then a couple of days to extract the data, depending on the amount of data you have in Pure.

Please find information about the Pure web service here or Pure API:

• For general information on the webservice and API see Classic (read-only) Webservices and the Pure API - Getting data in and out of Pure
• For classic webservice go to: https://<your-pure-server>/ws. Here you will find the interactive web service documentation on your Pure server.
• If Pure API is enabled gp to: https://<your-pure-server>/ws/api. Here you will find the interactive documentation for the Pure API 
• For webinars on using the web service go to Master Classes in Pure

Shutdown Pure and delete Elsevier-hosted data

When data is stored on your controlled storage we can delete any data and Pure system hosted on Elsevier's infrastructure. This is done either upon your request to us (via Client community) or at the latest when your Pure contract runs out.

Transform and ingest data into new system

Data transformation to the desired ingestion format can be done in several ways, usually either by an ETL tool or direct programming. Ask the vendor of your new system to assist or guide you transforming data into the correct format for the new system.

You can expect this to take any time from a few weeks to several months depending on your resources and the help and guidance provided by the vendor of your new system or a third party contractor.