Skip to content
CRM ⇄ Database

Close to SAP Hana integration — real-time, two-way sync

Keep Close and SAP Hana 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 Close and SAP Hana

Treat Close like part of your database: its records live in SAP Hana as real tables, and writes in either place sync to the other in seconds.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in SAP Hana, where it can be queried and joined like everything else.

Stacksync mirrors Custom Activities, Custom Fields, Users, Smart Views from Close into Sequences, Triggers, System-versioned temporal tables, System views (SYS schema) in SAP Hana with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Close with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.

Common use cases

  • 01 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
  • 02 Push call, SMS, and email activity data into a warehouse for rep performance and outreach-cadence analysis.
  • 03 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.
  • 04 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.

Common sync patterns

Product events onto CRM records

Signup, usage, or lifecycle changes written to SAP Hana sync onto the matching records in Close, giving go-to-market teams live product context.

Internal tools without API code

Back-office apps read and write the synced tables; Stacksync handles the Close API, limits, and retries.

Trigger workflows from CRM changes

Field and stage updates in Close arrive as row changes in SAP Hana, ready to drive jobs and notifications.

What you can sync between Close and SAP Hana

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.

Close objects SAP Hana objects How this pairing syncs
Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. Activities is specific to Close and Triggers to SAP Hana — each maps to any object or custom field on the other side.
Tasks Follow-up items assigned to users; synced for workload and SLA reporting. System-versioned temporal tables Column store tables with a history table tracking each row's validity period; used to reconstruct update and delete history for change capture. Tasks is specific to Close and System-versioned temporal tables to SAP Hana — each maps to any object or custom field on the other side.
Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. System views (SYS schema) Catalog and monitoring views such as SYS.TABLES and TABLE_COLUMNS; read to discover schema and auto-generate field mappings for new tables. Custom Activities is specific to Close and System views (SYS schema) to SAP Hana — each maps to any object or custom field on the other side.
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Column store tables HANA's default table type, optimized for analytics; synced two-way as rows over the SQL interface with the primary key driving upserts and delete tracking. Custom Fields is specific to Close and Column store tables to SAP Hana — each maps to any object or custom field on the other side.
Users Sales reps referenced as owners on leads, opportunities, and activities. Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. Users is specific to Close and Row store tables to SAP Hana — each maps to any object or custom field on the other side.
Smart Views Saved lead searches that can scope which records a segment-based sync pulls. Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. Smart Views is specific to Close and Calculation views to SAP Hana — each maps to any object or custom field on the other side.

How changes propagate between Close and SAP Hana

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.

Close SAP Hana Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.

SAP Hana Close Sub-second propagation

DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.

DeliveryEach detected change is written to Close through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Close: Subject to per-endpoint rate limits communicated in response headers.
  • SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
What ships with Close ⇄ SAP Hana

Connect Close and SAP Hana for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–SAP Hana connection.

Real-time

Two-way sync

Changes in Close or SAP Hana instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Close or SAP Hana 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 Close or SAP Hana record.

Observability

Monitoring

Track your Close ⇄ SAP Hana sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Close and SAP Hana.

How the Close and SAP Hana connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

SAP Hana

Integration surface
SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
Authentication
Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
Change detection
Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
Capabilities
read · write · CDC
Rate limits
No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
How it works

How to connect Close to SAP Hana — 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 Close and SAP Hana 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
    Close connected
    SAP Hana connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Close and SAP Hana 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 · Close ⇄ SAP Hana
    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
    Close SAP Hana
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Close and SAP Hana integration FAQ

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.

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 563 integrations available for Close and SAP Hana.

Popular · 8 of 563
All Close integrations All SAP Hana 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