Houghton Mifflin Harcourt

For a school district, changing the identity platform is not a background infrastructure swap. The transition has to preserve a dependable route into the learning systems people already use.

At HMH, I was an early contributor who led implementation of an identity-platform migration for a school district.

I chose event-driven synchronization for identity changes instead of polling downstream state or coupling the provisioning path directly to every consumer. That kept the migration paths separable, while security-sensitive deprovisioning required stronger handling than ordinary profile changes.

I built provisioning services that interacted with an identity platform and emitted identity-change events for downstream consumers. The mechanism covered creation, updates, and deprovisioning without exposing customer-specific architecture or proprietary identifiers.

The integration supported a gradual cutover in which migration paths could coexist during the transition, rather than requiring every dependent system to change in one step.

A district identity migration was implemented with downstream synchronization carried by identity-change events.

The consistency guarantee should follow the consequence of delay. Eventual consistency can be reasonable for ordinary profile changes; deprovisioning deserves stronger, explicitly verified treatment because stale access is a security condition, not merely stale data.