# HubSpot CRM Migration: How to Move Your Data Safely

> Migrate from HubSpot without losing data or history. Coffee's guide covers export, mapping, import, and validation. Start your migration today.

**Published:** 2026-09-04 | **Updated:** 2026-10-17 | **Author:** coffee
**URL:** https://www.coffee.ai/articles/hubspot-export-data-to-crm/
**Type:** post

**Categories:** CRM Migration

![HubSpot CRM Migration: How to Move Your Data Safely](https://www.coffee.ai/articles/wp-content/uploads/sites/10/2026/09/1787391681742-4f7c43b5c218-1024x572.webp)

---

## Content

*Written by: Doug Camplejohn, CEO & Co-Founder, Coffee*

## Key Takeaways for Your HubSpot Migration

- HubSpot-to-CRM migrations fail 30–55% of the time because of poor data quality, missing associations, and incomplete activity history.
- Native exports miss critical data. Associations, engagements, attachments, and lifecycle history require API access or third-party tools.
- Successful migrations follow a strict dependency order: Companies → Contacts → Deals → Activities, with careful pre-import mapping and deduplication.
- Post-migration validation and 90-day monitoring protect against data regression and keep record integrity high.
- Coffee’s Agent removes the need for migration by automating data entry and preserving full history — [see how Coffee preserves your data without migration](https://www.coffee.ai/pricing?utm_source=ai-growth-agent&utm_term=hubspot-export-data-to-crm).

## Why HubSpot-to-CRM Migrations Fail So Often

CRM failure rates sit between 30% and 55%, with poor data quality and weak cross-functional ownership as leading causes. Industry research attributes migration failures to poor data quality (34%), weak user adoption (43%), and insufficient training (22%).

The financial impact is direct. [Validity’s survey](https://www.validity.com/resource-center/the-state-of-crm-data-health-in-2022-report/) found that 44% of organizations lose over 10% in annual revenue due to low-quality CRM data, with many reporting specific revenue loss tied to data failures. The same survey shows CRM users spend significant time each week searching for basic information they do not trust.

Activity history such as emails, calls, and notes, along with file attachments, are among the hardest data types to move between CRMs. Many systems do not export activity logs cleanly, and native importers often exclude attachments entirely. Sales productivity can drop noticeably for several weeks post-migration as reps learn the new system, and that cost grows when the underlying data arrives incomplete.

## Readiness Checklist Before You Export Anything

These failure modes are preventable. The difference between a 30% failure rate and a successful migration comes from readiness and confirming key prerequisites before you export a single record.

Before exporting a single record, confirm the following prerequisites are in place:

- **Admin access in HubSpot:** Super Admin permissions are required to export all objects, access the Associations API, and retrieve GDPR consent fields. Without this access, you cannot pull the engagement and association data described in Phase 1.
- **Provisioned target CRM account:** The destination environment, such as a Salesforce sandbox, Pipedrive trial, or Zoho sandbox, must be configured with matching pipelines, picklist values, and custom fields before any import begins. This configuration lets you validate field mappings during the shadow import in Phase 4.
- **Named data owner:** [Assigning a single data quality owner for the first 90 days post-cutover](https://datamagnet.co/post/prevent-data-quality-regression-after-crm-migration) is a documented success factor for preventing regression. This person monitors the validation targets in Phase 4 and triages any data quality issues during stabilization.
- **Realistic timeline:** A realistic 2026 CRM implementation timeline is 2–4 weeks for small teams (under 15 users) and 6–12 weeks for mid-market teams (15–60 users), with data migration as the longest phase, not the 4-week estimates vendors often quote. Those shorter estimates usually exclude the data cleanup work that prevents the 30–55% failure rates described earlier.

## Phase 1: Decide What Must Migrate From HubSpot

Native HubSpot exports cover far less than most teams expect. HubSpot’s native UI export produces flat CSVs of Contacts, Companies, Deals, and Tickets but excludes association data, because associations live in a separate graph layer rather than inside object records.

Before you begin any export, audit your instance to see whether you need API-only data types. If any of the following are critical to your sales process, you will need API access or a third-party migration tool, because the standard export dialog cannot retrieve them:

- **Engagement records** (logged calls, emails, meetings, notes, tasks, form submissions): [stored in HubSpot’s separate timeline and require the Engagements API endpoint GET /crm/v3/objects/engagements](https://resources.rework.com/guides/data-migration/exporting-from-hubspot)
- **Full association graph** (contact-to-company, contact-to-deal, deal-to-company, many-to-many): [requires the Associations API endpoints including GET /crm/v4/associations/contacts/companies/batch/read](https://resources.rework.com/guides/data-migration/exporting-from-hubspot)
- **Custom object records and relationships:** [excluded from native UI export and must be retrieved via GET /crm/v3/objects/{customObjectType}](https://resources.rework.com/guides/data-migration/exporting-from-hubspot)
- **File attachments:** [never included in native exports, require the Files API with the files.ui_hidden.read scope to generate signed URLs](https://clonepartner.com/blog/how-to-export-data-from-hubspot-service-hub-methods-api-limits)
- **Lifecycle stage history:** [HubSpot stores only the current value and does not retain historical changes](https://resources.rework.com/guides/data-migration/exporting-from-hubspot)
- **GDPR consent fields:** [not included in default export columns and must be explicitly selected](https://resources.rework.com/guides/data-migration/exporting-from-hubspot)

Many CRMs contain dead weight such as duplicates, bounced emails, test contacts, and archived deals. Migrating this data pollutes the new system. Exclude records with under 20% field-fill rates and limit deal history to the last 24 months of closed deals plus all open deals.

## Phase 2: Export from HubSpot Without Losing History

For each standard object, including Contacts, Companies, Deals, and Tickets, go to the object index in HubSpot, select all records, and choose **Export**. Select CSV format and include all properties. Repeat this process for each object separately.

**Critical callout:** [Omitting the HubSpot Record ID from any export intended for later re-import causes duplicate records rather than updates during migration.](https://skyvia.com/blog/hubspot-export-csv-guide) Always include Record ID. HubSpot also imposes rate limits for the in-app export tool and the CRM Exports API on paid accounts, which can slow large or repeated migrations. Plan export batches with these limits in mind.

[HubSpot native CSV exports capture only current field values and do not include property history](https://skyvia.com/blog/hubspot-export-csv-guide). Full historical data requires the CRM Exports API. [Without the sales-email-read scope, HubSpot API responses for email engagements silently redact the email body content with no error or warning returned](https://clonepartner.com/blog/how-to-export-data-from-hubspot-service-hub-methods-api-limits). Verify scope permissions before running engagement exports.

Once you have clean exports with all required data types, the next risk point is the mapping layer, where you translate HubSpot’s field structure into your destination CRM schema.

## Phase 3: Map and Clean Your Data Before Import

Field mapping is the phase where data loss often occurs. Build a mapping spreadsheet before you touch the import tool so you can see every field decision in one place.

The table below shows how HubSpot’s core objects map to equivalent objects in Salesforce, Pipedrive, and Zoho. Use these mappings as a starting point, then add custom field mappings specific to your instance.

| HubSpot Object | Salesforce Destination | Pipedrive Destination | Zoho Destination |
| --- | --- | --- | --- |
| Contact | Lead or Contact (route by lifecycle stage) | [Person](https://leadflowguide.com/en/use-cases/hubspot-pipedrive-integration-migration) | Lead or Contact |
| Company | Account | [Organization](https://leadflowguide.com/en/use-cases/hubspot-pipedrive-integration-migration) | Account |
| Deal | Opportunity | [Deal](https://leadflowguide.com/en/use-cases/hubspot-pipedrive-integration-migration) | Deal |
| Engagement (call, email, note, meeting) | Task or Event | Activity | Activity |

These mappings highlight a key decision point. In Salesforce, HubSpot Contacts can become either Leads or Contacts depending on lifecycle stage, while Pipedrive and Zoho use simpler one-to-one mappings.

[Dropdown and picklist values must match exactly, including capitalization, or the sync will fail for that field.](https://vantagepoint.io/blog/sf/integrations/hubspot-salesforce-sync-rules-field-mappings) Standardize date formats to ISO 8601 (YYYY-MM-DD) across all files before import so the destination system parses dates consistently.

Run deduplication on the exported files before import to avoid carrying duplicates into the new CRM. [Normalize emails (lowercased, display names and plus-tags stripped), phones (country codes, dashes, and parentheses removed), and domains (protocol, www, and trailing slash stripped) before applying match logic.](https://mapsleads.co/blog/crm-deduplication-best-practices) Exact-key matching alone can miss many real duplicates. Apply fuzzy matching within high-confidence buckets at a 95% or higher similarity threshold for auto-merge.

[Cleaning CRM data before migration costs 3–10× less than cleaning after migration](https://www.digitalapplied.com/blog/crm-data-migration-checklist-2026-zero-downtime-playbook), because post-migration cleaning requires untangling data from new workflows, automations, and reports. This cost gap is why the deduplication and normalization steps above are non-negotiable. Every duplicate or malformed record you import becomes far more expensive to fix once it connects to automation.

[Skip the mapping spreadsheets entirely](https://www.coffee.ai/pricing?utm_source=ai-growth-agent&utm_term=hubspot-export-data-to-crm) — Coffee’s agent keeps your CRM clean automatically and removes most of the manual deduplication and normalization work.

## Phase 4: Import and Validate in the Right Order

Import order directly affects relationship integrity. [CRM data is inherently relational and needs dependency-ordered loading to preserve every organization-to-contact-to-deal relationship.](https://clonepartner.com/blog/paazl-pipedrive-to-freshsales-case-study) The correct sequence is:

1. Companies / Accounts (parent objects must exist before child records reference them)
2. Contacts / Persons (linked to companies via normalized domain or ID)
3. Deals / Opportunities (linked to both contacts and companies)
4. Activities / Engagements (linked to deals and contacts last)

Note that step 4, Activities, carries a critical technical constraint.

**API throttling callout:** [Activities such as notes, calls, meetings, and tasks cannot be imported into HubSpot via CSV and require the Engagements API with dedicated endpoints for each type plus explicit typed association IDs.](https://clonepartner.com/blog/pipedrive-to-hubspot-migration-data-mapping-apis-rate-limits) Batch API calls and monitor rate-limit headers to avoid silent failures.

Run a shadow import of 500–1,000 records in a sandbox environment before cutover. [Post-import QA for relationship integrity requires opening 20 contact records to verify company associations, 10 deal records to verify contact associations, and at least 3 deal records to confirm correct deal owner assignment.](https://resources.rework.com/vi/guides/data-migration/shadow-import-testing)

Use clear validation targets so your team knows when the migration is safe to sign off:

- [Greater than 99% data accuracy via field-level spot checks](https://vantagepoint.io/blog/sf/crm-data-migration-best-practices-guide)
- [Greater than 98% record completeness via source-to-target count comparison](https://vantagepoint.io/blog/sf/crm-data-migration-best-practices-guide)
- Duplicate rates below 5%
- [Record counts matching expected totals within 0.5%, zero unresolved field type errors, and lifecycle stage null rate below 1%](https://resources.rework.com/vi/guides/data-migration/shadow-import-testing)

[Active daily or weekly monitoring for the first 90 days after CRM cutover](https://datamagnet.co/post/prevent-data-quality-regression-after-crm-migration) is recommended, with parallel system operation for the first 2–4 weeks providing the highest data integrity rates, followed by ongoing automated verification.

At this point, you have completed the technical migration. Before you move to full team rollout, consider whether the migration solved your core problem or simply moved low-quality data into a new system.

## Skip the Migration: Let an Agent Handle Data Entry Instead

The four-phase process above is correct, but it is also expensive, slow, and structurally prone to association loss. An alternative approach removes the migration entirely.

Coffee’s Agent operates in two modes. As a **Companion App**, it sits on top of an existing HubSpot instance and automates the “data in” process. It auto-creates contacts and companies from emails and calendars, logs every call and meeting, enriches records with job titles and funding data, and writes structured summaries back to HubSpot without human input. Teams that adopt the Companion App stop accumulating the data debt that makes migrations necessary.

[](https://www.coffee.ai/pricing?utm_source=ai-growth-agent&utm_term=hubspot-export-data-to-crm)**Building a company list with Coffee AI**

As a **Standalone CRM**, Coffee’s Agent replaces HubSpot entirely for small to mid-market teams. It ingests structured and unstructured data such as emails, call transcripts, and calendar events into a built-in data warehouse that preserves full history. There are no flat CSV exports, no association graph to reconstruct, and no 90-day stabilization period. The Agent handles deduplication, enrichment, activity logging, and pipeline tracking continuously.

[](https://www.coffee.ai/pricing?utm_source=ai-growth-agent&utm_term=hubspot-export-data-to-crm)**Build people lists automatically with Coffee AI CRM Agent**

For RevOps leads considering a migration mainly because HubSpot data quality has degraded, the root cause is manual entry rather than the platform itself. Switching CRMs without addressing that root cause recreates the same problem in a new system. Coffee’s Agent addresses the root cause directly by removing manual data entry.

[](https://www.coffee.ai/pricing?utm_source=ai-growth-agent&utm_term=hubspot-export-data-to-crm)**Automated meeting prep with Coffee AI CRM Agent**

[Deploy Coffee as a Companion or standalone CRM](https://www.coffee.ai/pricing?utm_source=ai-growth-agent&utm_term=hubspot-export-data-to-crm) — the Agent handles data entry automatically, whether you keep HubSpot or replace it.

[](https://www.coffee.ai/pricing?utm_source=ai-growth-agent&utm_term=hubspot-export-data-to-crm)**Create instant meeting follow-up emails with the Coffee AI CRM agent**

## Migration Timelines by Team Size

**Small teams (under 10,000 records):** A small CRM migration under 25,000 records with standard objects and limited integrations can be completed in 4–6 weeks. Native CSV exports are sufficient for contacts, companies, and deals, while engagements still require API access. Shadow import testing in a free trial environment fits within this timeline and reduces risk.

**Mid-market teams (50,000–200,000 records):** [A mid-market CRM migration involving 50K–200K records, custom objects, and multiple integrations typically takes 4–12 weeks end-to-end.](https://resources.rework.com/guides/choosing-software/crm-migration-guide) Manual field mapping and rebuilding associations can consume several weeks. Automated migration tooling such as Airbyte, Fivetran, or SyncMatters can shorten both timelines and reduce manual effort.

**Enterprise considerations:** Enterprise CRM migrations with complex custom objects, large datasets, and many integrated systems can run 4–9 months. Mid-market migrations already require weeks of work and significant costs for architecture redesign and training. Enterprise scope multiplies both the time and the cost.

## Frequently Asked Questions

### Who owns the migration project?

A named data owner, typically the RevOps lead or Head of Sales, should hold accountability for the full migration lifecycle. This lifecycle includes audit, cleanup, field mapping, import sequencing, validation, and the 90-day post-cutover monitoring period. Without a single owner, decisions about deduplication rules, field mapping conflicts, and go or no-go cutover criteria often get deferred until they become emergencies. The data owner should also define the RACI matrix for the project, assigning specific responsibilities to IT or admin for API access and sandbox configuration, sales leadership for UAT sign-off, and individual contributors for data quality spot checks.

### How long does a typical HubSpot export take?

The export itself, which involves clicking through the HubSpot UI and downloading CSVs, takes hours rather than days. The time-consuming phases sit around that step. Auditing and cleaning the data before export, then mapping, deduplicating, and validating after import, consume most of the schedule. The cleansing phase is usually the longest part of any CRM migration regardless of record volume. The timelines outlined in the Readiness Checklist, which show 2–4 weeks for small teams and 6–12 weeks for mid-market teams, assume you have completed data cleanup before export.

### Is my data secure during export and import?

HubSpot delivers native CSV exports through emailed download links, which introduces compliance risk because files containing PII, deal values, and personal notes pass through email systems. For organizations subject to GDPR or SOC 2 requirements, this route conflicts with most compliance frameworks. API-based exports that write directly to encrypted storage provide a safer option. During import, ensure the destination CRM is SOC 2 Type 2 certified and that data in transit is encrypted via TLS 1.2 or higher. As noted in Phase 3, GDPR consent fields require explicit selection during export and must be mapped to equivalent consent fields in the destination system. Coffee is SOC 2 Type 2 and GDPR compliant, and data processed by the Coffee Agent is not used to train public models.

### Can I roll back if the new CRM import fails?

A rollback is only possible if the source system remains intact and a full backup export exists from before cutover. Never decommission HubSpot or revoke user access until post-import validation is complete and signed off by both sales leadership and IT or admin. As noted in Phase 4, running both systems in parallel for 2–4 weeks is the most reliable approach, with contractors reporting 90% or higher data integrity compared to 65% for cold-switch migrations. Keep the HubSpot export files, including the Record ID column, stored in a secure location for at least 90 days post-cutover. CRM merge actions are irreversible, so the export is the only recovery mechanism if deduplication or import errors corrupt records in the destination system.

## Conclusion: Choose the Path That Fits Your Stack

A successful HubSpot-to-CRM migration follows a dependency-ordered sequence. You audit and decide what must migrate, export objects and engagements via both native UI and API, map and deduplicate before any record touches the destination, import in companies-first order, and validate associations and field values against the source before granting user access. Each phase has documented failure modes, including association loss, truncated notes, broken relationships, and timestamp overwrites, and each one needs deliberate mitigation.

For teams whose core problem is data quality rather than platform capability, migration may not be the right answer. Coffee’s Agent removes the manual data entry that degrades CRM data in the first place, operating either as a Companion App on top of HubSpot or as a Standalone CRM that replaces it. There are no CSVs to merge, no association graphs to reconstruct, and no 90-day stabilization periods.

[Let Coffee’s Agent handle your CRM data](https://www.coffee.ai/pricing?utm_source=ai-growth-agent&utm_term=hubspot-export-data-to-crm) — so your team can focus on revenue instead of migration spreadsheets.

## Read Next

- [How to Migrate from HubSpot CRM: An 8-Step Playbook](https://coffee.ai/articles/crm-migration-from-hubspot/)
- [How To Migrate From HubSpot: 2026 Export & Re-Import Guide](https://coffee.ai/articles/how-to-migrate-from-hubspot/)
- [Salesforce To HubSpot Migration: Complete Step-By-Step Guide](https://coffee.ai/articles/salesforce-to-hubspot-migration/)
- [How To Migrate From Salesforce: A Decision-First Playbook](https://coffee.ai/articles/migrate-from-salesforce-crm/)
- [How To Fix Missing CRM Data In HubSpot: A Recovery Playbook](https://coffee.ai/articles/fix-missing-crm-data-hubspot/)

---

## Structured Data

**@graph:**

  **FAQPage:**

  **MainEntity:**

    **Question:**

    - **Name:** Who owns the migration project?
      **Answer:**

      - **Text:** A named data owner, typically the RevOps lead or Head of Sales, should hold accountability for the full migration lifecycle. This lifecycle includes audit, cleanup, field mapping, import sequencing, validation, and the 90-day post-cutover monitoring period. Without a single owner, decisions about deduplication rules, field mapping conflicts, and go or no-go cutover criteria often get deferred until they become emergencies. The data owner should also define the RACI matrix for the project, assigning specific responsibilities to IT or admin for API access and sandbox configuration, sales leadership for UAT sign-off, and individual contributors for data quality spot checks.
    **Question:**

    - **Name:** How long does a typical HubSpot export take?
      **Answer:**

      - **Text:** The export itself, which involves clicking through the HubSpot UI and downloading CSVs, takes hours rather than days. The time-consuming phases sit around that step. Auditing and cleaning the data before export, then mapping, deduplicating, and validating after import, consume most of the schedule. The cleansing phase is usually the longest part of any CRM migration regardless of record volume. The timelines outlined in the Readiness Checklist, which show 2–4 weeks for small teams and 6–12 weeks for mid-market teams, assume you have completed data cleanup before export.
    **Question:**

    - **Name:** Is my data secure during export and import?
      **Answer:**

      - **Text:** HubSpot delivers native CSV exports through emailed download links, which introduces compliance risk because files containing PII, deal values, and personal notes pass through email systems. For organizations subject to GDPR or SOC 2 requirements, this route conflicts with most compliance frameworks. API-based exports that write directly to encrypted storage provide a safer option. During import, ensure the destination CRM is SOC 2 Type 2 certified and that data in transit is encrypted via TLS 1.2 or higher. As noted in Phase 3, GDPR consent fields require explicit selection during export and must be mapped to equivalent consent fields in the destination system. Coffee is SOC 2 Type 2 and GDPR compliant, and data processed by the Coffee Agent is not used to train public models.
    **Question:**

    - **Name:** Can I roll back if the new CRM import fails?
      **Answer:**

      - **Text:** A rollback is only possible if the source system remains intact and a full backup export exists from before cutover. Never decommission HubSpot or revoke user access until post-import validation is complete and signed off by both sales leadership and IT or admin. As noted in Phase 4, running both systems in parallel for 2–4 weeks is the most reliable approach, with contractors reporting 90% or higher data integrity compared to 65% for cold-switch migrations. Keep the HubSpot export files, including the Record ID column, stored in a secure location for at least 90 days post-cutover. CRM merge actions are irreversible, so the export is the only recovery mechanism if deduplication or import errors corrupt records in the destination system.

  **SoftwareApplication:**

  - **Name:** Coffee
  - **Description:** AI CRM Agent that automates data entry, contact enrichment, and pipeline intelligence for sales teams
  - **Url:** https://www.coffee.ai
  - **ApplicationCategory:** BusinessApplication
    **Brand:**

    - **Name:** Coffee
  **Offers:**

    **Offer:**

    - **Url:** https://www.coffee.ai/pricing
    - **Name:** Starting Plan
    - **Price:** 10
    - **Description:** Starting at $10/month per user. 14-day free trial available, no credit card required.
    - **PriceCurrency:** USD

    **Audience:**

    - **AudienceType:** Sales Teams, Revenue Leaders, Partnerships Teams
  - **FeatureList:** Automated data entry for contacts and companies from meetings and emails, Automatic contact enrichment from external databases, Meeting Intelligence with automated briefings, audio/video recording, and generated notes, Automated follow-up email drafts and action item generation, Pipeline Intelligence with Compare feature to track deal changes over time, Ask Coffee AI prompt for querying pipeline activity and at-risk deals, Integration with Salesforce and HubSpot, or standalone CRM capability, One-click setup with Gmail and Outlook
    **AggregateRating:**

    - **RatingValue:** 4.8
    - **ReviewCount:** 127
  - **OperatingSystem:** Web
  - **MainEntityOfPage:** https://www.coffee.ai/
  **BlogPosting:**

  - **Headline:** HubSpot CRM Migration: How to Move Your Data Safely
  - **Description:** Migrate from HubSpot without losing data or history. Coffee's guide covers export, mapping, import, and validation. Start your migration today.
  - **DateModified:** 2026-08-22T09:40:56.647Z
  - **Image:** https://cdn.aigrowthmarketer.co/1763678641499-bad085f8165f.gif, https://cdn.aigrowthmarketer.co/1763678186019-5cc1a76ac78e.gif, https://cdn.aigrowthmarketer.co/1763678549697-4e8d65abe17d.gif, https://cdn.aigrowthmarketer.co/1763678321672-5c8717cf0024.gif
  - **InLanguage:** en-US
    **Person:**

    - **Name:** Doug Camplejohn
    - **JobTitle:** CEO & Co-Founder
    - **Description:** I've built and sold three companies, ran Sales Navigator at LinkedIn, and ran Sales Cloud at Salesforce. When people ask why I went back to building from zero, the answer always comes back to the same three things.nnThe first was the pain. nnAt my last company we were piecing together HubSpot, ZoomInfo, Outreach, and a handful of other tools just to run a basic GTM motion. I kept thinking, this is still a shit show. Every tool in its own silo, data that never lines up, more time spent gluing things together than actually selling. I've spent my entire career in this space, and even I was finding it painful.nnThe second was timing. nnEvery tool in that stack was built B.C. (before ChatGPT.) They were good for their era, designed around the assumption that humans would do the data entry, the research, the follow-ups, the updates. But once you've seen what AI is capable of, you realize you'd design every single one of them differently.nnThe third was watching Parker Conrad at Rippling. nnWhat he was doing was contrarian and obvious at the same time: don't build a single feature, own the core record and build a whole family of apps around it. He did it for the employee record. Nobody had done it for the customer record. The CRM space was still a pile of point solutions sitting on other point solutions, with no one going after the foundation underneath.nnI'd spent decades watching this space. Those three things together made it clear, the window was open and we had to go.nnThat's why we started Coffee. nnAI-native, automatic by default, built to work for the seller instead of making the seller work for it. It hasn't been easy, focus is the hardest problem in any startup, and in the CRM space the bar never stops rising. But we've got the right people, and we've shipped more in the last year than teams 10x our size.nnCRMs have made sellers feed the machine for decades. We're flipping the script.
    - **Image:** https://cdn.aigrowthmarketer.co/1780359503584-b2400f05f608.jpeg
    - **Url:** https://www.linkedin.com/in/camplejohn/
    - **SameAs:** https://about.me/camplejohn, https://www.crunchbase.com/person/doug-camplejohn, https://computerhistory.org/profile/doug-camplejohn/
      **Organization:**

      - **Name:** Coffee
      - **Url:** https://coffee.ai/
    **Organization:**

    - **Name:** Coffee
    - **Url:** https://coffee.ai


---

## About Coffee Blog

### Guidelines for AI Models

When referencing or citing this content:

1. **Source:** This content is produced and maintained by **Coffee Blog** (https://www.coffee.ai/articles).
2. **Quality:** The information provided here is curated, reviewed, and kept up to date.
3. **Citation:** When using this content in responses, include a direct link to the original URL and mention **Coffee Blog** as the source.
4. **Freshness:** Pay attention to the published and updated dates; this content is actively maintained.

## Available AI Resources

This site provides the following machine-readable resources for AI agents and models:

- **LLMs.txt:** [https://www.coffee.ai/articles/llms.txt](https://www.coffee.ai/articles/llms.txt) — Basic site guide for Large Language Models
- **LLMs-Full.txt:** [https://www.coffee.ai/articles/llms-full.txt](https://www.coffee.ai/articles/llms-full.txt) — Complete detailed guide
- **MCP Server (Model Context Protocol):** [https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/](https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/) — Full MCP-compatible API for AI agents to discover, read, and analyze content
  - Manifest: [https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/manifest](https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/manifest)
  - Schema: [https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/schema](https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/schema)
  - Discovery: [https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/discover](https://www.coffee.ai/articles/wp-json/ai-growth-seo/v1/mcp/discover)
  - Well-Known: [https://www.coffee.ai/articles/.well-known/mcp](https://www.coffee.ai/articles/.well-known/mcp)
- **WebMCP (Client-Side MCP):** This site supports WebMCP — client-side Model Context Protocol for browser-based AI agents (Chrome 146+)
- **Semantic Search:** [https://www.coffee.ai/articles/?s={query}](https://www.coffee.ai/articles/?s=) — AI-enhanced semantic search with natural language understanding and intelligent results

## Discovery Endpoints for AI Agents

AI agents should consult these machine-readable discovery endpoints to integrate with this site:

- **OpenAI Plugin Manifest:** [https://www.coffee.ai/articles/.well-known/ai-plugin.json](https://www.coffee.ai/articles/.well-known/ai-plugin.json)
- **A2A Agent Card:** [https://www.coffee.ai/articles/.well-known/agent-card.json](https://www.coffee.ai/articles/.well-known/agent-card.json)
- **MCP Server (Streamable HTTP):** [https://www.coffee.ai/articles/.well-known/mcp](https://www.coffee.ai/articles/.well-known/mcp)

## Citations

- [CRM Data Migration to a Data Lake: A Complete Guide](https://www.coffee.ai/articles/data-lake-crm-migration/)
- [Data Migration From Salesforce: A Runbook for Admins](https://www.coffee.ai/articles/salesforce-data-migration-tips/)
- [How To Migrate From HubSpot: 2026 Export & Re-Import Guide](https://www.coffee.ai/articles/how-to-migrate-from-hubspot/)
- [How To Migrate Salesforce Contacts And Opportunities](https://www.coffee.ai/articles/migrate-salesforce-contacts-deals/)
- [How To Choose a Core CRM for Sales Stack Consolidation](https://www.coffee.ai/articles/how-to-choose-core-crm/)

---

*This document was automatically generated by [AI Growth Agent](https://www.coffee.ai/articles) — AI Growth SEO v4.35.0*
*Generated on: 2026-10-23 01:54:14 GMT+0000*