---
title: "Map every Salesforce dependency before you clean it up | Rig"
description: "A US education software company planned to switch off around 40% of its Salesforce fields. Mapping every dependency first made the cleanup safe to run, and turned up renewals lost without a warning and over $1M of customer enquiries nobody had answered."
canonical: "https://rig.so/case-studies/education-software-group"
format: markdown
---

Audits · EdTech · Enterprise

# Map every Salesforce dependency before you clean it up

A US education software company planned to switch off around 40% of its Salesforce fields. Mapping every dependency first made the cleanup safe to run, and turned up renewals lost without a warning and over $1M of customer enquiries nobody had answered.

**45,381**custom Salesforce fields mapped before the cleanup

**62%**of lost renewal dollars booked as churn before the account owner was alerted

**$1M+**of customer enquiries found unanswered

[Before](#before)[The audit](#fields)[Renewals](#renewals)[Enquiries](#enquiries)

## A complicated Salesforce cleanup

Years of acquisitions had left 45,381 custom fields in Salesforce, 4,617 of them on the 17 core objects, and 2,505 places where a field was referenced in hand-written code. About 40% of those fields were due to be switched off.

Nobody could see what each change would break. A single field could feed more than 14 downstream rules, flows and systems, including commissions and finance, so approvals slowed down and deals slipped at the end of a quarter.

## Rig traced every field and delivered a read-only audit of the Salesforce estate

It took 22 days from the start of work. Every rule, trigger, flow and warehouse view that reads a field can now be traced, so the blast radius of each change, everything it would touch, is visible before it ships. Fields come out in a safe order, and each change gets a red, amber or green verdict.

> “This blast radius is just probably the number one thing.”

SVP, Go-to-Market Operations

## The cleanup found renewals lost without a warning

Project health and support signals had no route to the account owner. By February, 62% of the season’s lost renewal dollars had already been booked as churn, without anyone alerting the person responsible for the account.

## The cleanup also found unanswered buying enquiries

The map surfaced over $1M of open customer enquiries that nobody had answered, including 206 from districts asking to buy. Larger districts that had never bought, with 100 or more staff, received 14% of the sales development team’s calls, yet those calls booked meetings at 5.3%, against 1.9% for calls to existing customers.

Talk to Rig

## What work do you want to improve?

Tell us where your team spends time, loses money or needs better information.
In a 30-minute call, we’ll discuss the data and systems work that could help.

[Discuss your project](https://rig.so/book-demo)Use the platform with your team, or add our engineers.

---

- [This page as HTML](https://rig.so/case-studies/education-software-group)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)
