Understand the working context

Connecting an authorised application establishes access within the permissions and API capabilities available to that account. It does not automatically map every field or transfer every object. Identify the customer information you need, the source identifiers that should be preserved and the destination relationships. A bounded preview helps the team inspect representative records before choosing a migration approach. Keep expectations aligned with the current connector scope.

Put it into practice

  • Confirm the Salesforce organisation and authorised application.
  • Identify the objects and fields needed for the first task.
  • Review identifiers, account relationships and ownership.
  • Validate a sample before planning a larger data movement.

A practical example

A team wants to inspect account and contact data before a move. They connect the correct organisation, review the supported extraction and staging results, then check a sample against the source. Files, historical activities and custom objects require their own scope discussion instead of being assumed to transfer automatically.

HOW THIS RELATES TO ATLAS

In the current workspace

Enterprise provides Salesforce discovery and bounded extraction/staging workflows. Continuous two-way sync and a complete migration of every Salesforce object or attachment are not currently included.

Explore the product

Further reading

For more detail on the general topic:

Atlas feature scope reviewed 17 October 2026. Plan availability and connection setup apply.