From Guidewire Cloud Access to analytics-ready data

Insurers moving from on-premise Guidewire InsuranceSuite to Guidewire Cloud are making a strategic investment in agility, faster upgrades, and a more modern data architecture.

A key part of that transition is Guidewire Cloud Data Access (CDA). Rather than relying on batch extracts or direct database access, CDA continuously delivers incremental InsuranceSuite data to Amazon S3 as Parquet files, with near real-time updates, exactly-once guarantees, and current schema definitions.

But getting Guidewire data into S3 is only the first step. To make that data useful for analytics, reporting, and AI, it still needs to be continuously ingested, structured, and maintained as schemas evolve.

This is where many insurers run into challenges:

"Our Guidewire data is in S3, but the business can't use it."

Claims, underwriting, actuarial, and finance teams can't work directly from raw Parquet files. Until that data is loaded into a governed destination, the value of CDA remains out of reach.

"Every new entity creates more engineering work."

What starts as a manageable ingestion project can quickly become a growing backlog of custom jobs, file mappings, and maintenance tasks.

"Schema changes keep breaking pipelines."

As Guidewire introduces new fields, entities, and data types, brittle ingestion processes can fail. Dashboards become outdated, reporting slows down, and confidence in the data erodes.

How CDA works and why it matters for ingestion

CDA exports data through a commit model. Guidewire writes incremental Parquet files to S3, organized by table and timestamp folder. A manifest.json file tracks the last fully committed write timestamp, serving as the authoritative signal that a batch is complete and ready to consume. Any downstream process that uses this manifest watermark can avoid reading partial or in-flight data.

CDA environments also expand over time. A typical deployment can span hundreds of entities across PolicyCenter, BillingCenter, and ClaimCenter. New tables may appear as Guidewire releases updates or carriers launch new products, and schema changes are continuous. Ingestion that depends on manual entity setup or hands-on schema management can quickly become a bottleneck.

Guidewire data in your warehouse — complete, consistent, and ready to use

Fivetran's Guidewire Cloud Data Access connector is purpose-built for CDA ingestion. Point it to a CDA bucket and manifest, and it manages the rest: table discovery, incremental syncs, schema evolution, and Guidewire’s commit model, without ongoing configuration or engineering effort.

• Automatic table and schema discovery. Tables are discovered from the manifest instead of configured manually. New entities and schema changes are picked up on the next sync.
• Manifest-gated consistency. Before every sync, the connector reads the per-table high watermark and ingests only files Guidewire has fully committed, so in-flight data never reaches your destination.
• A built-in audit trail. At each sync, manifest state is written to a queryable manifest table in your destination, including the committed watermark, cumulative record count, and schema fingerprint history for each table.
• Performance that holds over time. List operations are scoped to the window between the last sync bookmark and the current manifest watermark, keeping syncs efficient as CDA retention grows.

What this means for insurers

As Guidewire encourages carriers to move to the cloud, insurers have an opportunity to modernize their data architecture alongside their core system transformation. Fivetran's Guidewire CDA connector helps make that transition easier.

• Move faster with less maintenance. Automatic table discovery and built-in schema evolution eliminate much of the operational overhead of managing Guidewire pipelines, allowing data teams to focus on analytics, reporting, and downstream applications instead of pipeline maintenance.
• Deliver trusted data to the business. Every record loaded into your destination comes from a fully committed CDA batch. Claims, underwriting, actuarial, and finance teams can work from consistent, reliable data without reconciliation headaches.
• Scale as your environment grows. Whether you're running PolicyCenter, BillingCenter, ClaimCenter, or all three, the connector adapts automatically as new entities, products, and schema changes are introduced.
• Extend your cloud data foundation. Apply the same automated, governed approach you use for the rest of your data stack to one of the most critical systems in the insurance enterprise.

Turn CDA exports into analytics-ready data

If you're using Guidewire Cloud Data Access or planning a migration to Guidewire Cloud, Fivetran provides an automated path from CDA exports in S3 to analytics-ready data in your warehouse or lake.

Get started with the Guidewire Cloud Data Access connector ->

Want to see how it would work in your environment? Reach out to your Fivetran account team for a tailored walkthrough.

[CTA_MODULE]