Google Directory to MySQL Integration

How Datrise loads Google Directory into MySQL

Datrise syncs Google Directory's users, groups, group members, organizational units, devices, and roles 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

Google Directory: Workspace user, group, and device directory.

MySQL: Widely used OSS relational engine (InnoDB).

How Google Directory entities map to MySQL

Google Directory entity	MySQL object	Notes
users	`google_directory_users`	id PK · custom fields → JSON columns
groups	`google_directory_groups`	id PK · linked to google_directory_users
group members	`google_directory_group_members`	id PK · linked to google_directory_users
organizational units	`google_directory_organizational_units`	id PK · linked to google_directory_users

FAQ

How does Datrise handle Google Directory'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 Google Directory 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 Google Directory 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.