While you can always manually map stages between Apollo and Salesforce, you can also make use of automapping to make the job easier. If an unmapped stage in Apollo matches an unmapped value in Salesforce, then Apollo can automatically map the two together. Additionally, for Salesforce values that don’t have a matching stage in the platform, Apollo will create one for you.
Please note, Apollo will not overwrite any mappings that you created before running the auto-mapping feature. Apollo will only automatically map stages that are not already mapped.
Refer to the sections below for details about how to automatically map Contact, Lead, or Account fields from Salesforce to stages in Apollo.
Please note, the process for automatically mapping stages is the same for all record types. Follow the same instructions below to automatically map stages for Contacts, Leads, or Accounts.
Automatically Map Stages
Launch Apollo and click Settings.
Click View in the Salesforce section.
Click View in the Stage and Field Mappings section.
Click the "Contacts," "Leads," or "Accounts" tab depending on the record type that you want to automatically map.
Click Get Started in the Automatically Create and Map Stages section.
You will see a modal with additional details about how Apollo automatically creates and maps stages. When you're ready to start the process, click Proceed.
Click the drop-down and then click an unmapped Salesforce field.
When you're finished, click Create and Map to run the automation based on the selected field.
Apollo has now automatically mapped the field status that you selected. Repeat this process for any other additional mappings that you'd like to automatically create.
Please note, if an unmapped value from Salesforce does not match a stage in Apollo, Apollo will automatically create a stage and map the two together. If an unmapped value from a Salesforce field matches an existing stage, but that stage is already mapped to a different value, Apollo will not map the Salesforce field to the existing stage. Apollo will also not attempt to create a new stage and match the two together, since that would incorrectly create a duplicate for a stage that already exists.