Pre-built duck creek data migration for Policy, Billing and Claims financial events. OnDemand REST APIs + Platform DCSB/SQL. Insurance-finance translation rules for unearned premium, reserves, IBNR, salvage, subrogation, reinsurance. FBDI AR/AP/GL output. Statutory-grade reconciliation.
The hard part isn't pulling JSON from a REST API. It's translating Duck Creek's insurance-core data model into Fusion's AR, AP and GL model without breaking statutory accounting or reinsurance audit trails.
Duck Creek Technologies, acquired by Vista Equity Partners in 2023, presents a P&C-native data model built around Policy (with terms, transactions and transaction details), Account (the billing aggregator across policies for a single billed party), Claim (with features for each coverage involved in a loss), Reserve (case and IBNR per claim feature), and Treaty (with proportional, excess-of-loss and facultative configurations driving cession calculations). Oracle Fusion has a completely different shape — AR Invoices tied to Customer Accounts and Receivables Distributions, AP Invoices tied to Suppliers and Payables Distributions, GL Journals with full COA-segment coding.
Every duck creek data migration to Oracle Fusion has to bridge those gaps while preserving the insurance-finance integrity that NAIC, state regulators, external auditors and the carrier's own actuarial team depend on. Custom REST clients and one-off SQL can do part of the job — but every domain (policy, billing, claims, reserves, treaties) becomes a multi-month negotiation between IT, finance, actuarial, reinsurance and statutory reporting teams. Syntra ETL replaces that with pre-built insurance-finance translation logic refined across multiple P&C carrier integrations.
The same engine handles three deployment scenarios: OnDemand-only carriers (typically smaller or newer carriers on Duck Creek's strategic SaaS platform), Platform-only carriers (typically larger carriers with long-tenured Platform deployments not yet migrated to OnDemand), and hybrid carriers running both (typically mid-to-large carriers with OnDemand for new lines and Platform for primary books). The duck creek data migration produces one unified Fusion landing surface in all three cases.
The transformations Syntra ETL ships pre-built. No bespoke insurance-finance scaffolding, no multi-quarter custom conversion development.
Duck Creek policy transactions translated into Fusion GL postings with the right daily pro-rata or 24ths-method earning. Cancellation, endorsement and reinstatement reshape the curve correctly.
Case reserves and IBNR estimates posted to Fusion GL monthly with full claim-feature drill-back. Loss-adjustment-expense reserves handled separately per NAIC convention.
Treaty configuration translated to Fusion AR (recoverables) and AP (ceded premium) postings paired to originating policy or claim per the treaty's proportional or excess-of-loss rules.
Recoveries reverse the original loss postings when collected, with the reversal posted to the same claim feature in Fusion for clean net-loss reporting.
Duck Creek line-of-business and state codes mapped to Fusion COA segments to preserve NAIC Pages 14/15 reporting.
Postings tagged with both statutory accounting (SAP) and GAAP attributes where they diverge — for example deferred-acquisition-cost treatment — so both reporting bases run from one Fusion ledger.
A repeatable load order that respects Fusion's data dependencies. Skip a step and your AR or AP load fails on missing customer accounts, supplier records or COA segments.
Fusion enterprise structures, ledgers, BUs, COA segments tuned for line-of-business and state reporting, currencies, conversion rates, statutory accounting flexfields configured via FSM.
Customer accounts created in Fusion AR for each Duck Creek billed account, suppliers created in Fusion AP for each reinsurance treaty cedant and each claim payee, producer registry loaded, claim-adjuster registry loaded, treaty registry loaded with cession parameters.
Historical policy-transaction backbook loaded as Fusion AR invoices and GL postings. Earned-premium curve recomputed and validated against Duck Creek's source-of-truth per policy.
Historical claim payments loaded as Fusion AP invoices with claim-feature DFFs. Historical reserve journals loaded into Fusion GL. Reserve totals reconciled per claim per period against Duck Creek.
Historical ceded-premium AP entries and recoverables AR entries loaded per treaty per bordereau period. Schedule F reconstructed and reconciled against Duck Creek treaty ledger.
Final delta replay, parallel-month reconciliation, sign-off pack (NAIC Pages 14/15, Schedule F, AR/AP aging, reserve roll-forward — Duck Creek vs Fusion to the cent). Production cuts to Fusion; Duck Creek-to-Fusion event stream enters steady-state.
Every duck creek data migration load produces signed drill-downable reconciliation reports.
Source Duck Creek policy and claim transaction counts vs Fusion-loaded counts per line of business per state per period. Variance threshold zero.
Written, earned and unearned premium plus paid loss, paid LAE and case reserves reconciled per period per LOB. NAIC Pages 14/15 totals tied out.
Each policy transaction and claim event content-hashed at Duck Creek source and re-hashed post-Fusion-load. Hash drift indicates transformation bug or corruption — surfaced row-level.
Beginning-of-period reserves + new claims + adverse development - paid losses - favorable development = end-of-period reserves. Reconciled per claim feature per period.
Reinsurance ceded balances per treaty per bordereau reconciled between Duck Creek treaty ledger and Fusion AR/AP. Recoverable aging tied out per cedant.
Annual Statement Pages 14/15, Schedule F, Schedule P (loss development) reconstructed against Fusion-loaded data and compared to Duck Creek-originated versions. External auditor sign-off ready.
Duck creek data migration is the process of extracting policy financial events (bind, endorsement, cancellation, renewal), billing transactions (premium-due, payment-receipt, write-off, agency commission), claim financial events (indemnity payment, LAE payment, case-reserve adjustment, salvage, subrogation), reserve valuations (case reserves, IBNR, unearned premium), and reinsurance cession entries from a Duck Creek Policy, Billing and Claims system — across either OnDemand SaaS or Platform deployments — into Oracle Fusion Receivables, Payables and GL with full insurance audit context preserved. The technical heart is two-fold: structured event extraction via the Duck Creek Insights API (OnDemand) or Duck Creek Service Bus and SQL replicas (Platform), plus insurance-finance translation rules that turn policy and claim events into NAIC-compatible Fusion postings. Syntra ETL handles both with pre-built extractors, governed crosswalks for line-of-business and state codes to Fusion COA segments, and Oracle-validated FBDI Receivables, Payables and GL Journal output.
Typical ERP data conversion moves a master record (customer, vendor, item) and a transaction history (invoice, payment, journal) one-for-one between two ERPs. Duck creek data migration is fundamentally different because the source is an insurance core system, not an ERP. The data shapes are policy transactions, claim features, reserves, treaties and bordereau — none of which Fusion has a native concept of. The duck creek data migration project is therefore a translation project as much as it is a movement project: every Duck Creek event has to be classified by its insurance-finance meaning, mapped to one or more Fusion postings, and validated against statutory accounting principles (SAP) as well as GAAP. Syntra ETL's insurance-finance translation engine handles this transformation as pre-built logic refined across multiple P&C carrier integrations.
Many carriers run both Duck Creek OnDemand and Duck Creek Platform simultaneously — OnDemand for new lines of business or recent acquisitions, Platform for primary legacy books. The duck creek data migration extractors handle both: OnDemand through the REST API surface (Policy API, Billing API, Claims API, Insights API) with OAuth2 client credentials and event-stream subscriptions; Platform through DCSB (Duck Creek Service Bus) for event-based capture plus direct SQL Server or Oracle DB read replicas for bulk historical extracts. The financial events from both deployments are normalized to one canonical event schema in the staging layer before transformation, so Fusion sees one consistent stream regardless of which Duck Creek deployment originated each event. NAIC reporting from Fusion combines events across deployments per the carrier's preferred segment structure.
Yes. Duck Creek's line-of-business taxonomy (auto, property, GL, workers' comp, specialty, E&S, etc.) and state ratebook codes are the dimensions on which NAIC Annual Statement Pages 14 and 15 are filed — and the dimensions on which most P&C carriers manage their book of business. The duck creek data migration crosswalk maps these into Fusion COA segments — typically into a dedicated 'product line' segment plus the natural 'cost center' or 'business unit' segment, with state captured separately to support multi-state filings. Producer codes, agency hierarchy and reinsurance treaty registry are similarly mapped into Fusion supplier, customer and project structures. The crosswalk is signed off by the controller, the actuarial lead and the statutory reporting lead before any production load runs.
Fusion-native load formats for every Duck Creek data domain: FBDI AutoInvoice for premium-due transactions to Fusion AR; FBDI Receivables Receipt API for cash receipts; FBDI AP Invoice Import for claim indemnity, LAE and reinsurance ceded-premium AP entries; FBDI GL Journal Import for monthly case-reserve, IBNR, unearned-premium and loss-ceded journals; HDL bundles for any HCM context related to claim adjusters or producers managed in Fusion HCM; REST API payloads for incremental delta loads during parallel-run and post-cutover steady-state operation. Every payload validates against the current Oracle Fusion 26x release schema before submission. Receipt-image-equivalent claim documentation (loss reports, police reports, medical records redacted) is bound via FBDI attachment metadata to the corresponding AP invoice.
Every policy transaction extracted from Duck Creek is hashed at the source (policy ID + transaction effective date + transaction type + premium amount + commission amount). Every claim financial event is similarly hashed (claim ID + feature ID + transaction date + amount + transaction type). Post-load into Fusion, the corresponding AR/AP/GL postings are re-hashed and matched back to source. Counts (policy transactions, claim payments, reserve adjustments), sums (written premium, earned premium, paid claims, paid LAE, ceded premium, recoverables) and hash signatures are reconciled per line of business per state per period. Variances surface row-by-row with the exact field-level reason. Output is a signed timestamped reconciliation pack: Duck Creek policy and claim ledger vs Fusion AR/AP/GL to the cent, NAIC Pages 14/15 totals reconciled, Schedule F treaty balances reconciled. Statutory accountants sign off on the pack directly.
Yes — and this is the standard pattern. After the initial historical bulk load, Syntra ETL captures Duck Creek deltas through the Insights API event stream (OnDemand) or DCSB subscription (Platform) and replays them into both Fusion (the new target) and the legacy finance system (the parallel-run incumbent) for 1–2 month-end cycles. Statutory close runs in both. Reconciliation runs both ways — Duck Creek vs Fusion, and Duck Creek vs legacy. Variances are investigated before sign-off. Once the controller, actuarial lead, statutory reporting lead and external auditors are satisfied, the legacy finance system is frozen, future events flow only to Fusion, and the duck creek data migration enters steady-state operation. Reinsurance treaty reporting is the most sensitive area — typically 2–3 bordereau cycles run in parallel before cession is cut over.
P&C insurance carriers are subject to multiple overlapping audit regimes: SOX for publicly traded carriers (7-year retention with auditable trace from GL entry to source transaction), NAIC statutory accounting (SAP) audited annually by state insurance regulators, GAAP for SEC filings, reinsurance treaty audits (typically every 2–3 years per major treaty), tax audits on premium and loss reserves. Syntra ETL's duck creek data migration preserves the full chain: GL line in Fusion → AR or AP invoice → originating Duck Creek policy or claim transaction → originating UW or claims-handler action — with every hop signed and timestamped. Read-access logs capture every retrieval. Statutory accountants and external auditors get the reconciliation evidence they need without reconstruction work.
30-minute call with our P&C insurance-finance integration team. Walk through your Duck Creek deployment, line-of-business footprint, reinsurance program and the legacy finance system being retired — leave with a concrete duck creek data migration plan.