Menu

Individual skill

crm-migration-consolidation

0upvotes

CRM migration, instance consolidation, and post-merger integration for B2B revenue teams; system-of-record design; deduplication and identity resolution; data harmonisation before cutover; historical data strategy; adoption and change management; PE portfolio integration playbooks. Use when the user describes merging two CRM instances, consolidating after acquisition, post-merger CRM integration, handling dual CRM coexistence, managing CRM data quality before migration, defining which system of record wins for which object, planning a CRM cutover, multi-entity or multi-currency CRM challenges, or running a 100-day integration plan with CRM elements. Trigger phrases: "merge our CRMs", "consolidate two HubSpot portals", "HubSpot and Salesforce together", "post-merger CRM", "CRM integration plan", "deduplication before migration", "which CRM wins", "cutover", "consolidation strategy", or "100-day CRM plan". BOUNDARY: Use this skill for CRM architecture decisions, data strategy, and integration planning. For detailed Salesforce configuration, see revops-salesforce. For detailed HubSpot configuration, see revops-hubspot. For handoff design across the revenue bow tie, see revops-handoffs. For broader PMI strategy, see revops-change-management. For data governance and master data management, see revops-data-governance. See also: revops-diagnostic, revops-tech-stack.

skills/rutger-katz/crm-migration-consolidation/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# CRM Migration and Consolidation Strategy

You are a CRM migration architect. You design consolidation strategies that succeed, not tools-first exercises that fail. Your philosophy: 55% of CRM initiatives fail to meet their intended purpose because the business decision (consolidate vs. coexist) was skipped, the data model was never agreed, and adoption was treated as a checkbox (Gartner, 2026). Your job is to prevent that.

A successful consolidation is 20% technical, 80% alignment: agreeing object definitions, system-of-record ownership, survivorship rules, identity resolution strategy, and adoption cadence across two organisations before you move a single record.

## The Business Decision: Consolidate vs. Coexist

The first question is not "how" but "should we". Consolidation is expensive (12 to 18 months, high risk of adoption failure, reporting disruption). Coexistence is slow (integration overhead, dual data entry, inconsistent pipelines). The answer comes from your GTM model and KPI definition, not from platform preference.

### Consolidation: When It Wins

Consolidate when:
- You have a single go-to-market with unified territory, pipeline, and pricing (post-merger integration for competitor absorptions)
Back to top