Why we built Corral Works for Ellucian CRM Advance

Walk into any college advancement office on a Tuesday afternoon and you’ll find someone in a spreadsheet. Not because they love Excel. Because the database can’t be edited the way the work actually flows.

A constituent moves. A campaign closes and twenty gifts need to land on a different designation. A reunion produces a list of fifty alumni who should have an updated affinity code. None of those are exotic data problems. All of them are common. And in Ellucian CRM Advance, all of them are surprisingly expensive to do well.

That’s the gap we built Corral Works to close.

The pattern we kept seeing

We’ve spent a lot of time embedded with advancement services teams. The pattern looks like this:

1. Someone identifies a small data problem — a hundred wrong addresses, a designation that needs to move, a salutation field that’s missing on a cohort.
2. They run a query in Advance, export to Excel, and fix it there.
3. The Excel file gets handed to IT.
4. IT runs the import, often in a release window that’s days or weeks away.
5. Someone spot-checks the result and files follow-up tickets for the rows that failed.

That whole loop runs anywhere from a few hours to a few weeks. Every step is reasonable in isolation. Together they make small updates feel like a project — and projects get deferred. Data quality decays. Reports start to lie a little.

Why “just give staff direct access” isn’t the answer

The honest reason this loop exists is that direct edits in Advance are scary. The UI lets you do things that the database doesn’t actually want. Bulk operations are limited or hidden. There’s no preview. There’s no diff. There’s no obvious way to roll back a bad import. So IT becomes the gate, and gates create queues.

We didn’t want to remove the gate. We wanted to move it earlier, into the tool itself.

What we ended up building

Corral Works is what an Advance shop ends up with if you take that whole loop seriously and try to compress it:

• Staff search and filter records the same way they do in Advance.
• Edits — single or bulk — happen in place. The data stays in Advance the whole time. No round-trip through Excel.
• Before anything writes, Corral Works runs every change against Advance’s actual validation rules. Bad rows get flagged with the same errors IT would have caught after the import.
• Staff see a clean before/after diff for every record. They commit when they’re ready.
• Every change is attributed, timestamped, exportable, and reversible at the batch level. The DBA gets the audit trail. Finance gets the receipt. The advancement officer gets their afternoon back.

That’s it. It’s not a CRM. It’s not a reporting tool. It’s a focused tool for the specific kind of small, day-to-day data work that Advance makes painful.

Why Advance first

The Ellucian Advance shops we’ve worked with all share the same shape: a small number of people who care deeply about data quality, a CRM that wasn’t designed for the way they actually work, and an IT team that doesn’t have the bandwidth to absorb every cleanup request. That’s the audience this tool was built for, in their language, with their data shapes.

Corral Works runs against Microsoft Dynamics CRM more broadly — Advance is built on Dynamics 365 underneath — so non-Advance Dynamics CRM shops can use it too. But Advance is where we’re focused, where the design decisions get made, and where the next year of work is pointed.

If your team has spent an afternoon in Excel fixing something that should have taken ten minutes, we built this for you. Get on the waitlist and we’ll be in touch.