How to Integrate LastDatabase with Salesforce

Connect your Salesforce account to LastDatabase and send eligible business or consumer email contacts directly to Salesforce Contacts.

The Salesforce integration lets you move selected LastDatabase records into Salesforce without manually downloading and importing a file. Before eligible email records are delivered, the LastDatabase CRM pipeline applies its configured verification and suppression checks.

Supported destination: The current Salesforce integration sends records to Salesforce Contacts. Your field mapping controls which supported LastDatabase fields are written to Contact fields.

Before you begin

You need:

An active LastDatabase customer account.
Access to the LastDatabase customer dashboard.
A Salesforce account that you are authorized to connect.
Permission in Salesforce to create or update Contact records.

1. Connect Salesforce

Open your LastDatabase customer dashboard.
Go to the CRM integration area and select Salesforce.
Choose Connect Salesforce.
LastDatabase starts the Salesforce authorization process and redirects you to Salesforce.
Authorize LastDatabase.
Sign in to the Salesforce account you want to connect and approve the requested access.
Return to LastDatabase.
After successful authorization, Salesforce redirects you back to LastDatabase and the connection is stored for your customer account.

A connected Salesforce account must remain active for exports to be delivered. Disconnecting the integration prevents new exports through that connection.

2. Configure Salesforce Contact field mapping

Field mapping determines how LastDatabase record fields are written into Salesforce Contact fields.

The standard mapping includes:

LastDatabase field	Salesforce Contact field
Email	Email
First name	FirstName
Last name	LastName
Job title	Title
City	MailingCity
State	MailingState
Postal code	MailingPostalCode
Country	MailingCountry

Review the mapping before sending records. Only map fields that are appropriate for your Salesforce Contact configuration.

Salesforce country values

Salesforce organizations that use State and Country/Territory Picklists can require standardized country values. LastDatabase normalizes supported country aliases when preparing the outbound Salesforce Contact payload.

LastDatabase value	Salesforce outbound value
USA / US / United States of America	United States
UK / Great Britain	United Kingdom
UAE	United Arab Emirates

This normalization is applied to the outbound Salesforce value. It does not rewrite the source country stored in the LastDatabase dataset.

3. Find the contacts you want to export

Use LastDatabase search and targeting tools to locate the records you need. Select the eligible records you want to send to Salesforce.

The CRM export workflow supports the email lead types enabled by the current integration, including B2B email and consumer email records.

4. Send selected contacts to Salesforce

Select your records.
Choose the contacts you want from the supported LastDatabase customer data interface.
Choose Send to Salesforce.
LastDatabase creates a CRM export for the selected records and begins the preparation process.
Wait for eligibility processing.
Email records pass through the configured CRM eligibility workflow before delivery.
Eligible records are delivered.
Records that pass the required checks are sent to the connected Salesforce account.

5. Verification and suppression checks

The CRM pipeline checks email-record eligibility before Salesforce delivery. Depending on the record state, this can include fresh email verification and suppression checks.

A record that does not satisfy the required delivery conditions can be skipped rather than pushed to Salesforce.

CRM eligibility does not replace your own legal, contractual, consent, or campaign-specific obligations. Use exported data only for purposes you are authorized to perform.

6. Contact creation and updates

When an eligible record reaches Salesforce, the connector sends the mapped Contact properties to the connected Salesforce organization.

The export result records whether the Salesforce operation created or updated the destination record. When Salesforce returns a Contact ID, LastDatabase stores that external record identifier with the CRM export item.

For an update, the existing Salesforce Contact remains the destination record rather than creating another Contact for that successful update operation.

7. Check export status

Use the Salesforce integration area in your LastDatabase customer account to review CRM export activity.

Export processing can track outcomes such as:

Successful — Salesforce accepted the record.
Skipped — the record did not satisfy a required delivery condition.
Failed — Salesforce or the delivery process returned an error.
Processing — the export is still being prepared or delivered.

Successful export items can also contain the Salesforce external record ID and whether the operation created or updated the Contact.

8. Disconnect Salesforce

If you no longer want LastDatabase connected to a Salesforce account, use the disconnect option in the Salesforce integration area.

Disconnecting prevents that connection from being used for new Salesforce exports. Existing Salesforce records are not deleted merely because the LastDatabase connection is disconnected.

Troubleshooting

Salesforce rejects the country

If your Salesforce organization uses State and Country/Territory Picklists, Salesforce can reject non-standard country names. LastDatabase normalizes supported aliases such as USA, UK, and UAE before sending the MailingCountry value.

A selected record was skipped

The record may not have satisfied the current CRM verification or suppression requirements. Review the export status before attempting another delivery.

The Salesforce connection is inactive

Reconnect Salesforce from the customer integration area and complete the Salesforce authorization process again.

A Salesforce export failed

Review the export error information. Salesforce can reject a record because of organization-specific validation rules, field restrictions, permissions, required fields, or Salesforce configuration.