For Papé Kenworth and Papé Group CRM leadership

Papé Kenworth has grown to 30 locations in five Western states, and Papé Group runs CRM and marketing for its brands on Salesforce.

Durham-Pentz joined in November 2025 and the new Yakima facility opened its doors to the community in April 2026. Flosum keeps that Salesforce data backed up and every change tested before it reaches the branches.

Book the working sessionWhy Flosum, specifically
30Papé Kenworth locations
5States: CA, OR, WA, NV, AK
160Papé Group locations across 8 brands
1,600Papé Group technicians
Where Papé Kenworth is headed

Papé Kenworth is growing by acquisition and by building larger service sites.

Durham-Pentz Truck Center became a Papé Kenworth parts and service location effective November 7, 2025.

Yakima moved into a 42,000-square-foot facility with 15 service bays; about 50 trucks are usually on site for service.

Ryan Papé now leads Papé Kenworth as president.

Footprint

30 locations.

Service

15 bays in Yakima.

Group

8 brands, 85 cities.

Pressures

Uptime is the promise, and the CRM has to keep pace with every new branch.

Acquisitions

Each acquired dealer brings its own customer records.

Group scale

160 locations and 815 service bays across Papé Group.

Marketing

Salesforce Marketing Cloud drives customer campaigns.

Service volume

About 50 trucks on site at Yakima on a usual day.

What leadership has said

Papé Kenworth’s leadership ties each acquisition to service continuity.

We are excited to welcome Durham-Pentz Truck Center customers to the Papé Kenworth family and look forward to continuing the tradition of excellent service and support.

Dave Laird, President, Papé Kenworth (Nov 2025)

Continuity for acquired customers depends on clean, recoverable records.

Papé Kenworth’s Salesforce reality

Papé Group runs a dedicated group CRM team on Salesforce.

From Papé’s own staff roles.

Group CRM
A Director of Group CRM, a former Salesforce consultant, has led the function since 2023.
Marketing Cloud
A senior manager runs marketing automation on Salesforce Marketing Cloud.
Shared org
One group team serves 8 brands.
What’s at risk

One bad change in a shared group org reaches every Papé brand at once.

If this happensWhy it is plausibleWhat it costs
A release breaks a shared objectGroup CRM across 8 brands.Every brand affected.
Records lost in a dealer migrationDurham-Pentz acquisition.Customer history gone.
Marketing data overwrittenMarketing Cloud campaigns.Campaigns stall.
Why it’s imperative for Papé Kenworth to choose Flosum

Flosum keeps Papé’s shared Salesforce org recoverable as the network grows.

Each row is a Papé fact.

Papé Kenworth initiativeExposure todayFlosum capabilityOutcome
8 brands on group CRMChanges collideGoverned pipeline with rollbackStable releases
Dealer acquisitionsData migrationBackup and point-in-time restoreRecoverable records
Marketing CloudCustomer data useMasked test dataPrivate sandboxes
30 Kenworth locationsMany usersAudit trail of changesClear ownership

Flosum is rated 4.80 on G2 and 4.97 on AppExchange.

Flosum DevOps

A governed release pipeline lets the group CRM team ship changes for one brand without breaking the other seven.

Control.

Where it bites today

  • 8 brands

What Flosum changes

  • Admin clicks, developer code and AI-generated changes all go through the same version control, approvals and audit trail.
  • Metadata is merged component by component, so two people editing the same Flow or profile do not overwrite each other.
  • A dependency graph catches the deployment that would fail before it reaches production.
  • If a release goes wrong, one-click rollback puts the org back.
  • Release evidence is produced as the work happens and kept beyond Salesforce’s native 180-day Setup Audit Trail.

How Papé Kenworth would measure it

  • Failed deployments
Flosum Backup & Archive

Backup with point-in-time restore protects customer and fleet records through each acquisition.

Recoverability.

Where it bites today

  • Durham-Pentz

What Flosum changes

  • Backups run near-continuously, and restores can target a single field, a record or the full org at a point in time.
  • Data, metadata, files and the relationships between records are all protected.
  • Backups can live with Flosum or in your own AWS, GCP, Azure or private cloud, with keys you hold.
  • If Flosum cannot restore your data, Flosum pays up to $100,000.
  • Salesforce’s Weekly Export runs every 7 days and deletes files after 48 hours; its Data Recovery Service costs $10,000, takes 6 to 8 weeks and returns no metadata.

How Papé Kenworth would measure it

  • Restore time
Flosum Sandbox Management

Warm-start sandboxes let the team test dealer migrations on real data shapes first.

Test first.

Where it bites today

  • Acquisitions

What Flosum changes

  • Developer sandboxes arrive ready to work: Flows disabled, PII masked, production data seeded, access locked and the pipeline reconnected.
  • Full-copy sandboxes stay in continuous sync with production, so the 29-day refresh window stops setting the schedule.
  • Teams need fewer full-copy licenses, and the 25 to 100 developer sandboxes in Enterprise editions stop sitting idle.

How Papé Kenworth would measure it

  • Hours to a usable sandbox

Sandbox Management is in early access; Flosum offers a 30-minute working demo on your own metadata.

Flosum Data Masking

Masking keeps customer contact data out of test orgs.

Privacy.

Where it bites today

  • Marketing Cloud

What Flosum changes

  • Masking happens before data lands in the sandbox, which turns it from a best-effort cleanup into a guarantee.
  • Because masking is part of sandbox provisioning, every new developer sandbox is masked by default.
  • Encryption keys can stay with your team.

How Papé Kenworth would measure it

  • Share of sandboxes masked
Org protection from configuration errors

Change history shows who changed what, by brand.

Audit trail.

Where it bites today

  • Group CRM

What Flosum changes

  • Automatic org synchronization flags drift when someone changes production outside the pipeline.
  • If a release goes wrong, one-click rollback puts the org back.
  • Salesforce’s native Backup shares the platform’s infrastructure and does not back up Flows, profiles or permission sets.

How Papé Kenworth would measure it

  • Audit prep hours
Why now

Papé Kenworth added a dealer in November 2025 and opened a larger Yakima site in 2026.

Each new location adds records to the same org.

Nov 2025Durham-Pentz acquisition
Apr 2026Yakima open house and ribbon cutting
2026Ryan Papé leads Papé Kenworth

The first 90 days

  1. Backup baseline
  2. Pipeline for group CRM changes
  3. Masked sandboxes
  4. Restore drill
Next step

A 30-minute working session with Papé’s Group CRM team on protecting the shared Salesforce org.

Bring the Director of Group CRM.

  • Backup baseline
  • Release pipeline
  • Acquisition data migration
Book the working session
Prepared by Flosum for Papé Kenworth, October 24, 2026. Papé Kenworth names and program names belong to their owners.