Skip to content
Accounting and finance ⇄ Database

Pigment to SQL Server integration — real-time, two-way sync

Keep Pigment and SQL Server in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Pigment and SQL Server

Work with Pigment's financial data straight from SQL Server: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Data imports, Users and permissions, Applications, Metrics from Pigment into Views, Columns, Primary and Unique Keys, CDC Change Tables in SQL Server and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against SQL Server, and rows your code writes or updates flow back into Pigment with validation, so the finance system stays the system of record.

Common use cases

  • Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
  • Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • Expose SaaS records as SQL Server tables that existing SSRS reports and internal apps can query
  • Mirror on-premises ERP data held in SQL Server into cloud CRM and support systems

Internal tools without API plumbing

Build dashboards and back-office tools directly on SQL Server; Stacksync handles the API calls, rate limits, and retries against Pigment.

Write back safely

Updates written to the synced tables in SQL Server propagate into Pigment, so automations can create or correct finance records without custom integration code.

React to financial events

Changes in Pigment appear in SQL Server as row changes, so you can trigger downstream logic with the database tooling you already use.

What you can sync between Pigment and SQL Server

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Pigment objects SQL Server objects
Applications Planning models organized by domain such as finance, sales, or workforce Views Read-side projections used as outbound sync sources.
Metrics Multidimensional values holding plans and actuals; the main target for inbound data Columns Field-level mapping targets with T-SQL types.
Dimension lists Master data like accounts, products, or employees that metrics are sliced by Primary and Unique Keys Match keys for idempotent upserts and conflict handling.
Tables Row-based transactional data loaded into models from source systems CDC Change Tables System-populated tables holding captured inserts, updates, and deletes for consumers.
Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Stored Procedures T-SQL logic that can validate or post-process synced rows.
Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Databases Instance-level databases that scope a sync's reads and writes.
What ships with Pigment ⇄ SQL Server

Connect Pigment and SQL Server for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Pigment–SQL Server connection.

Real-time

Two-way sync

Changes in Pigment or SQL Server instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Pigment or SQL Server data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Pigment or SQL Server record.

Observability

Monitoring

Track your Pigment ⇄ SQL Server sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Pigment and SQL Server.

How the Pigment and SQL Server connectors work

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits

SQL Server

Integration surface
SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers
Authentication
Database credentials entered as a connection string or as parameters (host/user/password) in the Create New Sync page
Change detection
SQL Server Native Change Data Capture (CDC); a DBA runs a one-time setup script with sysadmin privileges to enable CDC and create Stacksync wrapper procedures
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput depends on instance resources, licensing tier, and connection limits
SQL Server setup guide
How it works

How to connect Pigment to SQL Server — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Pigment and SQL Server with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Pigment connected
    SQL Server connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Pigment and SQL Server objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Pigment ⇄ SQL Server
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Pigment SQL Server
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Pigment and SQL Server integration FAQ

SECURITY

Security teams love Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Pigment and SQL Server.

Popular · 8 of 386
All Pigment integrations All SQL Server integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own