1. Export ACT's "Notes", try to get out Opportunities along with Contacts and Address stuff - get it into SF using Notes and Attachments, then roll out and configure Salesforce with the new fields and processes (figure out how to move the old ACT notes that are now in Notes and Attachments into a custom field or oject) OR
2. Figure out what fields and processes will be used in Salesforce, create them and the page layouts first, Rollout SF First, (maybe even importing the contacts, accounts and easy stuff already) then import ACT data into correct places.
What are the advantages or disadvantages of doing it either one way or the other or does it matter?
Pat
5 answers
1.) Always plan out your entire Data Model thoroughly first. Decide which custom objects you will need. Also, map out all processes! proper planning will make implementation go so much smoother!
2.) Create Custom Objects and Custom fields. You'll need to create custom fields before importing any data, to make sure you can import all data fields from the source system.
3.) Also, make sure to include some migration fields. Essentially, you'll need a new external ref ID field on each object to import the old record ID field to. This is absolutely necessary to ensure all for your contacts and opportunities will be related to the appropriate accounts! a good tool that does this for you is: https://appexchange.salesforce.com/listingDetail?listingId=a0N30000004cPFQEA2
Why are you considering a custom object for your ACT notes? Are there more fields than what Salesforce Notes has? A Custom object may not be a bad solution for this, but I would use Notes or Chatter if possible. I've also had situations where it made sense to import notes from a source system to Tasks/Activities, because they were always tied to a specific action, like Call or E-mail. This may be an option for you.
4.) Once you have your custom objects and Custom fields set up, with External Reference ID's, you'll then use APEX Data Loader to do an Upsert. The Upsert allows you to use External reference ID's for matching and relationships.
I would import(upsert) from 'Top to Bottom" - Meaning, import objects that are typically parents in relationships, Like Accounts, then their children like Contacts and Opportunities, then Notes/Activities, which could be related to any of the above.
I would import all data before rolling out to your users.
Hope this helps!
