Project Steps

Migrate to DynamoDB in 3 Milestones

Data can be migrated from a relational DB using the steps below. The amount of time needed will vary greatly depending upon the size, complexity, and maturity of your migration. All of these step could be completed within 4 weeks!

Milestone #1 – Design/Review the DynamoDB Table

Depending upon your progress, we will either design or review you single-table design. So the amount of time needed here will vary greatly based upon the project’s maturity. For best results, the migrated data should be loaded and incrementally tested with the new code as early in the project as possible.

Reviewing the existing system and new system to understand the access patterns.

Understand historical relational data, especially data which some may refer to as “bad”

Obtain quantity and estimated growth rates per table to understand magnitude.

Review the target state for the data. As an example, date time formats may change.

Meet with the business or review business requirements to ensure success.

Complete the onboarding of the dedicated resource.

Install the RelationalToDynamo software to prepare for the upcoming migration.

With the milestone achieved, checkpoint with management and (optionally) stakeholders

Milestone #2 –Map Relational Data to DynamoDB

With an understanding of the historical data and the target DynamoDB table, we begin the critical work of mapping the data. As part of this process, we add the necessary steps transform the data to the end-state format.

Generate baseline mapping through the software by reading the existing relational DB.

Freeze the existing database structure or new changes will need to be mapped.

Map the relational data to the new DynamoDB single-table.

Apply data transformation rules

Develop the extraction SQL scripts

If needed, customize to any specials needs, such as encryption.

Calculate and configure the number of concurrent processing needed to migrate

Test the migration on non-production environments.

Ensure the new application functions with migrated data through testing.

Review and repeat the above steps until it has been perfected.

Estimate the time and compute cost needed for the migration

Communicate the testing results, compute cost, and migration duration to management.

Milestone #3 –Migrate the Data

With testing complete, it is time to prepare for the production migration.

Establish a cutover target date and communicate the go-live to business and end-users.

Approximately one week prior, perform a mock migration to ensure success on production.

Migrate the data while closely monitoring to ensure success.

Review the migrated data and reports for issues. Address as needed.

Go live with the new system. Continue monitoring to ensure success.

Communicate the successful migration and cutover to the new system.