How Pinnacol Assurance Eliminated A Legacy System and Modernized Regulated Document Automation with Intellistack

When Pinnacol Assurance began reassessing its technology stack, the conversation started with cost.

As Colorado’s leading workers’ compensation insurer — and a quasi-governmental entity responsible for covering high-risk industries across the state — Pinnacol operates under strict regulatory oversight. Every claims notice, audit form, and policy document must comply precisely with Department of Workers’ Compensation (DOWC) language and formatting requirements.

For years, most of that correspondence lived inside a legacy system.

It was expensive. Increasingly unsupported. And deeply embedded in integrations that no longer aligned with Pinnacol’s Salesforce-first modernization strategy.

At some point, maintaining it felt less like stability and more like inertia.

The mandate became clear: simplify the stack, reduce technical debt, and consolidate vendors — without compromising compliance.

Turning a Migration into a Modernization Strategy

What could have been a straightforward document conversion project quickly revealed itself to be more complex.

More than 200 highly regulated documents needed to be rebuilt inside Salesforce as dynamic PDFs. These weren’t simple templates. Many required precise field population from Salesforce JSON payloads, bilingual formatting, and exact replication of legally mandated language. Even small deviations in wording or layout could introduce regulatory risk.

Pinnacol brought in The CRM Firm (CRMF) to lead the implementation of Intellistack’s Formstack Documents for Salesforce — and that partnership proved pivotal.

Rather than approaching the effort as a lift-and-shift migration, CRMF structured it as a phased modernization. Documents were prioritized into tiers, beginning with the most critical and highest-volume forms. Complexity was mapped early, allowing the team to refine templates, data mapping logic, and formatting controls before scaling across the full document library.

Early iterations surfaced challenges around header alignment, spacing, field mapping, and ensuring page counts remained consistent with legacy outputs. In a regulated environment, even adding a page could impact mailing costs and operational workflows.

CRMF worked closely with Pinnacol’s internal team to build a repeatable, scalable framework for mapping Salesforce JSON data directly into Intellistack templates. That precision mattered. By the time the team moved beyond the first wave of documents, they had created a structured, reusable process that significantly accelerated delivery.

The collaboration was tight, iterative, and transparent. CRMF provided dedicated project management, regular status reporting, and hands-on technical refinement — filling coordination gaps and helping Pinnacol maintain momentum.

What began as careful progress soon became confident execution.

216 Documents. Zero Compliance Drift.

In total, 216 templates were converted into Intellistack-generated PDFs within Salesforce.

The language remained exact. Formatting was preserved. English and Spanish variants were aligned. Complex claims documentation and medical reporting forms were dynamically generated without introducing compliance exposure.

Just as importantly, knowledge transfer was built into the process. As the implementation matured, Pinnacol’s team gained the confidence and capability to manage template updates internally. CRMF didn’t just deliver a solution — they enabled sustainable ownership.

By the later phases of the project, the system felt less like a vendor deployment and more like a fully integrated extension of Pinnacol’s Salesforce environment.

Eliminating A Legacy System and Reducing Technical Debt

Behind the document work was a larger strategic driver: vendor consolidation.

Pinnacol’s legacy system carried substantial licensing and maintenance costs. Maintaining it alongside Salesforce no longer made financial or architectural sense. The project aligned with broader budget objectives established in mid-2023 planning cycles, with a target to fully decommission the legacy system by the end of 2024 once API rework is complete.

Retiring the legacy platform means more than cost savings. It reduces integration complexity, simplifies long-term support, and shrinks Pinnacol’s vendor footprint — all while centralizing document generation within the system where the rest of the business already operates.

For a regulated organization, reducing technical debt while strengthening compliance controls is a rare combination.

Strengthening the Digital Experience

Although the initiative began as a cost and infrastructure discussion, the impact extends beyond IT.

Policyholders and injured workers now access correspondence through a portal experience connected to Salesforce. Audit forms, coverage notices, and claims-related documentation can be downloaded on demand. Mailing volume declines. Staff workload eases. Manual fulfillment decreases.

The organization didn’t launch the project because stakeholders demanded a new document system. They launched it to simplify operations. But in doing so, they advanced their broader digital transformation strategy in meaningful ways.

A Foundation for What’s Next

With document automation centralized in Salesforce, Pinnacol is now positioned to continue modernizing adjacent processes. Discussions are underway around consolidating additional legacy tools, including e-signature platforms, and further streamlining workflows.

The document transformation became a catalyst.

And CRMF’s structured approach — from tiered prioritization to repeatable template design to disciplined project governance — helped ensure the initiative didn’t stall under regulatory complexity.

Instead, it accelerated.

Outcomes

Document Modernization

• 216 legacy templates successfully converted to Intellistack PDFs
  
  
• Exact DOWC-compliant language and formatting preserved
  
  
• Dynamic population from Salesforce JSON data
  
  
• Bilingual document support maintained
  
  

Cost Savings & Vendor Consolidation

• Legacy licensing and maintenance costs eliminated upon full decommission
  
  
• Reduced vendor footprint
  
  
• Simplified architecture aligned with Salesforce-first strategy
  
  
• Targeted full legacy retirement by early 2026
  
  

Operational & Customer Impact

• Portal-based document access for policyholders and injured workers
  
  
• Reduced mailing and manual fulfillment costs
  
  
• Improved internal efficiency and scalability
  
  
• Internal team trained to manage ongoing template updates
  
  

Lessons Learned

• Phased, tier-based rollout reduces risk in regulated environments
  
  
• Early investment in repeatable template architecture accelerates scaling
  
  
• Tight collaboration and project governance are critical in compliance-heavy industries
  
  
• Vendor consolidation can drive both cost savings and strategic modernization
  
  

Next Steps

• Complete API rework to finalize legacy system decommission
  
  
• Explore expanded e-signature and workflow consolidation
  
  
• Continue Salesforce-centric digital transformation initiatives

‍