A signed duck creek migration assessment in 2–4 weeks. OnDemand and Platform inventoried. Lines of business, states, treaties, NAIC obligations mapped. Risk register with mitigations. Fusion COA proposal. Cutover sequence. Fixed-scope delivery plan signed by CFO, controller and chief actuary.
P&C insurance-finance integration projects fail at a notorious rate. The single biggest failure mode is starting the build before discovery is signed off. A duck creek migration assessment eliminates that failure mode.
Duck Creek estates are messier than they look. A typical mid-market P&C carrier runs Duck Creek Platform for primary legacy personal-lines books, Duck Creek OnDemand for a recently launched commercial line, separate Manuscripts product configurations across business units inherited from a 2018 acquisition, and dozens of state ratebooks with material per-state variance in rating algorithms and surcharge handling. On top of that sits a reinsurance program with two quota share treaties, one per-risk excess-of-loss, one catastrophe excess and a handful of facultative placements — each documented inconsistently between the legal contract, the treaty registry in Duck Creek and the actuarial reserve model. A duck creek migration assessment surfaces all of this in 2–4 weeks of structured discovery before any integration build starts.
The cost of skipping discovery is well documented in the P&C insurance industry. Carriers that launch Fusion integration projects on the strength of a one-week internal scoping exercise typically blow through their original budget by 60–120% and miss their original go-live by 4–9 months. The largest losses come from late discovery — finding out in week 18 that the commercial line uses a different premium-earning method than personal lines, or that Schedule F lineage depends on a treaty bordereau process that has never been documented, or that two business units have divergent state surplus-lines workflows that need rationalization before Fusion can take them on. The duck creek migration assessment finds these risks in weeks 1–4 when they are cheap to fix, not in weeks 18–22 when they require schedule slippage and budget supplements.
Syntra ETL's duck creek migration assessment is a fixed-fee structured engagement delivered by a team that includes a P&C insurance-finance integration lead, a Fusion data architect and a statutory reporting consultant. The deliverable is a signed 40–80 page assessment plus executive deck plus risk register plus Fusion COA proposal plus phased delivery plan with fixed-fee follow-on integration. Most carriers complete the assessment and start the integration build in the same quarter.
Every dimension of the Duck Creek estate that affects scope, timeline, budget and risk.
OnDemand tenants, Platform versions, Manuscripts product configurations, Author content branches, hybrid deployment topology, planned OnDemand migration timeline.
Premium volume per line of business per state per year over the planned migration period. NAIC Pages 14/15 dimensional structure mapped to proposed Fusion COA.
Every Policy, Billing, Claims, Reserve, Treaty and master record that will move. Volume estimate, complexity rating, mapping risk per domain.
Every system upstream and downstream of Duck Creek touching financial data — agency portals, FNOL portals, GL feeds, treasury feeds, statutory reporting, BI tools.
NAIC Annual Statement, Schedule F, Schedule P, state premium tax, surplus lines, municipal premium tax, self-procurement, SOC 1 — every filing inventoried with lineage.
Named risks with named owners, mitigation steps, mitigation dates, escalation triggers. Updated through the integration project as risks close out.
A repeatable 2–4 week structured engagement, sized to your Duck Creek complexity.
Stakeholder kickoff with sponsors and steering. Duck Creek deployment landscape mapped — OnDemand tenants, Platform versions, Manuscripts product configurations, Author content branches, planned OnDemand migration roadmap. Initial integration inventory drafted.
Five-year premium-by-LOB-by-state extract pulled from Duck Creek Insights. NAIC Pages 14/15 dimensional structure mapped to proposed Fusion COA segments. Multi-state ratebook variance documented per LOB.
Treaty registry walkthrough with chief reinsurance officer. Proportional, excess-of-loss and facultative cession patterns documented. Bordereau process documented. Schedule F lineage mapped end-to-end.
Every system touching Duck Creek financial data inventoried — agency portals, FNOL portals, GL feeds, treasury, BI, statutory reporting. Every active regulatory filing inventoried with current data lineage.
Discovered risks consolidated into a structured register. Mitigation workshop with steering. Named owners, mitigation steps and dates assigned. Escalation triggers documented.
Final deliverable produced — assessment document, exec deck, risk register, Fusion COA proposal, phased delivery plan with fixed-fee follow-on integration. CFO, controller, CIO, chief actuary and chief reinsurance officer sign off.
The recurring patterns we find across P&C carrier Duck Creek estates.
Multiple Manuscripts product configurations across business units producing different financial-event shapes. Mitigation: per-product crosswalk track with separate sign-off owners.
Legal contract, Duck Creek treaty registry and actuarial reserve model disagreeing on cession terms. Mitigation: pre-build treaty reconciliation workshop with broker and chief actuary.
State surplus-lines and self-procurement filings on manual workarounds. Mitigation: rationalization workstream parallel to integration build, scoped in the assessment.
Tiered, override and contingent commission structures not fitting Fusion AR commission flows. Mitigation: dedicated commission-translation layer with controller sign-off.
Salvage and subrogation handling varying by LOB and state. Mitigation: per-LOB-per-state mapping rules built into the insurance-finance translation engine.
Duck Creek Platform-to-OnDemand transition timing affecting integration assumptions. Mitigation: scenario contingency in the phased delivery plan covering accelerated OnDemand migration.
A duck creek migration assessment is a structured 2–4 week discovery engagement that inventories every Duck Creek-originated financial event, dependency, integration and regulatory obligation that will be in scope when the carrier modernizes the finance back-end to Oracle Fusion. The Duck Creek estate is rarely simple — most carriers run a mix of Duck Creek OnDemand (the SaaS platform), Duck Creek Platform (the licensed on-prem deployment), multiple Manuscripts product configurations across personal and commercial lines, dozens of state ratebooks, and a treaty registry covering proportional, excess-of-loss and facultative reinsurance. A duck creek migration assessment surfaces all of this in one signed document — what Duck Creek deployment(s) are in play, which lines of business and states feed Fusion, what reinsurance cession volume crosses the boundary, what NAIC and state DOI reporting will continue to operate from Fusion, and what the realistic timeline and budget are. Without a duck creek migration assessment, the project enters scope creep in week six and exits over-budget.
A typical duck creek migration assessment runs 2–4 weeks. Two weeks is realistic for a single-deployment carrier (OnDemand-only or Platform-only) operating in 1–5 states with a single primary line of business. Four weeks is realistic for a hybrid carrier (OnDemand + Platform) operating in 40+ states with multi-line P&C books, MGA delegated authority, fronting arrangements, and a complex reinsurance program with both quota share and excess-of-loss treaties. Output is a signed assessment deliverable: deployment inventory, data-domain inventory, integration inventory (everything calling Duck Creek today — billing portals, agency portals, claims FNOL, GL feeds, treasury feeds, statutory reporting), regulatory inventory (NAIC Annual Statement, Schedule F, state-by-state premium tax, surplus lines), risk register with mitigations, recommended Fusion COA structure, recommended cutover sequencing and a phased delivery plan with timeline and budget.
A signed 40–80 page deliverable plus an executive summary deck plus a populated risk register plus a Fusion COA design proposal. Sections: (1) Duck Creek deployment landscape — OnDemand tenants, Platform versions, Manuscripts product configurations, Author content branches; (2) Line-of-business and state footprint — premium volume per LOB per state per year over the planned migration period; (3) Data-domain inventory — every Policy, Billing, Claims, Reserve, Treaty and master record that will move; (4) Integration inventory — every system upstream and downstream of Duck Creek that touches financial data; (5) Regulatory inventory — NAIC Annual Statement Pages 14/15, Schedule F, Schedule P, state premium tax, surplus lines, SOC 1; (6) Risk register with named mitigations; (7) Fusion COA design proposal; (8) Cutover sequencing plan; (9) Phased delivery plan with timeline, budget and resource plan; (10) Assumptions, exclusions, decisions log. Sign-off comes from CFO, controller, CIO, chief actuary and chief reinsurance officer.
Sponsors: CFO and CIO. Steering: controller, chief actuary, chief reinsurance officer, head of statutory reporting, head of internal audit. Working team from the carrier: Duck Creek platform lead, Duck Creek admin (Author / Manuscripts), Duck Creek Insights / reporting lead, billing operations lead, claims operations lead, treasury / cash-management lead, IT integration architect, infosec lead. Working team from Syntra ETL: solution architect, P&C insurance-finance integration lead, Fusion data architect, statutory reporting consultant. Optional but useful: external auditor (audit partner from your statutory audit firm), reinsurance broker (especially if you have complex treaty terms), state DOI relationship lead (if your statutory filings have any sensitive interactions). The duck creek migration assessment is light on hands-on technical work and heavy on cross-functional alignment — get the right people in the room and the project's scope, budget and timeline lock in by the end.
Yes — and it has to, because most carriers run both. Duck Creek OnDemand is Duck Creek's strategic SaaS platform that carriers are progressively moving onto, typically starting with new lines of business or recently acquired books. Duck Creek Platform is the licensed on-prem or private-cloud deployment that primary legacy books frequently remain on for years after a carrier adopts OnDemand. The duck creek migration assessment treats both deployments as in-scope: OnDemand REST API surface (Policy/Billing/Claims/Insights), Platform DCSB and SQL replica surface, OAuth2 vs DCSB auth, Manuscripts product configurations on Platform, Author content on OnDemand, Insights tenant configuration. The deliverable shows how financial events from both deployments will be normalized to one canonical event schema before reaching Fusion, so reporting consistency holds regardless of which deployment originated each event.
Yes — extensively. P&C carriers are subject to a stack of statutory reporting obligations that have to keep functioning after Fusion goes live: NAIC Annual Statement (Pages 14/15 for premium and loss by state and line, Schedule F for reinsurance ceded, Schedule P for loss development triangles, Schedule T for state premium volume), state-by-state premium tax filings (PT-1 and equivalents), surplus lines filings (in states where the carrier operates as a non-admitted insurer), municipal premium tax filings (in states like Kentucky and West Virginia where municipalities also tax premium), Self-Procurement Tax filings (for direct-procurement business). The duck creek migration assessment inventories every active filing, the data lineage feeding each filing today, and how that lineage will reconstitute through Fusion plus the integration layer post-cutover. Statutory accountants sign off on the lineage map before the project moves to crosswalk design.
Common risks: (1) Manuscripts product configurations diverging across business units, creating different financial-event shapes that need separate crosswalks; (2) Reinsurance treaty terms documented inconsistently between the legal contract, the Duck Creek treaty registry and the actuarial reserve model — needing a reconciliation before cession can be mapped to Fusion; (3) Salvage and subrogation handling that varies by line of business and state — needing per-LOB-per-state mapping rules; (4) State surplus-lines and self-procurement filings that have been on a manual reporting workaround for years — needing rationalization before Fusion can take them on; (5) Producer commission structures with complex tiered, overrides and contingent commissions that don't fit cleanly into Fusion AR commission flows; (6) Vista Equity ownership uncertainty driving Duck Creek roadmap questions — the assessment recommends contingency for major Platform-to-OnDemand transitions that may be on the carrier's near-term horizon. Each risk gets a named owner and mitigation date in the register.
A typical duck creek migration assessment is a fixed-fee engagement priced based on Duck Creek estate complexity — single-deployment small-state carriers fall at the low end of the band, hybrid multi-state multi-line carriers with complex reinsurance fall at the high end. The assessment pays back in two clear ways: (1) project cost certainty — the downstream Fusion integration project is delivered against a fixed scope, fixed timeline and fixed budget signed off during the assessment, eliminating the consulting-firm overrun pattern that plagues 70%+ of large insurance-finance integrations; (2) execution speed — discovery is already done when the integration project starts, so weeks 1–6 of the integration project are crosswalk and translation-rule design rather than another round of discovery. Carriers consistently report that the duck creek migration assessment shortens total project elapsed time by 8–14 weeks versus consultant-led discovery-as-you-go approaches.
30-minute scoping call with our P&C insurance-finance integration team. We'll size your Duck Creek estate (OnDemand, Platform or both), your line and state footprint, your reinsurance program and your Fusion target architecture — and give you a fixed-fee assessment proposal before the call ends.