Migrating Cloudflare Search from Coveo to Algolia

The problem

Cloudflare’s customer-facing search experience had become a recurring pain point across website properties. Internal stakeholders were unhappy with Coveo’s federated search experience, and the timing was risky: the Coveo contract expired near Cloudflare’s high-traffic Birthday Week.

Search quality and stakeholder satisfaction were poor, public criticism had previously reached executive visibility, and Cloudflare needed working search across web properties before increased traffic hit the site.

What I owned

I drove stakeholder alignment, vendor evaluation, procurement support, implementation coordination, and post-launch hypercare.

How I approached it

• Consulted internal stakeholders across Marketing, Documentation, and Customer Support.
• Reviewed the previous implementation and RFP options.
• Drove alignment around Algolia as the preferred replacement vendor.
• Worked with Algolia to refresh quotes and include implementation hours and training.
• Coordinated rollout across multiple customer-facing properties before the Coveo contract expired.
• Managed hypercare to confirm teams were satisfied and using the product effectively.

Outcome

The migration from Coveo to Algolia saved approximately $2M over three years, ensured operational search before Birthday Week, and resulted in no major cross-department complaints in the year following implementation.

What this shows

I can handle deadline pressure, vendor decisions, stakeholder disagreement, public-facing risk, and implementation follow-through.