Pimcore Salesforce Connector

Salesforce Product2 records move both ways. On import, the connector reads product data through paged SOQL requests and matches on SKU and ProductCode.

Prices come from the standard PricebookEntry and are flattened onto the Pimcore product. The Salesforce Family value can derive or link a Pimcore category. For a headless commerce catalog, you can also check our Pimcore Commercetools Connector.

• Import Product2 records through paged SOQL requests.
• Read the product price from the standard price book.
• Link a Salesforce Family value to a Pimcore category.
• Upsert Pimcore products back to Salesforce Product2.
• Find or create the matching PricebookEntry on export.
• Strip unsupported and read-only fields before each request.

Accounts, Contacts, Leads, and Opportunities import from Salesforce and export from Pimcore. Each entity uses the Pimcore class you selected on the Object Mapping screen.

Field mappings define how values move between the two systems. Contact and Lead match on Email, Account matches on Account Number, and Opportunity matches on Name. To load records from a file instead, you can check our Pimcore DataImport Bundle.

• Sync Salesforce Accounts with a mapped Pimcore class.
• Sync Contacts and Leads matched on their Email value.
• Sync Opportunities with stage and close date defaults.
• Configure a separate field mapping for every entity.
• Match on a business field before any record is created.
• Apply create-only defaults so an update never blanks a value.

The Object Mapping screen sets which Pimcore class represents each Salesforce entity. The five supported pairs are Product2, Account, Contact, Lead, and Opportunity.

Field Mapping pairs a Pimcore field with a Salesforce field. One saved map drives both import and export, so the two directions can never drift apart. To fill mapped fields with generated copy, you can check our Pimcore Product Enrichment Agent.

• Select the Pimcore class for each Salesforce entity.
• Pick a standard field or type a custom API name.
• Map a custom Salesforce field such as Brand__c.
• Auto-create a mapped Pimcore field that does not exist yet.
• Keep the match key fixed so records pair on every run.
• Save one mapping per entity from its own tab.

The connector authenticates with OAuth2 Client Credentials through a Connected or External Client App. A credential holds a Name, My Domain URL, Consumer Key, Consumer Secret, and API version.

Consumer Secrets are stored with libsodium encryption and are never returned as plaintext. Any legacy plaintext credential can be migrated to encrypted storage.

• Authenticate through the OAuth2 Client Credentials flow.
• Enter the My Domain URL, Consumer Key, and Consumer Secret.
• Pick the Salesforce REST API version, such as v62.0.
• Test the credential against Salesforce before it is saved.
• Leave the secret blank on edit to keep the stored value.
• Refresh the bearer token once after a 401 response.

Imports and exports run as queued jobs on a Reader-Processor-Writer framework with its own Salesforce sync transport. Studio never blocks while a run is in progress.

Each run records how many records it read, created, and updated, beside a timestamped activity log. The job history combines import and export runs across every entity. For the same job view against a WordPress store, check our Pimcore WooCommerce Connector.

• Queue an import or export from its entity screen.
• Track records read, created, and updated per run.
• Follow the live activity log line by line.
• Stop a job while it is queued or already running.
• Retry a run from the job history screen.
• See the credential and the user who started each run.

Two Salesforce orgs rarely expose the same fields. The connector describes each sObject before it builds a request, so it only ever asks for fields that exist on the org.

Missing optional fields drop out of the SELECT statement and out of the write payload. A field the org lacks can no longer return an INVALID_FIELD error mid-run.

• Describe the real Salesforce object schema per run.
• Remove unavailable fields from the SOQL query.
• Remove unsupported fields from the write payload.
• Fall back to the Salesforce record Id as the key.
• Update by Id when the match field is missing.
• Keep repeat imports idempotent with no duplicates.

Pimcore Studio carries a Salesforce Connector menu with pages for Credentials, Object Mapping, Field Mapping, Import, and Export. Import and Export open one screen per entity.

Admins add, edit, test, activate, and delete credentials from the grid. Every run screen shows recent runs with status, item counts, and timestamps. To translate the synced content, you can check our Pimcore DeepL Translation Connector.

• Open Credentials to add or test a Salesforce connection.
• Set the Pimcore class per entity on Object Mapping.
• Configure field pairs per entity on Field Mapping.
• Start an import or export from its entity screen.
• Open any run to read its counts and activity log.
• Confirm before a credential is deleted.

The connector ships separate permission keys for credentials, mappings, imports, exports, and jobs. They appear under a Salesforce Connector category in Users and Roles.

Levels cover view, manage, execute, test, and stop. The backend stays the authority, so an ungranted action is refused even if a button is visible.

• Grant or withhold access to Salesforce credentials.
• Restrict who can change object and field mappings.
• Control who may execute an import run.
• Control who may execute an export run.
• Restrict who can stop a running job.
• Separate connection test rights from management rights.