Amazon DynamoDB to MySQL Integration

How Datrise loads Amazon DynamoDB into MySQL

Datrise syncs Amazon DynamoDB's tables, items, partition keys, sort keys, attributes, and stream records into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Amazon DynamoDB: Serverless key-value and document store on AWS.

MySQL: Widely used OSS relational engine (InnoDB).

How Amazon DynamoDB entities map to MySQL

Amazon DynamoDB entity	MySQL object	Notes
tables	`source_dynamodb_tables`	id PK · custom fields → JSON columns
items	`source_dynamodb_items`	id PK · linked to source_dynamodb_tables
partition keys	`source_dynamodb_partition_keys`	id PK · linked to source_dynamodb_tables
sort keys	`source_dynamodb_sort_keys`	id PK · linked to source_dynamodb_tables

FAQ

How does Datrise handle Amazon DynamoDB's custom fields in MySQL?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.

How does the Amazon DynamoDB to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Amazon DynamoDB to MySQL the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.