Salesforce Acquisitions: Timeline | SalesforceTutorial

Salesforce acquisitions explain how Salesforce expanded from core CRM into integration, analytics, collaboration, commerce, field service, industries, marketing, data protection, and AI data management. The practical value for admins and architects is not the headline price alone; it is knowing which acquired technology now sits inside the Salesforce product stack, which parts remain separate, and what that means for licensing, integration, data governance, and roadmap risk.

This guide lists major Salesforce acquisitions with dates, prices where Salesforce disclosed them, and the product impact for Salesforce professionals. It also explains how to read “Salesforce to buy” news, how to track companies acquired by Salesforce in an enterprise architecture register, and how to answer the related search query about a list of companies using Salesforce CRM without confusing customers with acquisitions.

Salesforce Acquisitions

Salesforce acquisitions usually fall into one of five patterns. Salesforce may buy a category leader, such as Slack or Tableau; add a missing platform layer, such as MuleSoft or Informatica; enter a vertical or commerce market, such as Vlocity or Demandware; deepen a cloud, such as ExactTarget for Marketing Cloud; or add a specialist capability that later becomes part of a wider roadmap.

For implementation teams, the important question is: What changed in the customer architecture? A deal can introduce a new product SKU, a new permission set license, a managed package, a new API endpoint, a data movement pattern, or a product retirement plan. That is why a Salesforce acquisitions timeline should be read with product documentation, not only finance news.

Salesforce to buy: announced deal versus closed acquisition

The phrase salesforce to buy usually appears when Salesforce signs a definitive agreement. That does not always mean the transaction has closed. For example, Salesforce announced its agreement to acquire Contentful on June 1, 2026, and the official announcement says the transaction is expected to close in Salesforce’s fiscal third quarter of 2027, subject to closing conditions and regulatory approvals.

When documenting Salesforce acquisitions for governance, keep two dates: the announcement date and the close date. Use the close date for procurement, vendor-risk, and support-transition records. Use the announcement date only for market context.

Companies Acquired By Salesforce: Timeline and Price Table

The table below focuses on larger or architecturally important Salesforce acquisitions and the companies acquired by Salesforce. Amounts are stated as approximate transaction values when Salesforce disclosed them in official announcements or investor materials. Some smaller 2025 and 2026 AI acquisitions did not disclose price publicly, so they should be tracked by product impact rather than purchase price.

Companies acquired by Salesforce that changed product architecture

Not every acquisition matters to every org, and not all Salesforce acquisitions create immediate admin work. Slack, Tableau, MuleSoft, Informatica, ExactTarget, Demandware, Vlocity, ClickSoftware, and Own Company affect architecture because they influence collaboration, analytics, integration, data, marketing, commerce, industry processes, field operations, or backup and recovery. These companies acquired by Salesforce are the ones most likely to appear in enterprise diagrams, procurement reviews, and integration runbooks.

Smaller AI-era deals, including Qualified, Momentum, Cimulate, Bluebirds, Waii, Regrello, Convergence.ai, and Contentful, should be tracked by release notes and product availability. A signed agreement may not mean the capability is enabled in your org.

What did the largest Salesforce acquisitions add?

Slack: collaboration and workflow surface

Slack gave Salesforce a collaboration surface that sits outside a single Salesforce record page. In enterprise orgs, this matters because sales, service, and incident workflows often involve people who do not spend their full day inside CRM. Architects should validate Slack app permissions, data retention, channel naming, approval paths, and whether sensitive record data can flow into conversations.

Tableau: analytics across Salesforce and non-Salesforce data

Tableau changed the analytics conversation. A Salesforce report answers questions inside a CRM data model; Tableau can combine CRM data with warehouse, product, finance, and external datasets. In 2026 designs, also account for Data 360 naming: Salesforce Help states that Data Cloud was rebranded to Data 360 on October 14, 2025.

MuleSoft: integration patterns after Salesforce acquisitions

MuleSoft matters when the Salesforce org is one node in a larger architecture. Use MuleSoft when the integration requirement needs API management, transformation, policy control, reusable connectors, or integration across ERP, data lake, commerce, and service systems. Salesforce Developer documentation for the Salesforce Data Cloud Connector shows how MuleSoft connectors can support ingestion, querying, calculated insights, and data action use cases.

Demandware and Commerce Cloud

Demandware became important because Salesforce needed a commerce engine for retail and direct-to-consumer scenarios. For architects, the acquisition changed the boundary between CRM, order capture, product catalog, promotions, and digital storefronts. If your org uses Commerce Cloud with Service Cloud or Marketing Cloud, document how customer identity, consent, orders, cases, and product data move between systems.

Salesforce ExactTarget Acquisition Date Price

The search query salesforce exacttarget acquisition date price has a direct answer: Salesforce announced the ExactTarget acquisition on June 4, 2013, in a transaction valued at approximately $2.5 billion. Salesforce later reported that ExactTarget closed in July 2013. The product impact was larger than email alone. ExactTarget became a foundation for Marketing Cloud Engagement, while Pardot, which ExactTarget had acquired before the Salesforce deal, later became Account Engagement.

For admins, the ExactTarget history explains why Marketing Cloud Engagement uses a different administration and data model than Sales Cloud. Contact model, subscriber keys, business units, send classifications, journeys, and data extensions need separate governance. Salesforce Help describes Journey Builder as the Marketing Cloud Engagement tool for designing and automating customer journeys.

Own Company: data protection and operational recovery

Own Company adds a different kind of value than a sales or service feature. Backup, restore, archive, sandbox seeding, and compliance controls reduce operational risk. Salesforce acquisitions in this category affect recovery time, audit evidence, data lifecycle design, and the separation between production data and test data.

ClickSoftware and Field Service

ClickSoftware strengthened Field Service scheduling and mobile workforce management. Salesforce Help now describes Agentforce Field Service and Operations as tools for work orders, scheduling, and mobile workers. In a production implementation, review dispatcher console setup, service territories, operating hours, skills, work rules, mobile app offline requirements, and integration with ERP inventory or billing.

Vlocity, Salesforce Industries, and OmniStudio

Vlocity became the basis for many Salesforce Industries assets. Salesforce Help describes OmniStudio as services, components, and data model objects used to create guided interactions and industry cloud applications. For architects, this means Vlocity-style assets can introduce OmniScripts, FlexCards, Integration Procedures, Data Mappers, industry managed packages, and data model assumptions that must be reviewed before a migration or consolidation project.

How Salesforce Acquisitions Affect Enterprise Architecture

Salesforce acquisitions can create value, but they also add architecture decisions. In large orgs, Salesforce acquisitions often show up as separate workstreams for identity, data, integration, and compliance. The same customer may run Sales Cloud, Service Cloud, Slack, Tableau, MuleSoft, Marketing Cloud Engagement, Data 360, Commerce Cloud, Field Service, and an industry package. Treat each acquired product as a system with its own identity model, data retention rules, audit logs, release cadence, admin console, API limits, and licensing terms.

Best practices for acquisition-aware Salesforce governance

• Keep a product dependency register. Track the acquired product, owning team, business process, license type, integration method, data classification, and renewal date.
• Separate brand names from technical assets. A product can be renamed while API names, package names, or object prefixes stay different.
• Document data movement. Acquisition-driven products often use connectors, external APIs, managed packages, or separate clouds.
• Review security boundaries. Check SSO, connected apps, permission sets, OAuth scopes, field-level security, sharing, and data residency.
• Watch retirements. Quip is a current example: Salesforce Help says end of renewal is effective March 1, 2027.

Technical checklist before adopting an acquired Salesforce product

Apex example: track acquired-product dependencies with custom metadata

The following Apex pattern is useful when an enterprise architecture team wants a lightweight registry of acquisition-related dependencies. The example assumes a custom metadata type named Acquired_Product__mdt with fields Product_Family__c, Owner_Team__c, Status__c, and Review_Required__c. Salesforce Developer documentation supports custom metadata type access from Apex through type methods such as getAll().

public with sharing class AcquisitionDependencyService {
    public class ProductRisk {
        @AuraEnabled public String productFamily { get; set; }
        @AuraEnabled public String ownerTeam { get; set; }
        @AuraEnabled public String status { get; set; }

        public ProductRisk(String productFamily, String ownerTeam, String status) {
            this.productFamily = productFamily;
            this.ownerTeam = ownerTeam;
            this.status = status;
        }
    }

    @AuraEnabled(cacheable=true)
    public static List<ProductRisk> getOpenRisks() {
        List<ProductRisk> risks = new List<ProductRisk>();

        for (Acquired_Product__mdt item : Acquired_Product__mdt.getAll().values()) {
            if (item.Review_Required__c == true && item.Status__c != 'Retired') {
                risks.add(new ProductRisk(
                    item.Product_Family__c,
                    item.Owner_Team__c,
                    item.Status__c
                ));
            }
        }

        return risks;
    }
}

Keep this type of code small. Do not store secrets in custom metadata. Salesforce Developer documentation notes that public custom metadata types are readable for all profiles, including the guest user, so use protected custom metadata in a managed package or a secure secrets pattern when the value is sensitive.

SOQL example for a list of companies using Salesforce CRM inside your org

The phrase list of companies using salesforce crm often means a public customer list, but Salesforce does not publish a complete customer database. Inside your own org, you can produce a scoped list only if your implementation records product usage. The example below queries active Asset records linked to Product2 families. Use your actual product model, and enforce access using the current Apex security model.

Set<String> productFamilies = new Set<String>{
    'Sales Cloud',
    'Service Cloud',
    'Marketing Cloud Engagement'
};

List<Asset> subscriptions = [
    SELECT Id, Name, AccountId, Account.Name, Product2.Name, Product2.Family
    FROM Asset
    WHERE Status = 'Active'
    AND Product2.Family IN :productFamilies
    WITH USER_MODE
    LIMIT 200
];

for (Asset subscription : subscriptions) {
    System.debug(subscription.Account.Name + ' uses ' + subscription.Product2.Name);
}

Salesforce Developer documentation describes SOQL as the language for searching Salesforce data. For current Apex security, review the official Apex security and sharing guidance before moving code to production. In API version 67.0 and later, the Apex security docs state that WITH SECURITY_ENFORCED is not available and that developers should use WITH USER_MODE for user-mode data operations where appropriate.

How to Read Salesforce Acquisition News Without Misleading Users

Salesforce acquisitions news can be useful, but it should not drive implementation promises. A press release may describe a product vision before packaging, limits, pricing, geography, or feature availability are final. Use this review order before advising a stakeholder:

1. Confirm whether the deal is announced, pending, or closed.
2. Check whether Salesforce has published product documentation, release notes, or help pages.
3. Verify whether the feature is Generally Available, Beta, Pilot, or roadmap only.
4. Review licensing and contract terms with the account team.
5. Run a security and data review before connecting the product to regulated data.

This approach keeps Salesforce acquisitions useful for planning without turning them into unverified commitments. Treat Salesforce acquisitions as input to architecture planning, not as proof that a feature is ready for every org. A well-maintained Salesforce acquisitions register also helps support teams answer renewal, data, and ownership questions without searching old project notes.

Internal SalesforceTutorial Resources

Use these related SalesforceTutorial resources when Salesforce acquisitions map to a product implementation area. These links help you move from Salesforce acquisitions history into setup, integration, and governance work.

• Salesforce Marketing Cloud implementation basics
• Salesforce Commerce Cloud architecture overview
• Salesforce Data Cloud and Data 360 concepts
• MuleSoft Salesforce integration patterns
• Salesforce Field Service setup guide

Official Salesforce References

• Salesforce mergers and acquisitions newsroom
• Salesforce Help: About Salesforce Data 360
• Salesforce Help: Journeys and Automations in Marketing Cloud Engagement
• Salesforce Help: Agentforce Field Service and Operations
• Salesforce Help: OmniStudio
• Salesforce Developer Docs: Apex security and sharing model

Frequently Asked Questions