DataTools for Goldmine to SugarCRM Migration

Tue, 18 Dec 2007, 2:44pm

Pervasive DataTools offers solutions for migrating data from Goldmine to SugarCRM.

Goldmine to SugarCRM data migrations can be problematic because Goldmine implemented a proprietary method of linking child records in the .DBT files to the parent records in the .DBF files in versions of Goldmine that used a dBASE format for record management. The most common problem is retaining the relationship between the memo fields (child records that contain activities/events and history records) stored in .DBT files and Contact records that are stored in .DBF files.

The DataTools solution...

If you have the Goldmine application, you can create reports that contain both the parent (Contact) and child (Activities/Events/History) records. Then, print the report to a file on your workstation - rather than to a printer - and download the Data Parser for Unstructured Text to extract the records, with relationships intact, as needed. Export the data records to a CSV file from the Data Parser.

Then use the Data Builder for SugarCRM to map & transform the "raw" CSV data into the exact CSV structure that is ready to import into SugarCRM using the SugarCRM import utility.

- The Pervasive DataTools Team