DatriseAI-first ETL

Lokalise to Microsoft SQL Server Integration

AI-first ETL from Lokalise into Microsoft SQL Server. Governed entities, incremental sync, typed landing tables.

How Datrise loads Lokalise into Microsoft SQL Server

Datrise syncs Lokalise's projects, keys, translations, languages, contributors, and translation statuses into Microsoft SQL Server as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses a watermark on updated-at, applied with a MERGE statement, so re-runs update only what changed. Optional partitioned tables on a date partition function. SQL Server defaults to a case-insensitive collation, so Datrise preserves original casing in a metadata column to avoid silent key collisions.

Ideal for Microsoft-stack analytics and Power BI Import models.

Endpoints

Lokalise: Translation management for product strings.

Microsoft SQL Server: Microsoft relational DB with enterprise features.

How Lokalise entities map to Microsoft SQL Server

Lokalise entityMicrosoft SQL Server objectNotes
projectslokalise_projectsid PK · custom fields → NVARCHAR(MAX) JSON columns
keyslokalise_keysid PK · linked to lokalise_projects
translationslokalise_translationsid PK · linked to lokalise_projects
languageslokalise_languagesid PK · linked to lokalise_projects

FAQ

How does Datrise handle Lokalise's custom fields in Microsoft SQL Server?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Microsoft SQL Server types.

How does the Lokalise to Microsoft SQL Server sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with a MERGE statement.

Related pipelines

Early access

Connect Lokalise to Microsoft SQL Server 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.