Roughly 70% of personal and commercial lines premium in the United States still flows through policy administration systems (PAS) designed before the iPhone existed. Mainframe COBOL platforms at carriers like Travelers, Hartford, and Liberty Mutual were originally written between 1978 and 1995, layered with three decades of bolt-ons, and are now maintained by engineers approaching retirement. The cost of keeping them alive — typically 65-75% of insurance IT budgets goes to 'run-the-bank' spend — is the single largest constraint on every other transformation initiative this guide covers, from usage-based rating to claims automation.
A modern PAS handles product configuration, rating, quoting, binding, issuance, endorsement, renewal, cancellation, billing integration, and reinsurance ceding for every policy a carrier writes. Replacing one is the largest discretionary technology investment a P&C insurer ever makes: $50M for a regional monoline carrier, $300M-$800M for a top-25 multi-line carrier, and over $1B for the largest nationals when you include data migration, product re-implementation, and parallel operations. Roughly one in three programs is abandoned, descoped to irrelevance, or restarted with a new system integrator within 48 months.
What the legacy PAS actually costs
The headline number is operating cost. A 1990s-era PAS running on IBM z/OS with DB2 and CICS typically costs $35-$60 per policy per year to operate, versus $8-$15 for a cloud-native platform. But the operating cost is the smaller problem. Three structural costs dwarf it.
First, speed-to-market. Filing a new product variant — say, adding a cyber endorsement to a BOP, or implementing a wildfire surcharge in California zip codes adjacent to declared CAL FIRE high-severity zones — typically takes 9-14 months on a legacy PAS because rate tables, forms libraries, and rules are encoded in COBOL copybooks rather than externalized configuration. The same change on Guidewire PolicyCenter Cloud or Duck Creek OnDemand averages 6-10 weeks. For a personal auto carrier filing rate revisions in 50 states annually, this is the difference between leading and trailing the market by two full rate cycles.
Second, data accessibility. Legacy PAS data models were optimized for transaction processing on 1990s hardware: hierarchical VSAM files, denormalized DB2 schemas, and policy versions stored as overlays rather than discrete records. Extracting a clean, time-correct view of in-force exposure for catastrophe modeling — covered in detail in our climate modeling article — typically requires a 48-72 hour ETL run and produces exposure files that are already stale when delivered to RMS or Verisk Touchstone.
Third, integration cost. Every new third-party data source — MVR, CLUE, LexisNexis Current Carrier, smart-home telemetry, ISO RiskMeter — requires custom screen-scraping or point-to-point integration. Carriers running legacy PAS typically maintain 200-400 active integrations, each costing $80K-$250K per year in change management overhead.
The vendor landscape in 2026
The modern PAS market has consolidated into five viable platforms for tier-1 and tier-2 carriers, with a fragmented long tail serving MGAs, specialty carriers, and emerging insurers. Selection is largely driven by line-of-business fit, deployment model, and the depth of the system integrator ecosystem.
| Platform | Deployment | Strength | Typical Carrier Size |
|---|---|---|---|
| Guidewire PolicyCenter (Cloud) | AWS-hosted SaaS | Personal lines, mid-market commercial; deepest SI ecosystem | Tier 1-3 multi-line |
| Duck Creek OnDemand | Azure-hosted SaaS | Commercial lines, specialty; strong rating engine | Tier 1-3 commercial |
| Majesco P&C Suite | AWS/Azure SaaS | Mid-market, MGA, program business | Tier 3-5, MGAs |
| EIS Suite | Cloud-native microservices | Customer-centric data model; multi-LOB | Tier 2-3 |
| Socotra / Instanda | API-first SaaS | Greenfield, embedded, niche products | Insurtechs, MGAs |
| Sapiens IDITSuite | Cloud or on-prem | International, workers comp, specialty | Tier 2-4 |
Guidewire reached approximately 540 customers across PolicyCenter, BillingCenter, and ClaimCenter by Q1 2026, with cloud migration accelerating after the company effectively ended new on-premises licenses in 2023. Duck Creek, taken private by Vista Equity Partners for $2.6B in 2023, has been aggressive on commercial lines and specialty, winning displacements at AIG, Allstate (commercial), and Munich Re's HSB unit. EIS has differentiated on a customer-centric (rather than policy-centric) data model that appeals to carriers prioritizing cross-line bundling, the subject of our Customer 360 article.
Below the tier-1 platforms, Socotra (acquired by EIS in 2023) and Instanda compete for greenfield builds where time-to-market matters more than feature depth — typical use cases include embedded insurance products and MGA-launched specialty lines. A monoline cyber MGA can stand up a working PAS on Socotra in 90-120 days versus 18-24 months on Guidewire.
Four replacement strategies
Carriers approach PAS replacement through one of four patterns. The choice is more consequential than the vendor selection itself, because it determines program risk, duration, and the order in which business value is unlocked.
Big bang replacement migrates all lines of business, all states, and all books simultaneously on a single cutover date. The approach worked for some 1990s mainframe-to-mainframe migrations but has a documented failure rate above 60% in modern PAS programs. The most recent high-profile failure: a top-15 carrier abandoned a $400M big-bang PolicyCenter program in 2022 after 51 months, having migrated only the homeowners book in two states. Big bang remains defensible only for monoline carriers under $500M GWP with simple product portfolios.
Line-of-business sequencing migrates one LOB at a time — typically personal auto first, then homeowners, then small commercial, then middle market. This is the dominant pattern for tier-1 carriers and is what Nationwide, Farmers, and Zurich North America have used. Total program duration is 4-7 years, but business value accumulates from year 2 onward. The principal risk is integration complexity during the multi-year coexistence period when the new and legacy PAS both write business.
State sequencing migrates one or a few states at a time across all LOBs. Used primarily by carriers with heavily state-customized products (workers comp specialists, regional mutuals). Reduces regulatory filing risk but multiplies the integration effort because every state cutover requires a synchronized billing, claims, and reporting cutover.
Strangler fig pattern wraps the legacy PAS in an API layer and incrementally redirects functionality to new microservices, eventually retiring the legacy platform. This is the lowest-risk approach but only works when the legacy PAS can be API-enabled — typically requiring middleware like MuleSoft, Apigee, or a custom integration platform. The pattern is described in more architectural depth in our microservices vs. modular core architecture analysis. USAA, Travelers, and Allstate have all used strangler patterns for selective functionality (quoting, FNOL, agent portals) while keeping core policy issuance on legacy until later phases.
Architecture: what 'modern' actually means
Buying Guidewire Cloud does not, by itself, make a carrier modern. The architectural decisions made during configuration determine whether the new PAS becomes a faster legacy system or a genuine platform for product innovation. Five design choices matter most.
Externalized product configuration. Rating algorithms, form selection rules, and underwriting eligibility should be expressed in configuration (decision tables, DMN models, or low-code rule editors) rather than Java/Gosu code. The test: can a product manager change a rating factor and deploy it to UAT without engaging engineering? Carriers that get this right reduce rate-revision deployment time from 12 weeks to 5-10 business days.
Event-driven integration. Modern PAS implementations publish policy lifecycle events (PolicyBound, EndorsementIssued, PolicyCanceled) to a Kafka or AWS Kinesis stream rather than relying on batch extracts. Downstream systems — billing, claims, data warehouse, reinsurance, agent commission — consume events in near real-time. This is the same architectural shift covered in our analysis of batch-to-real-time ledger architectures in banking.
API-first product distribution. Every quote, bind, and endorsement action should be available as a REST or GraphQL API, with the carrier's own portals and agent UIs treated as just another API consumer. This is the precondition for embedded distribution covered in our embedded insurance article.
Multi-tenant rating engine separation. Leading carriers are increasingly separating the rating engine from the PAS proper, allowing the same rates to be called from the PAS, the agent portal, third-party aggregators (EverQuote, The Zebra, Insurify), and embedded partners without inconsistency. Earnix and Akur8 have built standalone rating-and-pricing platforms that sit alongside Guidewire and Duck Creek for this reason.
Data model normalization. The single most consequential decision is whether to adopt the vendor's reference data model (ACORD-aligned for Guidewire, Duck Creek's proprietary model, or EIS's customer-centric model) or to customize it heavily. Carriers that customize more than 20-25% of the data model lose most of the vendor's upgrade benefits and effectively own a custom system again within five years.
Data migration: where programs actually die
Vendor selection consumes 6-9 months of executive attention. Data migration consumes 30-40% of total program cost and is where the majority of failed programs unravel. The reason is structural: legacy P&C data has 20-40 years of accumulated business rules encoded as conventions rather than constraints.
A representative example: a homeowners book at a regional carrier had a 'roof_age' field that was populated three different ways across vintages. Policies issued before 1998 used roof_age = (current_year - construction_year), assuming the original roof. Policies from 1998-2011 used inspector-reported roof age. Policies after 2011 used a derived field from a third-party property data integration. Migrating this to a clean roof_age attribute in the new PAS required reconstructing the underwriting intent for each policy vintage — a six-month exercise across actuarial, underwriting, and IT for a single field on a single book.
Typical migration scope for a mid-size multi-line carrier:
Three migration patterns are used in practice. Full historical migration moves all policy versions back to inception — most accurate, but doubles or triples migration cost. Active-only migration moves in-force policies plus 24-36 months of expired policies, with the legacy system retained in read-only mode for older history. Effective-date snapshot migration migrates only current effective values, accepting loss of version history. The vast majority of programs choose active-only migration with read-only legacy retention, which typically adds $8M-$20M per year in legacy maintenance cost during the 5-7 year retention window.
Implementation economics and timeline
A representative program for a tier-2 multi-line carrier ($2B-$5B GWP) writing personal auto, homeowners, and small commercial lines:
Vendor selection, SI selection, target operating model design, reference architecture, data model decisions. Burn rate: $1.5M-$3M per month. Output: signed contracts, architecture blueprint, business case refreshed with bottom-up estimates.
Product configuration, rating engine implementation, integration build-out, data migration tooling, first agent portal release. Burn rate: $3M-$6M per month. Output: live policies on new PAS in pilot states, typically 50K-200K policies.
State-by-state rollout of personal auto, parallel build of homeowners. Coexistence operations stabilize. Burn rate: $4M-$7M per month. Output: 100% of personal auto on new PAS, homeowners in pilot states.
Homeowners and small commercial complete. Legacy PAS moves to read-only. SI staffing ramps down. Burn rate: $2M-$4M per month.
Final history archival, regulatory retention compliance, mainframe shutdown. Run-rate IT cost reduction of 40-55% achieved 12-18 months after final cutover.
Total program cost for the reference carrier: $180M-$320M, with software licenses representing 15-20%, system integration 45-55%, internal carrier resources 20-25%, and data migration 10-15%. The big four/SI market is dominated by Accenture, Capgemini, Deloitte, EY, PwC, and Cognizant for tier-1 programs, with specialty firms like ValueMomentum, X by 2, and Saggezza taking mid-market work at 25-40% lower blended rates.
Measuring success: what KPIs matter
Carriers that treat PAS replacement as an IT modernization project rather than a business transformation typically deliver the new system on time and on budget — and produce no measurable business improvement. The KPIs that distinguish successful programs are business outcomes, tracked quarterly, with named accountability.
Values shown as percentage improvement (rate revision time = 78% reduction; conversion rate = 18% increase). Bottom-quartile carriers see less than half these gains because product configuration is still treated as a technical, not business, function.
Three KPIs deserve special attention. Speed-to-file measures elapsed days from product change approval to SERFF filing readiness — top performers achieve 15-25 days versus 90-120 for laggards. Configuration-vs-code ratio measures what proportion of product logic lives in business-managed configuration versus engineering-managed code; healthy targets are 75%+. Integration mean time to deliver measures elapsed days to integrate a new third-party data source — modern PAS architectures hit 20-40 days versus 6-9 months on legacy. This last metric matters for third-party data integration economics across underwriting and claims.
What boards should ask before approving
PAS modernization is the largest discretionary capital allocation most P&C boards will see in a decade. The questions that separate disciplined programs from ones that will be written down in year 4 are surprisingly specific.
The carriers that complete PAS modernization on schedule are not the ones with the best technology or the best SI. They are the ones whose CEO publicly committed to the timeline and whose board reviewed program health monthly, not quarterly.
PAS replacement remains the highest-stakes technology decision in P&C. Done well, it cuts unit operating costs by half and reduces time-to-market by an order of magnitude, unlocking everything from AI-assisted underwriting to embedded distribution. Done badly, it consumes a decade of capital and management attention while competitors writing on modern platforms file rates twice as often, integrate new data sources four times faster, and capture the segments the carrier used to lead.