Skip to main content
PYRAMYD
Resources

Migration Guide · Competitive Intelligence

Crayon → PYRAMYD. How the move works.

Crayon stores signals; sales asks multi-node 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 playbook for moving onto the graph.

Step-by-step planGuided move, with our helpHighspot / Seismic compatibleFree to start
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 timeline. Crayon-specific notes below.

The timeline

Four weeks. Four phases.

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

Week 1 · Discovery

  • Export Crayon competitor list, battlecards, 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,546 live Product Categories
  • Joint scoping with PYRAMYD design-partner success team

Week 2 · Library port

  • Import Crayon battlecard library (CSV / JSON / API)
  • Tag library content against graph nodes: competitor, product, capability, category
  • Connect Salesforce or HubSpot so battlecards are built with your deal context
  • Train 3-5 CI power users on graph-grounded query patterns

Week 3 · Live graph cutover

  • Add your 25 named competitors to a watchlist and refresh their signals — releases, pricing, hiring, press, reviews
  • Build the first graph-grounded battlecard for the most-deployed competitor; compare to Crayon source
  • 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 battlecards (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 step-by-step plan.

Migration

Loopio → PYRAMYD

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

Migration

Highspot → PYRAMYD

Enablement content on the graph.

Ready to start the cutover?

Start the migration callSee the CI use case