Skill

drt-migrate

From drt

Migrates Reverse ETL syncs from Census, Hightouch, Polytomic, or custom scripts to drt by mapping sources, destinations, schedules, and generating sync YAML configs.

data-engineering

npx claudepluginhub drt-hub/drt --plugin drt

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Help the user migrate from an existing Reverse ETL tool (Census, Hightouch, Polytomic, or custom scripts) to drt.

SKILL.md

Similar Skills

drt-migrate

Migrates Reverse ETL syncs from Census, Hightouch, Polytomic, or custom scripts to drt by mapping sources, destinations, schedules, and generating sync YAML configs.

drt-hub

drt-create-sync

Generates drt sync YAML configuration files for Reverse ETL pipelines, connecting data warehouse tables via dbt refs or SQL to destinations like Slack, Discord, REST APIs, HubSpot, GitHub Actions, Google Sheets, PostgreSQL, or MySQL.

drt

setting-up-a-data-warehouse-source

Guides connecting data warehouse sources like Postgres, MySQL, Stripe, HubSpot, MongoDB, Salesforce, BigQuery, Snowflake to PostHog via wizard, credential validation, table discovery, sync selection, and creation.

1 file

posthog

Stats

Parent Repo Stars11

Parent Repo Forks13

Last CommitMar 30, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Census / Hightouch concept

drt equivalent

Source (BigQuery model)

model: ref('table') or raw SQL

Destination connection

destination.type + auth config

Sync behavior: Full

sync.mode: full

Sync behavior: Append

sync.mode: incremental + cursor_field

Field mappings

body_template / properties_template (Jinja2)

Run schedule

drt run via cron or CI

Error notifications

on_error: skip + drt status

Old tool style

drt equivalent

Stored API key in UI

token_env: MY_TOKEN + export MY_TOKEN=...

OAuth app

Use token from OAuth flow → token_env

Service account JSON

Set GOOGLE_APPLICATION_CREDENTIALS for BigQuery source

Help the user migrate from an existing Reverse ETL tool (Census, Hightouch, Polytomic, or custom scripts) to drt.

Steps

Ask the user to share their existing sync configuration (screenshot, YAML, JSON, or description).
Map their existing config to drt equivalents using the table below.
Generate a valid syncs/<name>.yml for each sync.
Note any features that need manual setup (auth env vars, profiles.yml).

Concept Mapping

Census / Hightouch → drt

Census / Hightouch concept	drt equivalent
Source (BigQuery model)	`model: ref('table')` or raw SQL
Destination connection	`destination.type` + auth config
Sync behavior: Full	`sync.mode: full`
Sync behavior: Append	`sync.mode: incremental` + `cursor_field`
Field mappings	`body_template` / `properties_template` (Jinja2)
Run schedule	`drt run` via cron or CI
Error notifications	`on_error: skip` + `drt status`

Auth migration

Old tool style	drt equivalent
Stored API key in UI	`token_env: MY_TOKEN` + `export MY_TOKEN=...`
OAuth app	Use token from OAuth flow → `token_env`
Service account JSON	Set `GOOGLE_APPLICATION_CREDENTIALS` for BigQuery source

Output Format

For each sync, output:

# syncs/<name>.yml
name: <name>
description: "Migrated from <tool>"
model: ref('<table>')   # or raw SQL

destination:
  type: <type>
  # ... fields

sync:
  mode: full   # or incremental
  # ...

Then summarize:

What manual steps are needed (env vars, ~/.drt/profiles.yml)
Any features the old tool had that drt doesn't support yet (flag these clearly)

Reference

See docs/llm/API_REFERENCE.md for all destination types and fields.