> ## Documentation Index
> Fetch the complete documentation index at: https://help.ruddr.io/llms.txt
> Use this file to discover all available pages before exploring further.

# What fields sync as part of the Salesforce integration?

This integration syncs data from Salesforce into Ruddr. All data flows **one way (Salesforce → Ruddr)**.

* [Companies](#companies-accounts)
* [Contacts](#contacts)
* [Opportunities](#opportunities)
* [Pipelines](#pipelines)
* [Stages](#stages)
* [Activities](#activities-tasks)

## Companies (Accounts)

### Syncing companies from Salesforce

When accounts are synced, Ruddr imports the following:

**Basic details**

* Company name and description
* Phone number (limited to 20 characters)
* Website URL

**Addresses**

* Billing address (street, city, state, postal code, country)
* Shipping address (if available)

**Ownership**

* Owner is matched to a Ruddr member by email
* If no match is found, a new member is created automatically

**Additional fields**

* Industry (matched or created if missing)
* Company type (matched or created if missing)
* Annual revenue
* Number of employees
* Year founded
* Ticker symbol
* SIC code
* Ownership classification (public, private, subsidiary, or other)

**Status**

* Active status is derived from Salesforce (deleted accounts are marked inactive)

***

## Contacts

### Syncing contacts from Salesforce

**Basic details**

* Full name (first + last name)
* First name and last name stored separately
* Email address

**Contact information**

* Mobile phone
* Office phone
* Fax

**Additional fields**

* Job title
* Description

**Ownership and relationships**

* Owner is matched to a Ruddr member
* Associated company is linked

***

## Opportunities

### Syncing opportunities from Salesforce

**Basic details**

* Opportunity name and description
* Amount
* Close date
* Next steps

**Sales data**

* Probability
* Stage (matched by name and pipeline)
* Lead source (matched or created if missing)
* Opportunity type (matched or created if missing)

**Ownership and relationships**

* Owner is matched to a Ruddr member
* Associated company is required (opportunity is skipped if no match is found)

**Dates and currency**

* Open date (created date)
* Currency (Ruddr sets the currency based on the opportunity's currency. If it doesn't find one, it uses the workspace currency, and if that's not available, it defaults to USD.)

**Pipeline**

* Determined based on Salesforce record type

***

## Pipelines

### Syncing pipelines

Pipelines are derived from Salesforce business processes tied to record types.

**Fields synced**

* Pipeline name
* Pipeline description

Only pipelines selected in your [integration settings](/integrations/salesforce-integration-setup) are synced into Ruddr. If no specific configuration is provided, a default pipeline is created.

***

## Stages

### Syncing stages

**Fields synced**

* Stage name and description
* Probability
* Active status

**Stage status mapping**

* Won → marked as “Won”
* Closed (but not won) → marked as “Lost”
* All others → marked as “Open”

Stages are filtered per pipeline based on Salesforce configuration.

***

## Activities (Tasks)

### Syncing activities from Salesforce

Note that Ruddr only syncs activities according to the [integration settings](/integrations/salesforce-integration-setup), as configured by a Workspace Admin.

**Common fields**

* Subject (falls back to description or “Task Activity” if missing)
* Content (description)
* Activity date (uses activity date or created date)
* Created by and owner (matched to Ruddr members)
* Associated company
* Associated opportunity
* Associated contact

***

### Activity type mapping

Activity type is determined using a multi-step approach:

1. Match by subject
2. Match by Salesforce subtype
3. Match by predefined type
4. Default to “Other” if no match is found

***

### Sync behavior

* Activities missing in Salesforce are removed from Ruddr during full sync
* Email-type activities are parsed to extract structured content

***

## Member Mapping

### How users are matched and created

* Members are matched by email address
* If no match is found:
  * A new member is created automatically
  * Name is pulled from Salesforce user data
  * Active status is preserved from Salesforce
  * Assigned the workspace default role
  * Set as non-billable
  * Not invited to the workspace