Integrated Data

Salesforce

What this page covers: A complete reference mapping every Salesforce field to its Mosaic equivalent. Use this guide when configuring your integration, verifying synced data, or troubleshooting discrepancies.

Integration typeCloud (Salesforce REST API / Outbound Messages)
Setup complexityLow
Configurable fieldsStandard fields; custom fields via scoped engagement
PrerequisiteSalesforce Integration Setup

How Data Flows

Salesforce (REST API / Outbound Messages) → Mosaic Sync Engine (field mapping) → Mosaic (4 synced data types)

Mosaic pulls data from Salesforce using the REST API and Outbound Messages. Standard object fields are mapped automatically; custom fields can be evaluated and incorporated through a scoped engagement.

Edition Requirements

Essentials and Professional editions of Salesforce (and any others) that do not include Workflows and Outbound Messages are not supported for integration.


Integrated Data Types

The integration syncs 4 data categories from Salesforce into Mosaic:

#Data TypeDescription
1ClientsAccount records mapped to Mosaic clients
2EmployeesUser records with names, emails, and active status
3ProjectsOpportunity records mapped to Mosaic projects
4TasksTask records with assignments, priorities, and statuses

This list may expand as new features are added. If new features require expanded permissions, your assigned Customer Success Manager will reach out to request updates to the profile associated with the Mosaic user.


Reading the Field Mapping Tables

Symbol legend for technical tables

The Technical Reference tabs below use a shorthand notation for Salesforce REST API sources. Read this legend before reviewing the mappings.

SymbolMeaningExample
.API object field referenceAccount.Name = the Name field from the Account object
Maps to / results inUser.IsActive → Active Status = IsActive determines active status

Detailed Field Mappings

Jump to a section: Clients | Employees | Projects | Tasks


Clients

What Syncs to MosaicWhere It Comes From in Salesforce
Client NameThe Account name
Client DescriptionThe Account description
Archive / Delete StateWhether the Account has been deleted
Created DateWhen the Account record was created
Modified DateWhen the Account record was last modified

Note: Parent Account can inform hierarchy but is not surfaced as a Mosaic Client relation by default.


Employees

What Syncs to MosaicWhere It Comes From in Salesforce
Employee NameThe User's full name
EmailThe User's email address
RoleThe User's title (default mapping)
Active StatusWhether the User is active in Salesforce

Note: Manager or Department are not mapped by default.


Projects

What Syncs to MosaicWhere It Comes From in Salesforce
Project NameThe Opportunity name
ClientThe Account associated with the Opportunity
StatusDerived from the Opportunity stage and closed/won flags
End DateThe Opportunity close date
FeeThe Opportunity amount (optional)

Notes:

  • Opportunity Owner is not mapped by default.
  • Client probability is not mapped by default but can be scoped.
  • Customized append data coming soon: Description, Probability, Expected Revenue, and Type fields from Opportunity will be available as additional synced data in a future release.

Tasks

What Syncs to MosaicWhere It Comes From in Salesforce
Task NameThe Task subject line
DescriptionThe Task description / comment body
ProjectThe related Opportunity (if one exists)
AssigneeThe User assigned to the Task
PriorityThe Task priority level
StatusThe Task status value
End DateThe Task due date or completion date

Notes:

  • OwnerId (Created By) is not mapped by default.
  • Custom pick-lists may require alignment.

Salesforce Documentation Links

A consolidated reference of all Salesforce documentation referenced in this guide:

TopicLink
Object ReferenceStandard Objects
AccountAccount Object
UserUser Object
OpportunityOpportunity Object
TaskTask Object

Related Documentation

Custom Fields & Unsupported Data

  • Custom fields can be evaluated and added through a scoped engagement.
  • Field availability varies by Salesforce edition, configuration, and user permissions.
  • Relationships such as Account hierarchy, Opportunity Owner, and Task Owner are not mapped by default but can be scoped if needed.
  • Integrating data types not explicitly listed above is not supported as a standard feature.