Skip to main content
PYRAMYD
Resources

Migration Guide · Competitive Intelligence

Crayon → PYRAMYD. How the move works.

Sellers ask questions that join a competitor to your product, the buyer's role, and the deal stage. PYRAMYD answers them from one place where your product, competitors, customers, and deals already sit together. This is the playbook for the move.

Step-by-step planGuided move, with our helpHighspot and Seismic connectorsStarter: Workspace + one hub
Start the migration callRead why battlecards belong next to your product

Why teams move

Teams move so product, marketing, and sales work from one set of evidence: battlecards built from your product, the rival's, and your deals, and rebuilt when you ask. The steps match the Klue guide. Crayon-specific notes below.

The timeline

Four weeks. Four phases.

Assumes an existing Crayon deployment with 5-9 active battlecards out of up to 25 tracked competitors, 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, and Track each one from Competitors › Discover
  • Map your category coverage to PYRAMYD's 2,546 product categories (Markets › Categories)
  • Joint scoping with PYRAMYD design-partner success team

Week 2 · Library port

  • Save your Crayon battlecards as Word files and import them into Workspace › Studio › Documents (Ctrl+K, then Import document…), so your hand-written positioning stays on file
  • Generate a first card per competitor in Competitors › Battlecards › New Battlecard, and attach the right competitor, product, customer, and deal nodes in its Context Manager
  • Connect Salesforce or HubSpot in Workspace › Library › Connectors and choose Sync now, so a battlecard can be built for a linked deal
  • Train 3-5 CI power users on asking APEX about competitors and deals

Week 3 · Cutover to PYRAMYD battlecards

  • Refresh the signals of your 25 tracked competitors on demand (Run now in Workspace › Signals › Sources): releases, pricing, hiring, and press
  • Build the PYRAMYD battlecard for the most-deployed competitor; compare it with the Crayon card
  • Side-by-side AE test: same deal-stage question in Crayon and PYRAMYD; compare recency + citations

Week 4 · Cutover + Crayon sunset

  • Build the remaining named-competitor battlecards with Bulk Generate in Competitors › Battlecards › All, then review each one
  • Disable Crayon auto-publish into enablement stack (Highspot / Seismic / wikis)
  • Cancel Crayon at your next renewal date, under your contract's notice terms
  • 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

RFP answers drafted from your product's data, next to the deal.

Migration

Highspot → PYRAMYD

Enablement content on the graph.

Ready to start the cutover?

Start the migration callSee the CI use case