Akamai Identity Cloud Data Migration

This documentation explains – in detail – the Akamai Identity Cloud data migration process: the act of moving user data from a legacy system to the Identity Cloud’s user profile store. Suppose that, up until now, you’ve been using a non-Akamai system or vendor to store user data for your app or website. Having subscribed to the Akamai Identity Cloud, you’d like to move that data from your legacy system to the Identity Cloud. This documentation tells you exactly how to do that.

Following is a complete list of the topics covered in the data migration documentation. Admittedly, that’s a lot of documentation; however, you don’t need to read every one of these articles. Instead, see the About This Documentation note immediately following the list for more information. 

Note that, in the following list, the key articles (the articles that you really should read) are denoted by using asterisks:

About the Data Migration Documentation

The articles in this documentation are aimed at system administrators: no background in development or experience with APIs is required to perform a data migration (although that background could come in handy if you need to create data transformations). However, that does not mean that this documentation (and the data migration process) is for everyone. Typically, data migration is a one-time process: after you subscribe to Akamai, you move your legacy data to the Identity Cloud and then you are finished with data migrations. If you have already migrated your legacy data then you don’t need to worry about this. Likewise, if you don’t have any legacy data then you don’t need to worry about data migrations at all: there’s nothing for you to migrate. 

Note. Of course, even if data migration does apply to you, you don’t have to do the data transfer yourself: Akamai can do it for you. See the article What is Data Migration? for more information.

Other articles in this documentation series – such as Transforming Plurals– focus on tasks that might not apply to you: for example, if you don’t have any plural attributes to migrate then you don’t have to read the article on transforming plurals. Likewise, the documentation discusses different password hashing algorithms and explains how to transform passwords encoded with those algorithms. If that isn’t a concern of yours then there’s no need to worry about whether or not you need to read that article: you probably don’t.