A nonprofit’s CRM migration revealed an organizational data problem with no clean fix—until the solution was designed around structure, not just software.

The Situation

The organization provides services to people with developmental disabilities, such as autism and related conditions, from early childhood through adulthood. Operating primarily on Long Island, they partner with school districts and state agencies, running programs across multiple departments and life stages.

When the engagement started, three things were happening at once: a full organizational rebrand (new name, new identity, new website), a hard deadline to exit their legacy email platform before year-end, and the growing realization that their contact data was in worse shape than anyone had initially expected. All three tracks needed to run in parallel.

The Problem Behind the Problem

On the surface, the “ask” was a contact migration: move records out of Axios HQ and into HubSpot. But the legacy platform wasn’t functioning as a CRM in any practical sense—it held contacts and sent emails, but had no segmentation logic, no property structure, and no hierarchy. There was nothing to migrate to without first deciding what HubSpot needed to look like.

The real issue was organizational.

• The nonprofit operated multiple distinct programs, including early childhood services, school district partnerships, adult day programs, and donor management, and each had been functioning independently.
• Staff members were manually pulling contact spreadsheets from each program to build mailing lists.
• There was no shared framework, no common properties, no way to query across the whole contact database.

Dropping that data into HubSpot without solving the architecture first would have just recreated the same mess in a new environment.

There was also a content dimension specific to this sector. Organizations serving people with disabilities operate within a precise and evolving set of language standards around how the people they support are described. Getting that terminology right is a trust signal to families, staff, and partner organizations—and it sits in direct tension with SEO, where the terms families actually search rarely match the preferred language used internally. That tension needed to be addressed explicitly, not papered over.

The Approach

Rather than treating this as a lift-and-shift migration, the Hypha team built a system for how contacts would be managed going forward.

Custom contact properties were created to map to each of the organization’s program types: early childhood, adult services, donor, family member, employee, and others. From there, the team developed a standardized import template that staff across any department could use to populate and categorize contacts correctly. HubSpot workflows were configured to automatically assign contacts to the right segments on import, triggered by the property values in the incoming file.

The result was a process any marketing staff member could run without technical knowledge. When a new list arrived from a program team, the staff member could import it, select the relevant property, and HubSpot would handle segmentation automatically—no manual sorting, no reconciliation after the fact.

That custom property framework was also designed with the future in mind. The organization is working toward a centralized internal database that consolidates program data from across all departments. When that system is ready, HubSpot’s property structure is already in place to serve as the receiving end of an API-based sync, eliminating manual imports entirely.

The Website

In parallel with the migration, the team rebuilt the organization’s website from scratch on HubSpot CMS.

The previous site had been built on a proprietary in-house platform, and had real limitations: the blog was actually a mixed listing of press releases, event announcements, and articles, and clicking what looked like a blog post often redirected visitors off-site entirely. In effect, there was no clean editorial environment and no structured path toward conversion.

The new site was built outward from the client’s new brand guidelines, with structured navigation, a rebuilt blog environment that keeps visitors on-site, and clear pathways toward program inquiries and contact.

Two additional constraints shaped the build in ways that aren’t common:

• The first was accessibility. The brand colors provided didn’t meet WCAG contrast standards for web use. The production team recalibrated the palette to bring it into compliance while preserving the intent of the new brand identity.
• The second was the language issue. Developing copy for an organization serving people with disabilities required deliberate decisions about what to say, what to avoid, and how to handle the gap between preferred organizational terminology and the search terms families actually use. That conversation happened explicitly during the engagement and shaped both the site’s structure and its copy.

The engagement also included a domain transition. The previous site lived under the organization’s former name. Ensuring that all existing pages redirected correctly to their counterparts on the new site was the final technical requirement before launch.

The Outcome

The organization launched on its target date with a new website, a new brand, and a HubSpot instance that reflects how the organization actually operates. Marketing emails now go out through HubSpot, replacing a legacy tool the team had outgrown. Contacts from all program areas are segmented automatically on import. The website and marketing platform sit under one roof for the first time. And the property framework already in place will support a future API integration when the organization’s internal database consolidation is complete.

What This Tells Us

A contact migration almost always has a data architecture problem underneath it. Moving records from one platform to another without understanding the organizational structure behind them doesn’t solve anything—it relocates the problem. The real work here was building HubSpot to reflect how this organization actually functions, so the platform could serve them rather than requiring constant manual intervention to compensate for missing structure.

The same is true of website builds in sensitive sectors. Accessibility and terminology aren’t edge cases to handle after the fact. They shape how the work gets scoped, how copy gets written, and what constitutes a successful launch.

Working through a migration that’s more complicated than it first appeared? We’ve built HubSpot data architectures for organizations where the contact structure is as complex as the work itself. Let’s talk through what you’re dealing with.