Production-grade duck creek data extraction tool. OAuth2 governance for OnDemand REST APIs, DCSB and SQL read-replica integration for Platform, near-real-time event subscriptions, scheduled bulk extracts, Parquet/JSON/FBDI outputs. No bespoke integration scaffolding.
Hand-built integration to Duck Creek always starts cheap and ends expensive. OnDemand OAuth quirks, Platform DCSB schemas, SQL replica complexity and 10-year backbook volume break custom scripts one by one.
Duck Creek's OnDemand REST APIs are not difficult to call — but they are difficult to call correctly at scale. Each domain (Policy, Billing, Claims, Insights, Reinsurance) has its own pagination pattern, its own rate-limit behavior, its own OAuth2 scope, and its own quirks left over from the pre-Vista-Equity era when Duck Creek was a Trident Capital portfolio company. A custom script written for the Billing API breaks on Claims; the Claims script breaks again on Insights; the Insights script falls over the first time the rate limiter triggers 429 back-off.
Duck Creek Platform is even more complex. DCSB carries its own message schemas evolved across multiple major Platform releases. The underlying SQL Server / Oracle DB schema has hundreds of tables with naming conventions inherited from the original ClaimCenter and Underwriter products. A custom SQL extract that works for policy transactions breaks on claim feature data; the claim-feature extract breaks again on reserve adjustments; the reserves extract falls over when the carrier upgrades from Platform 8 to Platform 9. Custom integrations don't survive Platform upgrades.
Syntra ETL's duck creek data extraction tool ships pre-built support for every domain across both deployment modes — plus the undocumented quirks we've discovered across multiple carrier deployments. Backed by an SLA. Customers typically pay back the tool in week-three savings versus equivalent custom development, and the ongoing maintenance burden (chasing API deprecations, handling DCSB schema changes, surviving Platform upgrades) disappears entirely. Whether you need a one-shot bulk extract for Fusion migration, a scheduled hourly delta feeding your data warehouse, or a near-real-time event stream for treasury and reinsurance reporting — the same tool covers every case.
Every production domain across OnDemand and Platform, every payload type, every quirk handled.
Policy headers, terms, transactions, transaction details — pulled via OnDemand Policy API or Platform DCTPolicy tables. Modified-since watermark for delta extraction.
Premium-due, payment receipts, NSF, write-offs, commissions — pulled via OnDemand Billing API or Platform DCTBilling tables. Routed to Fusion AR FBDI or downstream warehouse.
Claims, claim features, indemnity payments, LAE payments, case reserves, salvage and subrogation — pulled via OnDemand Claims API or Platform DCTClaim tables.
Near-real-time event subscription for cash, bordereau, claim payment, large-loss notification. Drives treasury cash forecasting and reinsurance notification.
Treaty registry, cession calculations, bordereau periods, reinstatement premium, profit commission — for Schedule F reconciliation and reinsurance audit support.
Line-of-business codes, state ratebook configurations, producer registry, claim-adjuster registry, claim-status codes — feeds the migration discovery loop without manual export.
From OAuth2 or DCSB provisioning to first scheduled delta run, typically completes in 3–5 days.
For OnDemand: Duck Creek admin provisions a tenant-level OAuth2 client with read-only scope on the domains in your extraction plan. For Platform: DCSB subscription credentials issued and SQL read-replica access granted with read-only role. Credentials stored in your cloud KMS — Syntra never holds them in plaintext.
Extractor runtime deployed to your cloud environment (containerized, runs on Kubernetes, ECS, Cloud Run or bare VM). Output destination configured: S3 / GCS / Azure Blob for files, plus optional Fusion FBDI / HDL drop targets.
Per-domain extraction scope configured (which fiscal years, which lines of business, which states, which deployments — OnDemand, Platform or both). Schedule defined: one-shot bulk, hourly delta, daily snapshot, event-stream subscription, or any cron. Output format per domain set: Parquet / JSON / FBDI.
Initial full-snapshot extract runs across all configured domains in parallel. For 10-year multi-state backbook (5M policies, 8M claims, 60M events) the extract typically completes in 36–96 hours. Signed manifest produced with counts, sums and hashes per partition.
Scheduled delta or event-stream subscriptions execute. Run logs feed your SOC 2 audit trail. Failures surface as alerts via email, Slack, PagerDuty or webhook — no silent drift. Quarterly extractor updates roll in via the standard release channel.
The details that matter when the tool has to run unattended for years across Duck Creek upgrades.
Every extract is idempotent — re-running the same scope produces byte-identical output. Failed runs resume from the last checkpoint rather than starting over.
Respects OnDemand per-tenant REST API rate limits and Platform SQL replica connection limits. Automatic back-off and retry. Never disrupts live UW, billing or claims activity.
Every run produces a signed JSON manifest with record counts, sum totals, hash signatures and source-modified timestamps per partition — ready for downstream reconciliation.
Credentials encrypted at rest in cloud KMS. Parquet and JSON outputs encrypted at rest with KMS-managed keys. TLS 1.3 in transit.
Prometheus metrics for extraction throughput, error rates, API/SQL latencies, queue depth. Grafana dashboards shipped. Plug into your existing observability stack.
Every credential issuance, every API call, every SQL session, every output write logged with operator identity, timestamp, scope and result. Audit logs ship to SIEM via standard syslog or CloudTrail integration.
A duck creek data extraction tool is software that authenticates to a Duck Creek environment — either Duck Creek OnDemand (the SaaS deployment) or Duck Creek Platform (the licensed on-premises or private-cloud deployment) — and pulls policy financial events, billing transactions, claim financial events, reserve valuations and reinsurance cession data into a destination of your choice. For OnDemand, the tool calls the REST API surface (Policy API, Billing API, Claims API, Insights API) with OAuth2 client credentials and optionally subscribes to event streams for near-real-time capture. For Platform, the tool connects through DCSB (Duck Creek Service Bus) for event-based capture and to SQL Server or Oracle DB read replicas for bulk historical pulls. Syntra ETL's duck creek data extraction tool handles both deployment modes, normalizes the output to a canonical event schema, hash-signs every output for downstream reconciliation, and emits Parquet, JSON Lines or Fusion FBDI/HDL formats.
Custom integration to Duck Creek always starts cheap and ends expensive. The OnDemand REST APIs have evolving schemas, deprecated endpoints, pagination patterns that vary by domain, and OAuth2 quirks specific to the Vista Equity ownership era. The Platform DCSB has its own message schemas that have evolved across major Platform releases, plus the SQL Server / Oracle DB schema underneath has hundreds of tables with cryptic naming conventions inherited from the legacy ClaimCenter / Underwriter heritage. A custom integration that works for premium events falls over on claim payments; the claim-payment integration falls over again on reserves; the reserves integration falls over on reinsurance cession. Syntra ETL's duck creek data extraction tool ships pre-built support for every domain across both deployment modes — backed by an SLA. Customers typically pay back the tool in week-three savings versus equivalent custom development.
For OnDemand: Policy API (policy lifecycle, terms, transactions), Billing API (accounts, premium-due, payments, write-offs, commissions), Claims API (claims, features, payments, reserves, salvage, subrogation), Insights API (event streams for near-real-time capture), Producer API (agency hierarchy), Reinsurance API (treaty registry and cession transactions where exposed). For Platform: DCSB message subscriptions for the same event types, plus direct read access to the underlying SQL Server or Oracle DB schema for bulk historical extracts (the standard Platform schemas around DCTPolicy, DCTBilling, DCTClaim and their many transaction-detail tables). New API endpoints get folded in via quarterly extractor releases tracking Duck Creek's roadmap — you never have to chase a deprecation announcement alone.
Duck Creek OnDemand uses OAuth2 with client_credentials grant for company-level integration access. Syntra ETL ships a vetted OAuth client pattern: scoped client credentials provisioned with read-only access to the domains in your extraction plan, automatic token rotation before expiry, encrypted credential storage in your cloud KMS, SOC 2-compliant audit logging of every token issuance and API call. No admin password is ever stored. The OAuth scope can be reduced post-deployment without reinstalling. Carriers in regulated jurisdictions (US states with stringent data-handling rules, EU markets under GDPR, Canadian provinces under PIPEDA) routinely pass internal security review on the first attempt.
Yes. The tool includes a built-in scheduler with cron syntax and supports modified-since delta extraction on every domain that exposes a watermark (policy transactions, billing transactions, claim financial events, reserve adjustments, treaty bordereau periods). Common schedules: near-real-time event-stream subscription for cash and bordereau events, hourly delta extract for premium and claim activity feeding a downstream data warehouse, daily snapshot extract for the operational reporting tier, monthly bulk extract for reserve recomputation. Each scheduled run produces a signed manifest (counts, sums, hashes per partition) plus a run log captured for SOC 2 audit. Failures surface as alerts via email, Slack, PagerDuty or webhook — no silent drift.
Three primary formats. Parquet (columnar, partitioned by fiscal period, line of business and state, ideal for downstream analytics in Athena, BigQuery, Snowflake or Databricks). JSON Lines (newline-delimited JSON preserving the full Duck Creek API or DCSB response shape, ideal for streaming pipelines or downstream ETL). Fusion-native loaders (FBDI AutoInvoice for premium, FBDI Receivables Receipt for cash, FBDI AP Invoice Import for claim payments and reinsurance, FBDI GL Journal Import for reserves and unearned-premium, HDL bundles for any HCM context). Custom output formats are configurable per domain. The duck creek data extraction tool can feed multiple downstream destinations from one extract — for example Parquet to the data lake plus FBDI to Fusion simultaneously.
Large P&C carriers carry 10+ years of policy and claim history — frequently terabytes of transactional data across millions of policies and millions of claims. The duck creek data extraction tool uses parallel worker pools sized per the source deployment: for OnDemand, parallel REST workers respecting Duck Creek's per-tenant rate limits with automatic 429 back-off; for Platform, parallel SQL read sessions against the read replica plus parallel DCSB subscribers. Throughput in production: a typical 10-year multi-state personal-lines backbook (5M policies, 8M claims, 60M financial events) completes a full historical extract in 36–96 hours depending on Duck Creek deployment performance. Checkpoint-resume on failure means a single dropped connection doesn't restart the extract.
Yes. For OnDemand, the extractor authenticates with read-only OAuth2 scope and respects per-tenant REST API rate limits, so underwriters, billing analysts and claims adjusters see no performance impact. For Platform, the extractor reads from a SQL read replica (not the transactional primary) and subscribes to DCSB events without participating in transaction commit, so the production Platform instance is similarly insulated. Heavy historical extracts are scheduled for off-peak windows (typically overnight or weekends). No Duck Creek admin downtime is needed, no configuration changes are required to the active Duck Creek instance, and the extractor leaves no trace beyond the API request log or DCSB subscription audit. Carriers routinely run scheduled nightly extracts against live production Duck Creek for years without a single user complaint.
30-minute discovery call. We'll scope your Duck Creek deployment (OnDemand, Platform or both), data domains, historical backbook volume, OAuth2 / DCSB setup and downstream destination — and have a working extract running on your environment within a week.