Production-grade duck creek etl connector. OnDemand REST APIs + Platform DCSB/SQL. Fusion, Snowflake, Databricks, BigQuery, Power BI destinations. Insurance-finance translation logic built-in. Quarterly updates track Duck Creek roadmap. SOC 2, NAIC Cybersecurity Model Law, NYDFS, GDPR compliant.
Generic connectors expose tables and endpoints; insurance-finance integration needs semantic understanding. A purpose-built duck creek etl connector ships the semantics out-of-the-box.
A generic JDBC connector pointed at Duck Creek Platform's SQL Server schema gives you access to hundreds of cryptically named DCT-prefix tables — but it tells you nothing about which fields participate in premium-earning calculations, how case reserves relate to claim features through the claim-feature-coverage hierarchy, how the treaty registry interacts with policy and claim transactions to produce ceded-premium and loss-ceded entries, or how Schedule F lineage reconstitutes through the data model. The semantic gap is enormous. A team trying to integrate Duck Creek to Fusion through a generic JDBC connector spends 60–80% of project time on insurance-finance semantic discovery — finding out the hard way which DCT tables matter, which joins produce correct results, which fields are reliable vs which are vestigial from earlier Platform versions.
A generic REST connector pointed at the OnDemand API surface gives you authenticated access to JSON payloads — but it tells you nothing about which combinations of API responses participate in NAIC Pages 14/15 reporting, which Insights API events constitute the canonical financial-event stream, or how OAuth2 scope decisions affect what data is accessible. The semantic gap is identical. A team trying to integrate OnDemand to Fusion through a generic REST connector spends the same 60–80% of project time on semantic discovery — finding out the hard way which API combinations matter and which OAuth scopes are needed.
The Syntra ETL duck creek etl connector is purpose-built for Duck Creek. It knows the OnDemand REST API surface and the Platform DCSB/SQL surface. It knows the insurance-finance semantics — premium earning, reserve roll-forward, cession calculation, salvage and subrogation handling, NAIC reporting structure. It ships the insurance-finance translation logic that converts Duck Creek events into Fusion-ready AR/AP/GL postings or warehouse-ready dimensional fact tables. Months of custom integration development become weeks of configuration. Customers pay back the investment in week-three savings, and the ongoing maintenance burden (chasing API deprecations, handling DCSB schema changes, surviving Platform upgrades) disappears entirely.
The patterns that show up in every P&C insurance integration to Fusion or warehouse.
Bind, endorsement, cancellation, reinstatement, renewal — full transaction history per policy. Earned-premium curve computed per LOB per state.
Premium-due, payment receipts, NSF, write-offs, return premium, agency commissions — per account, per producer, per period.
Indemnity, LAE, case reserves, IBNR, salvage, subrogation — per claim per feature per accident period.
Treaty-driven cession calculations — proportional, excess-of-loss, facultative. Schedule F-ready posting structure.
Case reserve, IBNR, UPR, LAE reserve, DAC — period-end roll-forward calculations per actuarial convention.
LOB codes, state ratebook configurations, producer registry, treaty registry, claim-adjuster registry — exported as crosswalk inputs.
A repeatable installation pattern. From credentials provisioning to first scheduled extract typically completes in 3–5 business days.
OnDemand: Duck Creek admin provisions tenant-level OAuth2 client with read-only scope on extraction-plan domains. Platform: DCSB subscription credentials and SQL read-replica access issued. Credentials stored in carrier's cloud KMS.
Connector deployed to carrier's cloud environment (containerized on Kubernetes, ECS, Cloud Run or VM). Downstream destinations configured — Fusion FBDI/REST drop targets, warehouse credentials, S3/GCS/Azure Blob buckets, BI dataset endpoints.
Per-domain extraction scope configured (which fiscal years, which LOBs, which states, which deployments — OnDemand, Platform or both). Schedules defined (real-time event subscription, hourly delta, daily snapshot, monthly bulk). Output format per domain set per destination.
Initial full-snapshot extract runs across all configured domains in parallel. 10-year multi-state backbook (5M policies, 8M claims, 60M events) typically completes in 36–96 hours. Signed manifest produced with counts, sums, hashes per partition.
Scheduled delta or event-stream subscriptions execute. Run logs feed SOC 2 audit trail. Failures alert via email/Slack/PagerDuty/webhook — no silent drift. Quarterly connector updates roll in via standard release channel.
Connector updates absorb Duck Creek OnDemand API changes and Platform release upgrades. Insurance-finance translation rules updated for NAIC reporting changes. Downstream destination connectors tracked against target product releases.
The decisions that drove P&C carriers to choose pre-built over custom build.
3–5 days to first extract vs 3–6 months for custom integration build. Project kickoff to production use measured in weeks, not quarters.
Subscription pricing. Fixed-fee implementation. No surprise consulting overruns. Total cost typically below a single FTE Duck Creek integration engineer fully loaded.
Quarterly connector updates absorb Duck Creek API and Platform changes. Carrier IT doesn't chase deprecation announcements or rebuild after Platform upgrades.
Translation logic for earned premium, reserves, cession, salvage, commission — pre-built, refined across multiple P&C carrier deployments.
Carrier infosec teams pass internal security review on the first attempt. NAIC Cybersecurity Model Law, NYDFS, GDPR, PIPEDA compliance built-in.
Horizontal scaling. CAT-event volume absorbed automatically. New states, new LOBs, new acquisitions onboarded by configuration, not by code.
The duck creek etl connector is a pre-built, production-grade ETL component that handles the full extract-transform-load lifecycle for Duck Creek financial data into downstream destinations — most commonly Oracle Fusion AR/AP/GL, but also data warehouses (Snowflake, Databricks, BigQuery, Redshift), data lakes (S3/GCS/Azure Blob with Parquet partitioning), and BI/analytics tools (OTBI, Power BI, Tableau, Looker). Rather than building bespoke Duck Creek integration each time, the duck creek etl connector ships pre-built support for both OnDemand REST APIs (Policy/Billing/Claims/Insights) and Platform DCSB and SQL replica surfaces, plus the insurance-finance translation logic that converts Duck Creek's P&C-native data model into the target's expected shape. Backed by an SLA and quarterly releases tracking the Duck Creek roadmap, the duck creek etl connector replaces months of custom integration development with weeks of configuration.
Generic JDBC connectors expose tables; generic REST connectors expose endpoints. Neither understands Duck Creek's semantics. A generic JDBC connector against Duck Creek Platform's SQL Server schema would expose hundreds of cryptically named DCT-prefix tables with no context about which fields drive premium-earning calculations, how case reserves relate to claim features, or how treaty cession produces ceded-premium and loss-ceded entries. A generic REST connector against the OnDemand API would expose JSON payloads without telling you which fields participate in NAIC Pages 14/15 reporting or which combinations produce Schedule F treaty cession entries. The duck creek etl connector is purpose-built for Duck Creek — it knows the entity model, knows the financial semantics, knows the NAIC reporting requirements, and ships the insurance-finance translation logic that turns Duck Creek events into Fusion-ready AR/AP/GL or warehouse-ready dimensional fact tables. Customers pay back the investment in week-three savings versus equivalent custom integration.
Both OnDemand (the SaaS deployment, Duck Creek's strategic platform after the 2023 Vista Equity acquisition) and Platform (the licensed on-prem or private-cloud deployment that most large carriers still run for primary legacy books). For OnDemand: REST API connectivity to Policy API, Billing API, Claims API, Insights API, Producer API and Reinsurance API with OAuth2 client_credentials authentication; event-stream subscriptions for near-real-time capture; pagination handling, rate-limit back-off and OAuth token rotation built-in. For Platform: DCSB (Duck Creek Service Bus) message subscriptions for event-based capture; direct SQL Server or Oracle DB read-replica access for bulk historical extracts; understanding of the standard Platform schema (DCTPolicy, DCTBilling, DCTClaim and supporting transaction-detail tables). For hybrid carriers running both deployments simultaneously, the duck creek etl connector normalizes events from both into a single canonical event schema before downstream routing.
Oracle Fusion (FBDI AutoInvoice for AR, FBDI AP Invoice Import for AP, FBDI GL Journal Import for reserves and accruals, REST APIs for real-time AR receipts and AP invoice creation, HDL bundles for HCM context), Snowflake (direct connector with multi-cluster warehouse scaling), Databricks (Delta Lake table writes with partitioning), BigQuery (load jobs with partitioning by fiscal period and LOB), Amazon Redshift (COPY commands from S3 staging), Microsoft Fabric and Synapse (Synapse Link or copy activity), S3 / GCS / Azure Blob (Parquet partitioned by fiscal period, LOB, state — ideal for downstream Athena/BigQuery External/Synapse Serverless queries), Kafka and Event Hubs (event-stream routing for downstream microservices), OTBI/Power BI/Tableau/Looker (dataset extracts pre-shaped for insurance BI). One duck creek etl connector run can feed multiple destinations simultaneously.
Three to five business days from kickoff to first scheduled production extract. Day 1: credentials and surface provisioning — Duck Creek admin provisions OAuth2 client credentials for OnDemand or DCSB subscription credentials and SQL read-replica access for Platform; credentials stored in the carrier's cloud KMS. Day 1–2: connector runtime deployed to the carrier's cloud environment (containerized on Kubernetes, ECS, Cloud Run or VM); downstream destination configured. Day 2–3: per-domain scope and schedule configured — which fiscal years, which LOBs, which states; output format per domain (Parquet, FBDI, REST). Day 3–5: first bulk extract runs across configured domains; for a 10-year multi-state backbook (5M policies, 8M claims, 60M events) the extract typically completes in 36–96 hours. Day 5 onward: steady-state operation with scheduled delta or event-stream subscriptions.
The duck creek etl connector ships quarterly updates tracking Duck Creek's OnDemand API roadmap and Platform release roadmap. OnDemand API minor version bumps (typical quarterly cadence) are absorbed transparently — the canonical event schema stays stable, downstream destinations don't see the change. Platform release upgrades (typical 18–24 month cadence for major versions like Platform 8 to 9) are similarly absorbed through the canonical schema layer. Carriers running mid-transition from Platform to OnDemand (a 24–36 month transition for large carriers) get unified operation across both — the integration's per-event routing updates automatically as lines of business migrate, and the downstream destination sees one consistent stream throughout. Customers don't chase Duck Creek deprecation announcements; Syntra ETL ships extractor updates on schedule with documented changelogs.
Yes. SOC 2 Type II controls operate across the full connector platform. NAIC Cybersecurity Model Law compliance for carriers in NAIC-adopting states. State-specific data-handling requirements honored (New York DFS Cybersecurity Regulation, California Insurance Code data-protection rules, Massachusetts data-security requirements, etc.). GDPR compliance for carriers with EU exposure (UK personal lines, EU specialty, EU reinsurance), including DPA support, sub-processor disclosure and right-to-erasure handling for in-scope personal data. PIPEDA compliance for Canadian carriers. End-to-end encryption — TLS 1.3 in transit, KMS at rest for credentials and payloads. Comprehensive audit logging — every credential issuance, every API call, every SQL session, every output write logged to your SIEM via standard CloudTrail or syslog integration. Carriers' infosec teams routinely pass internal security review on the first attempt.
Tiered subscription pricing based on Duck Creek estate scale (deployment mode, number of tenants, LOB count, state count), event volume (typical mid-market carrier sees 20K events per business day; large national multi-line carrier sees 100K+ per day with CAT-event spikes to 500K+), and downstream destination count (Fusion-only carriers pay less than carriers feeding Fusion + warehouse + BI simultaneously). Implementation is typically a fixed-fee engagement priced based on Duck Creek estate complexity — single-deployment single-state carriers fall at the low end of the band, hybrid multi-state multi-line carriers with complex reinsurance fall at the high end. Total cost typically compares favorably to a single FTE Duck Creek integration engineer fully loaded — and the connector eliminates the staffing risk, knowledge-transfer risk and quality risk of in-house build. Carriers consistently report payback within the first 6–9 months.
30-minute discovery call. We'll scope your Duck Creek deployment (OnDemand, Platform or both), downstream destinations and use cases — and have the duck creek etl connector running on your environment within a week.