Overview

When the ACME/Salesforce integration is activated, any newly created or updated data will begin to flow into your Salesforce environment. The integration will not send any historical data over to your Salesforce environment, unless it’s part of a new transaction, so you’ll want to plan to migrate any important data to Salesforce as part of your transition.


The source of the data and whether it’s currently shared across multiple systems will determine what you’ll need to consider when migrating the data to ensure things work smoothly once the integration is activated.


TABLE OF CONTENTS


Historical Data

Migrate CRM Data

Any data that is only in your CRM

  • Most commonly customers and organizations

  • Data is migrated solely to Salesforce, and ACME will have no record of it. If Organizations or Customers get created in ACME using the same data at a later date, then a new record will be created and sent to Salesforce when this data flows to Salesforce from ACME. 

  • This is the expected behavior when data is only in the CRM, and no change to the current state.


Data in CRM and ACME, most commonly customers and organizations

  • Most commonly customers, organizations, and memberships

  • If Data is migrated to both Salesforce and ACME, then the correct IDs must be placed on the records in Salesforce so that the records are tied together and duplicates are not made once the integration is on. 

  • See the table below for where the ACME IDs should be placed when migrating this data to Salesforce.


Migrate ACME Data

  • If there is historical ACME order data that you choose to import into Salesforce, you will need to import that data into the same objects that are used by the integration. This ensures that if those orders are later edited in ACME, the updates flow into Salesforce as expected.

  • We recommend backfilling order data using the same object and field structure, so the data can be updated smoothly as needed and so reporting across the data is consistent. If the data is loaded in a different way, then there is a high likelihood of dupes being created, or blocking ACME updates.

  • We recommend using the Workato transaction report to pull this data. The CSV can then be used with Salesforce's API data loader to import it.


ACME Data Keys

While the full field map outlines the source and destination fields for each object, the key fields below are required to ensure that no duplicates are created if shared data is later synced via the integration. Migrating the data to use the same fields used by the integration will ensure these records can be used by the integration later on, if needed. If you migrate some data but not all, you may see incomplete data or inaccurate quantities.


Customer or Organization

Source
ACME Object, Field

Destination
SF Object, Field

Customer, Customer ID (aka Customer Number)

Customer, External Customer Import ID

Contact, ACME Customer Number 

Contact, ACME External Customer Import ID

If the Customer/Contact is also an Organization Contact:


Customer, Customer ID (aka Customer Number)

Organization Contact, ID

If the Customer/Contact is also an Organization Contact:

Affiliation, ACME Customer Number

Affiliation, ACME Org Contact ID

Organization, Organization ID

Account, ACME Org ID


Membership

Source
ACME Object, Field

Destination
SF Object, Field

Membership, Membership ID

Membership, Import ID

ACME Membership, ACME Membership ID

ACME Membership, ACME Membership Import ID

Membership Card, Card ID

ACME Membership Card, ACME Membership Card ID


Order

Source
ACME Object, Field

Destination
SF Object, Field

Order, Order ID

Opportunity, ACME Order ID 

Order Items, Order Item ID

Opportunity Products, ACME Order Item ID

Transaction, Transaction ID

Payment (NPSP), ACME Payment ID, (same custom field used by the integration)