Pre-built guidewire data migration for PolicyCenter, BillingCenter, ClaimCenter. Cloud Data Access (CDA), Cloud API and on-prem JDBC extractors. Premium/paid-loss/recovery crosswalks, reserves history preserved, FBDI emitters, row-level reconciliation. Audit-ready evidence at every load.
The hard part isn't pulling Parquet from CDA. It's translating Guidewire's policy/billing/claim data model into Fusion's GL/AP/AR shape without losing reserve history, reinsurance traceability or state-retention chain-of-custody.
Guidewire InsuranceSuite presents a tightly-coupled data model across three Centers. PolicyCenter holds policies, risks, coverages, endorsements, premium transactions and product configuration. BillingCenter holds bills, receipts, disbursements, commission statements and the full cash-application ledger. ClaimCenter holds claims, exposures, reserves (case + IBNR), indemnity payments, expense payments, recovery payments and SIU flags. Cross-Center foreign keys tie a policy in PolicyCenter to its bill in BillingCenter to its claim in ClaimCenter.
Oracle Fusion Financials uses a different shape — Subledger Accounting (SLA) rules that turn source transactions into GL journals; Payables with supplier-and-invoice-driven AP; Receivables with customer-and-receipt-driven AR; Revenue Recognition for earned-premium recognition; Cash Management for bank reconciliation. Every guidewire data migration to Oracle Fusion has to bridge those gaps without breaking the audit chain that links a Fusion journal line back to its originating PolicyCenter policy or ClaimCenter reserve change.
The same engine handles three deployment scenarios: full finance-integration cutover (premium + paid-loss + recovery + commission → Fusion), Center-by-Center rollout (BillingCenter cash first, then PolicyCenter premium, then ClaimCenter paid-loss), and the hybrid pattern where some lines of business have moved to Guidewire Cloud Platform (GWCP) while others remain on-prem awaiting decommissioning.
The transformations Syntra ETL ships pre-built. No custom CDA scaffolding, no multi-month bespoke conversion development.
PolicyCenter premium transactions converted to Fusion revenue journals — written premium to written-premium GL account, earned premium to earned-premium recognition schedule, unearned reserve to unearned-premium liability — per LOB and per legal entity.
ClaimCenter indemnity payments routed to Fusion paid-loss GL by coverage. Reserve changes (case + IBNR) carried as evidence metadata preserving the full actuarial loss-development triangle for Schedule P and statutory filings.
BillingCenter cash receipts to Fusion AR cash application. Commission disbursements to Fusion AP commission accounts. Claim payments to claimant suppliers in Fusion AP. Full premium-payment-disbursement audit trail preserved.
Ceded premium and ceded loss recoveries routed to Fusion ceded GL accounts with cross-references to source policies and claims. Bordereaux reconciliation supported for 30+ year reinsurance audit horizons.
Producers (agents/brokers) and claimants from BillingCenter and ClaimCenter synced to Fusion Suppliers with tax IDs, banking info and 1099 classification preserved — eliminating duplicate supplier master.
Every record tagged with state, line of business and retention-clock-start date so per-jurisdiction retention rules (NY 6yr, CA 5yr, TX 10yr, FL 5yr post-close) can be enforced independently in the archive.
A repeatable load order that respects Fusion's data dependencies. Skip a step and your premium-revenue load fails on missing legal entity or chart-of-account segments.
Fusion enterprise structures, ledgers (statutory + GAAP), legal entities per state of admission, BUs, COA segments, revenue recognition setup, AP/AR/Cash Management configured. Loaded via FSM tasks — not user-facing data, but everything downstream depends on it.
Producers and claimants as Fusion Suppliers (FBDI Supplier Import), policyholders as Fusion Customers (FBDI Customer Import), GL accounts per state and LOB per Schedule P line. Loaded in dependency order — suppliers before AP invoices, customers before AR receipts.
PolicyCenter premium transactions converted to Fusion revenue journals via FBDI Journal Import. Written/earned/unearned split applied per LOB. Reconciled against PolicyCenter premium ledger to the cent at written and earned level.
BillingCenter receipts loaded via FBDI Receipt Import. Disbursements (commissions, NSF write-offs) loaded as AP invoices via FBDI AP Invoice Import. Reconciled against BillingCenter cash ledger and disbursement register.
ClaimCenter indemnity, expense and recovery payments routed to Fusion paid-loss GL accounts and AP claimant payments. Reserve changes carried as evidence metadata. Reconciled against ClaimCenter paid register and reserve register.
Final delta replay, parallel-close reconciliation, sign-off pack (premium register, paid-loss register, ceded-premium register, ceded-recovery register — Guidewire vs Fusion to the cent). Statutory accounting and GAAP accounting sign-off. Production cut to Syntra pipeline.
Statutory exams, GAAP audits, reinsurance audits and SIU subpoenas all demand the same thing: signed proof of data integrity. The Syntra ETL guidewire data migration sign-off pack delivers it.
Written premium, earned premium and unearned reserve per LOB per legal entity per period — PolicyCenter source vs Fusion target — reconciled to the cent with hash signatures.
BillingCenter daily cash receipts vs Fusion AR cash application per bank account per business day — full daily cash tie-out for the cutover window.
ClaimCenter indemnity + expense + recovery payments per coverage per claim per period vs Fusion paid-loss GL accounts and AP claimant payments — Schedule P aligned.
Ceded premium and ceded loss recovery per treaty per layer — bordereaux register vs Fusion ceded GL — for the standard reinsurance audit horizon.
Every reserve change (case + IBNR) with timestamp and user preserved as evidence metadata — actuarial loss-development triangle reconstructible from the archive for Schedule P and ICRA filings.
Every extract, transform, load and reconciliation step signed and timestamped with hash chains, satisfying state insurance commissioner chain-of-custody requirements during market-conduct exams.
Guidewire data migration is the process of moving structured policy, billing and claims data — written premium, earned premium, paid loss, paid expense, indemnity payments, subrogation recovery, reinsurance cessions — from Guidewire InsuranceSuite (PolicyCenter, BillingCenter, ClaimCenter) into Oracle Fusion Financials for statutory and GAAP accounting. It is NOT a replacement of Guidewire's core policy/claim engine. The technical heart is two-fold: streaming structured data through Guidewire Cloud Data Access (CDA), Cloud APIs and (for legacy on-prem) direct JDBC, and bulk-transferring multi-TB claims and policy attachments. Syntra ETL handles both with pre-built extractors, governed crosswalks for the InsuranceSuite data model to Fusion's GL/AP/AR/Revenue Recognition shape, and Oracle-validated FBDI output.
Migration is the end-to-end project (extract + transform + load + reconcile + cutover); conversion is the transformation layer specifically. Syntra ETL's Guidewire data conversion engine ships pre-built rules for premium ledger to Fusion revenue account mapping, paid-loss to GL paid-loss account translation, reserve change to GAAP loss-development triangle conversion, BillingCenter disbursement to Fusion AP supplier matching, commission disbursement to AP commission accounts, ClaimCenter indemnity to paid-loss-by-coverage GL, subrogation recovery to recovery accounts, and ceded reinsurance to ceded GL accounts. These are rules that on a consultant-led project would otherwise consume 4–6 months of bespoke CDA pipelines and SQL development.
Two different extraction profiles, one downstream pipeline. For Guidewire Cloud Platform (GWCP) — the AWS-hosted SaaS — Syntra uses Cloud Data Access (CDA) for bulk Parquet exports of the InsuranceSuite data model, Cloud APIs for REST-based incremental deltas, and Cloud Studio query bundles for any custom-rated risk decoding. For legacy on-prem InsuranceSuite (Tomcat/WebLogic + Oracle or SQL Server backend) Syntra uses read-only JDBC against a read-replica with Gosu-aware metadata extraction. Most large insurers run a hybrid (some lines on GWCP, others still on-prem) for several years post-Cloud-cutover, and Syntra handles both sides simultaneously without changing the downstream FBDI output.
Yes — and this is non-negotiable for P&C insurance. Reserve history (case reserves + IBNR) drives the actuarial loss-development triangle, which drives statutory reserves, reinsurance ceded calculations and Schedule P filing for the NAIC. Syntra ETL extracts every reserve change from ClaimCenter — initial reserve, every adjustment with timestamp and user, every reserve close — and preserves the full audit trail in the Fusion-targeted load (as reserve-by-period evidence metadata) and in the long-tail archive (as the full transactional history). Actuaries can rebuild any historical loss triangle from the archive without re-extracting from a decommissioned Guidewire instance.
Syntra ETL emits Fusion-native load formats for every Guidewire data domain: FBDI Journal Import for premium and paid-loss GL journals from the InsuranceSuite ledgers; FBDI AP Invoice Import for indemnity payments, expense payments and commission disbursements; FBDI Supplier Import for claimant, vendor and producer master from BillingCenter; FBDI Receipt Import for BillingCenter cash application; and REST API payloads for incremental delta loads during parallel-run and post-cutover. Every payload is validated against the current Oracle Fusion 26x release schema before submission, so validation errors surface locally — not in a 4-hour Fusion ESS job that fails on row 200,000.
Every record extracted from Guidewire is hashed at the source (policy hash + premium hash + claim hash + payment hash). Every record loaded into Fusion is re-hashed post-load. The reconciliation engine compares counts, sum totals (written premium, earned premium, paid loss, paid expense, ceded recovery per LOB per period) and hash signatures per ledger per period. Any record that fails Fusion validation is captured with the exact field-level reason ready for bulk fix. Output is a signed timestamped reconciliation pack: Guidewire premium ledger vs Fusion revenue to the cent, ClaimCenter paid-loss vs Fusion paid-loss GL to the cent, BillingCenter cash vs Fusion AR cash to the cent. Statutory accounting signs off on the pack directly.
Yes. After the initial bulk load, Syntra ETL captures Guidewire deltas via CDA's incremental Parquet exports and Cloud API modified-since watermarks on every domain (policies, transactions, claims, reserves, payments, cessions). Deltas are replayed into Fusion through FBDI and REST APIs. This supports the standard parallel-run pattern: legacy integration continues feeding Fusion for 1–2 close cycles while the Syntra pipeline runs side by side. Once statutory accounting, GAAP accounting and actuarial sign off, the legacy integration is retired and Syntra becomes the production path. Live policy issuance and claim handling in Guidewire are never disrupted.
State insurance commissioners conduct periodic market-conduct exams and financial exams that require pulling random policy and claim files, sometimes 10+ years old. Syntra ETL's guidewire data migration preserves the full chain: GL line in Fusion → premium/loss transaction → source policy/claim in Guidewire archive → underlying attachments (declarations page, claim file, recorded statement, medical records). Every hop is signed and timestamped. Read-access logs satisfy the chain-of-custody requirements that examiners look for. When a New York DFS or California DOI exam team arrives, the response is a query, not a six-month reconstruction project.
Book a 30-minute discovery call. We'll walk through your PolicyCenter/BillingCenter/ClaimCenter footprint, your GWCP/on-prem split, your statutory and GAAP ledger requirements, and your reinsurance cession profile — and give you a concrete data-migration plan and reconciliation strategy before the call ends.