Migrating from ACT! to Salesforce: Difference between revisions
Jump to navigation
Jump to search
Jkuehlthau (talk | contribs) No edit summary |
Jkuehlthau (talk | contribs) (→Notes) |
||
Line 11: | Line 11: | ||
===Notes=== | ===Notes=== | ||
#The initial "Accounts + Contacts Staging" job does not bring over phone number extensions. If you want | #The initial "Accounts + Contacts Staging" job does not bring over phone number extensions. If you want the extensions, you will need to add it to the Origin, p1.SUFFIX AS PhoneExt, and then update the PhoneNo field mapping to be a Hardcoded Function Field with "@@ORG:PhoneNo@@ @@ORG:SUFFIX@@" as the Value. Salesforce stores phone and Extension in the same field, so you can merge them here. |
Revision as of 18:43, 17 August 2015
This map will migrate ACT! to Salesforce.
This map is set up to use the SQL versions of ACT. If you have the older flat-file version of ACT, a simple upgrade process can get you on SQL for the migration. Duplicate companies are merged into a single Company record, with contact records underneath it, based on Company Name + City though this logic could be easily changed to fit your needs. This is done through use of a temporary database file, included with the download.
You will have to create 4 custom External ID fields in Salesforce, as defined in the included "instructions.txt" file, to allow for ID cross-referencing.
This map migrates Users, Accounts, Contacts, Opportunities, Notes, History, Activities and Attachments.
Notes
- The initial "Accounts + Contacts Staging" job does not bring over phone number extensions. If you want the extensions, you will need to add it to the Origin, p1.SUFFIX AS PhoneExt, and then update the PhoneNo field mapping to be a Hardcoded Function Field with "@@ORG:PhoneNo@@ @@ORG:SUFFIX@@" as the Value. Salesforce stores phone and Extension in the same field, so you can merge them here.