Settings

Migrate data from GoldMine version 6.0 to Microsoft Dynamics CRM

Published: April 12, 2008

To migrate from GoldMine version 6.0 to Microsoft Dynamics CRM, you need to first export and prepare your source data for migration, and then run the Data Migration Manager to map and migrate your data. For an overview of the migration process, see Data migration overview.

This article describes how to export your data and set up your source files to match Microsoft Dynamics CRM record types, shows you where the default fields in GoldMine version 6.0 map to in an uncustomized Microsoft Dynamics CRM, and includes detailed steps for using Data Migration Manager to do your own mapping.

Important

The mappings in this article are guidelines only. Because your GoldMine version 6.0 database and Microsoft Dynamics CRM may be customized, you will need to verify that the mappings make sense for your data.

Preparing the data

Before migration, data must be in comma-separated value format (.CSV) files, and each file must contain data for one record type in Microsoft Dynamics CRM.

Prepare your data:

Export data from GoldMine version 6.0 to a text file. This file can contain comma-delimited or tab-delimited data.
Rename the exported data file to Accounts.csv.
Remove any newline characters from the data in Accounts.csv. If a record contains the newline character, it will not migrate.
Because data in GoldMine version 6.0 maps to several areas of Microsoft Dynamics CRM, make three copies of Accounts.csv, naming the copies Contacts.csv, Notes.csv, and Tasks.csv. In Data Migration Manager, you will map the corresponding columns in each file to attributes in the Account, Contact, Note, and Task record types.
If you want to map the owners of records to Microsoft Dynamics CRM users other than you, refer to footnote ¹ in the following Review the mapping table section. If necessary, create a Users.csv file.

Review the mapping table

Review the data in the following table to see how the columns in the source Accounts.csv, Contacts.csv, Tasks.csv, and Notes.csv files map to attributes in Microsoft Dynamics CRM. Click the following link to see the table.

GoldMine to Microsoft Dynamics CRM mapping table

GoldMine attribute	Accounts mapping	Contacts mapping	Tasks mapping	Notes mapping

ACCOUNTNO	Account Number	Ignore	Ignore	Ignore
COMPANY	Account Name	Parent Customer (Account Name)	Regarding (Account Name)	Regarding (Account Name)
CONTACT	Ignore	Address 1: Primary Contact Name	Ignore	Ignore
LASTNAME	Ignore	Last Name	Ignore	Ignore
DEPARTMENT	Ignore	Department	Ignore	Ignore
TITLE	Ignore	Job Title	Ignore	Ignore
SECR	Ignore	Assistant	Ignore	Ignore
PHONE1*	Main Phone*	Business Phone*	Ignore	Ignore
PHONE2	Other Phone*	Home Phone*	Ignore	Ignore
PHONE3	Address Phone*	Address 1: Phone*	Ignore	Ignore
FAX	Fax	Ignore	Ignore	Ignore
EXT1	Ignore, or create custom attribute ³	Ignore, or create custom attribute ³	Ignore	Ignore
EXT2	Ignore, or create custom attribute ³	Ignore, or create custom attribute ³	Ignore	Ignore
EXT3	Ignore, or create custom attribute ³	Ignore, or create custom attribute ³	Ignore	Ignore
EXT4	Ignore, or create custom attribute ³	Ignore, or create custom attribute ³	Ignore	Ignore
ADDRESS1	Address 1: Street 1	Address 1: Street 1	Ignore	Ignore
ADDRESS2	Address 1: Street 2	Address 1: Street 2	Ignore	Ignore
ADDRESS3	Address 1: Street 3	Address 1: Street 3	Ignore	Ignore
CITY	Address 1: City	Address 1: City	Ignore	Ignore
STATE	Address 1: State/Province	Address 1: State/Province	Ignore	Ignore
ZIP	Address 1: ZIP/Postal Code	Address 1: ZIP/Postal Code	Ignore	Ignore
COUNTRY	Address 1: Country	Address 1: Country	Ignore	Ignore
DEAR	Ignore	Salutation	Ignore	Ignore
SOURCE	Ignore	Lead Source	Ignore	Ignore
KEY1 ... KEY 5 ²	Ignore	Ignore, map to existing attribute, or create custom attribute ²	Ignore	Ignore
STATUS	Ignore	Ignore	Ignore	Ignore
NOTES	Ignore	Ignore	Ignore	Description
MERGECODES	Ignore	Ignore	Ignore	Ignore
CREATEDBY	Ignore, or create custom attribute ³	Ignore, or create custom attribute ³	Ignore	Ignore
CREATEDON	Ignore, or create custom attribute ³	Ignore, or create custom attribute ³	Ignore	Ignore
CREATEDAT	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
OWNER¹	Ignore¹	Ignore¹	Ignore¹	Ignore
LASTUSER	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
LASTDATE	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
LASTTIME	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
CALLBACKON	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
CALLBACKAT	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
CALLBKFREQ	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
LASTCONTON	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
LASTCONTAT	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
LASTATMPON	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
LASTATMPAT	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
MEETDATEON	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
MEETDATEAT	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
COMMENTS	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
PREVRESULT	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
NEXTACTION	Ignore	Ignore, or create custom attribute ³	Title	Title
ACTIONON	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
CLOSEDDATE	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore
USERDEF01 ... USERDEF10²	Ignore	Ignore, map to existing attribute, or create custom attribute ²	Ignore	Ignore
RECID	Ignore	Ignore, or create custom attribute ³	Ignore	Ignore

¹ The mappings shown in the table will result in all records being owned by the user who migrates the data. If your goal is to have more than one owner or someone else as the record owner, you can use one of the following approaches:

After migrating the records using the mapping described in this article, use Microsoft Dynamics CRM to bulk-assign the records to specific users. For an example of using Advanced Find to find and bulk-assign records, see Don't lose customers when a salesperson leaves your organization.
Instead of ignoring the OWNER column during mapping, map the OWNER column for accounts, contacts, and tasks to the Microsoft Dynamics CRM Owner attribute. You will also need to create and migrate a Users.csv file that includes a record for each user in the source data.

You will be prompted by Data Migration Manager to map each OWNER value to a Microsoft Dynamics CRM user, and be given the option to create a new user, if needed. For more information on migrating ownership data, see the topic "How Ownership Data is Migrated" in the Data Migration Manager Help file.

² For user defined fields, you have a choice on how to map the data. Select the option that makes sense given the information contained in your source data file. If you need to create custom attributes, see the topic "Custom Attributes" in the Data Migration Manager Help file.

³ For fields that exist in GoldMine version 6.0, but do not exist, by default, in Microsoft Dynamics CRM, you can either ignore the data or create a custom attribute. Review the data in your source files to see if you have useful data in this field that needs to be preserved.

* Microsoft Dynamics CRM has many attributes for telephone numbers. Verify that these mappings make sense for the phone numbers stored in GoldMine version 6.0.

Migrating the data

On the Start menu, click All Programs, click Microsoft Dynamics CRM, and then click Microsoft Dynamics CRM Data Migration Manager.
Click Start a migration.
Select the Start a new migration option, and then on the Get Started page, click Next.
Click Start a Migration.
Specify the migration name, enter GoldMine as the source system, and then click Next.
Select the .csv files you created: Accounts.csv, Contacts.csv, Notes.csv, Tasks.csv, and the optional Users.csv, and then click Next.
Specify the delimiters:
1. Select the delimiter used in the source files, and the character that is used to enclose fields that contain the delimiter.
2. Select the First row of each file contains column headings checkbox.
3. Preview each file to make sure it displays correctly, including using the horizontal scroll to check all columns.
4. Click Next.
  
  Note
  
  If errors are found while validating files, such as finding newline characters, a separate error page will be displayed. Troubleshoot any errors.
On the File Mapping page, click Next.
For each of the four, or five, files, select Map this file to an existing Microsoft Dynamics CRM entity, select the entity with the same name as the file, and then click Next.
On the File Summary page, click Next.
On the Column Mapping Results page, click Next.
For each column in each file, on the Map Column page, select the needed option, based on the mapping shown in the following GoldMine-Microsoft Dynamics CRM mapping table, and then click Next.

When you get to the Company column for the Contacts.csv, Notes.csv, and Tasks.csv files, after you map the column, you will see the Define Relationship page. On this page, select Account, select Account Name, and then click Next.
The Column Summary page appears. Click Next.
The User Summary page appears. Unless you created a Users.csv file and mapped ownership of the records, all records will be assigned to the current user. Click Next.
The Review Summaries page appears. Click Next.
The Start Migrating Data page appears. Click Migrate Data.
The Converting Data page appears,converting your data to the required format, and uploading it to your server. If no errors are found, the wizard will continue to the Migration Completed page.
- If no errors are found, click Next.
- If errors are found, the first 50 are displayed. To view additional errors and error details, click Export Errors.
Click Finish.

Your GoldMine version 6.0 data is now migrated. If you need to do another migration from GoldMine version 6.0, you can reuse these mappings by selecting the migration name you specified in step 5 when you start your new migration.

Migrate data from GoldMine version 6.0 to Microsoft Dynamics CRM

Preparing the data

Review the mapping table

Migrating the data

Related Links