Visma e-conomic to MySQL Integration

How Datrise loads Visma e-conomic into MySQL

Datrise syncs Visma e-conomic's invoices, customers, suppliers, journal entries, accounts, and products 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

Visma e-conomic: Nordic accounting, invoicing, and ledger records.

MySQL: Widely used OSS relational engine (InnoDB).

How Visma e-conomic entities map to MySQL

Visma e-conomic entity	MySQL object	Notes
invoices	`visma_e_conomic_invoices`	id PK · custom fields → JSON columns
customers	`visma_e_conomic_customers`	id PK · linked to visma_e_conomic_invoices
suppliers	`visma_e_conomic_suppliers`	id PK · linked to visma_e_conomic_invoices
journal entries	`visma_e_conomic_journal_entries`	id PK · linked to visma_e_conomic_invoices

FAQ

How does Datrise handle Visma e-conomic'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 Visma e-conomic 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 Visma e-conomic 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.