Real-time
Two-way sync
Changes in Pigment or SQL Server instantly reflect in both systems. No stale data, no manual imports.
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
- 01 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- 02 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- 03 Expose SaaS records as SQL Server tables that existing SSRS reports and internal apps can query
- 04 Mirror on-premises ERP data held in SQL Server into cloud CRM and support systems
Common sync patterns
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 | How this pairing syncs | |
|---|---|---|---|
| Tables Row-based transactional data loaded into models from source systems | Tables The primary sync target; rows map to records in connected systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Applications Planning models organized by domain such as finance, sales, or workforce | Databases Instance-level databases that scope a sync's reads and writes. | Applications is specific to Pigment and Databases to SQL Server — each maps to any object or custom field on the other side. | |
| Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Schemas Namespaces (dbo and custom) used to organize synced tables. | Metrics is specific to Pigment and Schemas to SQL Server — each maps to any object or custom field on the other side. | |
| Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Views Read-side projections used as outbound sync sources. | Dimension lists is specific to Pigment and Views to SQL Server — each maps to any object or custom field on the other side. | |
| Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Columns Field-level mapping targets with T-SQL types. | Scenarios is specific to Pigment and Columns to SQL Server — each maps to any object or custom field on the other side. | |
| Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | Data imports is specific to Pigment and Primary and Unique Keys to SQL Server — each maps to any object or custom field on the other side. |
How changes propagate between Pigment and SQL Server
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Pigment SQL Server Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is applied to SQL Server as a row-level write, with types converted between the two schemas.
SQL Server Pigment Sub-second propagation
DetectionChanges in SQL Server are captured at the source via change data capture — no polling loop against its API. SQL Server Native Change Data Capture (CDC).
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Pigment: Subject to the platform's API rate limits.
- SQL Server: No API rate limits; throughput depends on instance resources, licensing tier, and connection limits.
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.
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
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.
- 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.
Pigment
connected
SQL Server
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 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.
objects · Pigment ⇄ SQL ServerCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Pigment SQL ServerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Pigment and SQL Server integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Pigment and SQL Server: authenticate both systems, choose the objects to sync (such as Pigment's Tables and Applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Pigment side: Data imports, Users and permissions, Applications, Metrics, plus custom fields where Pigment exposes them. On the SQL Server side: Views, Columns, Primary and Unique Keys, CDC Change Tables. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Pigment and SQL Server: Internal tools without API plumbing; Write back safely; React to financial events. Build dashboards and back-office tools directly on SQL Server; Stacksync handles the API calls, rate limits, and retries against Pigment.
-
Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. SQL Server: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Scenario versioning (budget versus forecast versus actuals) is native to the model, so exports need a scenario context to be meaningful. SQL Server: Native Change Data Capture reads inserts, updates, and deletes from the transaction log into change tables without touching application code. Stacksync's field mapping accounts for these differences between Pigment and SQL Server without custom code.
SECURITY
Security teams trust 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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 444 integrations available for Pigment and SQL Server.
Popular · 5 of 444
No integrations match .
