Skip to main content
PYRAMYD
Resources

Migration Guide · Competitive Intelligence

Crayon → PYRAMYD. 30-day cutover.

Crayon stores signals; sales asks multi-entity questions. The gap between document-centric CI and graph-grounded CI shows up the moment a question requires joining two facts that live in different documents. This is the 30-day playbook for moving onto a graph substrate.

30-day cutoverLibrary imports cleanlyHighspot / Seismic compatibleFrom $50K/yr
Start the migration callRead the CI substrate argument

Why teams move

The migration playbook is functionally identical to the Klue cutover · same library export pattern, same enablement-tool connectors, same 30-day timeline. We've run both with design partners. Crayon-specific notes below.

The 30-day timeline

Four weeks. Four phases.

Assumes existing Crayon deployment with 5-9 active named-competitor battle cards and a Salesforce + Highspot / Seismic integration footprint.

Week 1 · Discovery

  • Export Crayon competitor list, battle cards, stakeholder roster, and content tags
  • Identify which 25 named competitors hurt deals most · anchor migration around those
  • Map your category coverage to PYRAMYD's 2,606 live Product Categories
  • Joint scoping with PYRAMYD design-partner success team

Week 2 · Library port

  • Import Crayon battle-card library (CSV / JSON / API)
  • Tag library content against graph entities: competitor, product, capability, category
  • Wire Salesforce / HubSpot push so battle cards surface in deal stages where they currently surface in Crayon
  • Train 3-5 CI power users on graph-grounded query patterns

Week 3 · Live graph cutover

  • Activate live signal feed across your 25 named competitors · releases, pricing, hiring, press, reviews
  • Build the first graph-grounded battle card for the most-deployed competitor; compare to Crayon source
  • Wire Slack alerts for material competitor changes (replaces Crayon newsfeed)
  • Side-by-side AE test: same deal-stage question in Crayon and PYRAMYD; compare recency + citations

Week 4 · Cutover + Crayon sunset

  • Migrate remaining named-competitor battle cards (typically 5-9 active cards per Crayon deployment)
  • Disable Crayon auto-publish into enablement stack (Highspot / Seismic / wikis)
  • Cancel Crayon renewal at next contract date · typical 30-day notice clause
  • QBR alignment: Sales + CI + Product Marketing on the new substrate; measure 30-60-90 day deal-stage win lift

Adjacent migrations

If you're moving off Crayon, you might be moving off others too.

Migration

Klue → PYRAMYD

Same CI substrate. Same library port. Same 30-day cutover.

Migration

Loopio → PYRAMYD

Sales Enablement / RFX substrate change · graph-grounded answer composition.

Migration

Highspot → PYRAMYD

Enablement content substrate change. Same Salesforce push, graph-grounded retrieval.

Ready to start the cutover?

Start the migration callSee the CI use case