More Than a Migration: Inside the Smithsonian's Enterprise-Wide Transformation with Nonprofit Cloud

The Smithsonian Institution is the world's largest museum and research complex, its reach stretching from national landmarks like the National Museum of American History to specialized research centers and archives found nowhere else. Every part of that network runs its own donor community, giving programs, and advancement staff, each with its own way of doing things.

For years, that work was supported by PANDA, a legacy platform that had served the institution well but was never built to keep pace with the Smithsonian's ever-evolving needs. Gift data, membership records, and constituent history lived in systems that did not always talk to each other, or to the institution's finance operations. Increasingly, donors expect a personalized, seamless giving experience. A modern, unified CRM stopped being a 'nice-to-have' and became a mission imperative. The Smithsonian needed a platform built to integrate fundraising, communications, finance and more purposefully and in real time. It needed a system that could be depended on as a single, shared source of truth.

The Smithsonian turned to Sleek to make it happen.

The Challenge: One Platform, Every Unit

Migrating from a Legacy CRM is rarely simple, and at this scale, the challenge was matching pace with size. PANDA held decades of donor, gift, pledge, and membership history, with every unit maintaining its own rule set.

The new platform needed to bring all of it together—major gifts, planned giving, memberships, ticketing, and digital giving—without slowing down a single unit or restricting what makes it unique. At the center of it all was going to be JAMES, the Smithsonian's new Salesforce Nonprofit Cloud platform.

The Solution: A Six Product Platform Built for Institutional Scale

Working closely with the Smithsonian's advancement and technology teams, Sleek designed and delivered six products at once, anchored by a core set of QSS™ Accelerators.

Getting to go-live took close collaboration with every unit, careful migration of years of PANDA history into JAMES without losing a single donor's record, and hands-on training so Smithsonian staff could run the system themselves from day one.

The Moment It All Clicked

Three days before user launch, a message came through the project channel that captured what both teams had been building toward.

A live, connected pipeline from donor to database to finance system. Not just a working CRM, but a connected institution.

Results

JAMES is live, Smithsonian's PANDA is retired, and every unit is working from one system of record. Six products launched together on day one, ERP and finance integration included, and within a week the Smithsonian's own team was running.

The QSS™ Accelerators Behind JAMES

At the Smithsonian, several accelerators anchored the work.

Biographical Management (QSS™ 1) shaped the foundation. When years of constituent history from every unit has to be converted onto a new platform without a record going astray, the data model has to be settled before anything else can be.

Gift Processing (QSS™ 2) was the go-live critical path. Gift entry had to work correctly on day one for every unit, at Smithsonian volume, with the finance handoff intact. It needed to handle donations, membership payments, and more through an efficient, accurate process.

Major Gifts and Prospect Research (QSS™ 5 and 6) came as a pair throughout design, giving gift officers portfolio, contact report, and prospect management structure that matched how the Smithsonian's teams already worked.

Donor Relations and Stewardship (QSS™ 7 and 8) and the online giving and sub-ledger suites (QSS™ 17 and 21) rounded out the core, connecting gift and financial data through to the ERP. That last piece is what made the moment described above possible.

Most institutions are not migrating at Smithsonian scale, but the underlying needs look much the same: constituent data everyone trusts, gift processing that keeps pace with volume, and GL reconciliation that does not get pushed to monthly or yearly.

What Made This Work

A project this ambitious comes down to the people who show up for it, and a few things stood out.

Deep nonprofit Salesforce expertise. The edge cases at this scale only surface with real platform mastery, from database architecture and strategy to Experience Cloud forms and multi-source duplicate resolution.

Disciplined development practices. A strict, staged deployment pipeline meant every change was validated before it touched production, so the team could move quickly without breaking things.

Focused design time. Because the QSS™ Accelerator suites brought proven structure to biographical management, gift processing, and prospect work, design sessions could focus on what made the Smithsonian (and every unit under its umbrella) distinct rather than on what every advancement shop has in common. That is time returned to the parts of the project that actually needed it.

True partnership. The Smithsonian's advancement and technology teams were active, engaged collaborators throughout, as was the broader stakeholder group. That effort was led by Hiruy Yimam, the Smithsonian's Director of Advancement Information Technology. The best implementations are not done for a client. They are built with them.

Asked about the project team's commitment to seeing the work through, Hiruy Yimam, Director of Advancement Information Technology at the Smithsonian Institution, put it this way: "Saying 'above and beyond' falls short."

What's Next

JAMES is live, and the most exciting work is still ahead. The Smithsonian's teams are already shaping the next round of enhancements, with Agentforce capabilities continuing to evolve and room ahead for deeper reporting, dashboards, and Marketing Cloud optimization.

What stands out most, looking back, is not the launch itself. It is that within a week the Smithsonian's own staff were supporting their colleagues on the new platform. A system belongs to the people who use it every day, and that transition happened faster here than on almost any project of this size.

If your institution is weighing a legacy CRM replacement, working through a migration that has stalled, or looking at where our QSS™ Accelerators could shorten the path, we would welcome the conversation.