Skip to main content
PYRAMYD
Resources

Migration Guide · Sales Enablement

Highspot → PYRAMYD. How the move works.

Sellers need answers that join the buyer, the persona, the competitor, the category, and your product. PYRAMYD connects them for every deal, so battlecards and RFP answers come from the same evidence as the rest of your go-to-market work.

Step-by-step planHighspot connectorSalesforce and Gong connectorsStarter: Workspace + one hub
Start the migration callRead why enablement belongs next to your product

Why teams move

A content library stores what was written. Sellers need the competitor, the persona, the category, your product, and the deal stage in one answer, and PYRAMYD connects them.

Same migration pattern applies to Seismic.

The timeline

Four weeks. Four phases.

Assumes an existing Highspot or Seismic deployment with a typical Salesforce + Gong + Outreach integration footprint, plus active product marketing and sales teams.

Week 1 · Discovery

  • Export Highspot content library · spots, pitches, playbooks, plays, owner mapping
  • Inventory current Highspot integrations · Salesforce, Gong, Outreach, Microsoft Teams
  • Identify the 3 highest-revenue content surfaces where graph grounding pays back fastest (typically: battlecards, RFP responses, deal-stage briefings)
  • Joint scoping with PYRAMYD design-partner success team

Week 2 · Content port

  • Connect Highspot in Workspace › Library › Connectors and choose Sync now to bring in your spots, items, pitches, and plays
  • Generate a battlecard per rival in Competitors › Battlecards › New Battlecard, and attach the competitor, product, customer, and deal nodes in its Context Manager
  • Connect Salesforce so battlecards can be built for a specific deal. Gong connects too, but call content does not feed battlecards yet
  • Train 3-5 enablement power users to build battlecards and comparisons from the graph and share them with sellers

Week 3 · Parallel test

  • Pick a deal-stage moment (discovery, demo prep, RFP response, close). Run it through both Highspot and PYRAMYD in parallel
  • Compare: content recency, citation count, relevance to the specific deal context
  • Give AEs the battlecard for the rival in each deal. With a personal access token (Settings › Workspace › API) they can also look it up from Claude Desktop, Cursor, ChatGPT, or Microsoft 365 Copilot
  • Load your approved answers into the Answers library (Accounts › Opportunities › Answers) so first drafts start from your team's own wording, then review the first round together

Week 4 · Cutover + Highspot sunset

  • Rebuild the remaining active spots and pitches as battlecards or Studio documents
  • Point sellers to PYRAMYD battlecards by tracked share link, and read who opened each one in Usage and readers
  • Cancel Highspot at your next renewal date, under your contract's notice terms
  • QBR alignment: Sales + Enablement on the new substrate; baseline 30-60-90 day content-usage + win-rate KPIs

Adjacent migrations

Other moves teams make to PYRAMYD.

Migration

Klue → PYRAMYD

CI on the graph. Battlecards rebuilt whenever you ask.

Migration

Loopio → PYRAMYD

RFX on the same graph as your competitive data.

Migration

Crayon → PYRAMYD

Battlecards built from your product, the rival's, and your deals. Same library port, same step-by-step plan.

Ready to start the cutover?

Start the migration callSee the Sales Enablement use case