Opportunities Import Fields

When you import opportunity information, the import process adds a new opportunity record in DPS for each opportunity in the .CSV file that does not already exist in DPS.

Imported Opportunity Information

You can import any standard or custom data that you enter on any tabs in the Opportunities area, with the exception of fields in grids and calculated fields (for example, the Weighted Revenue and Days Open fields).

Note that if the proper data match between fields is not allowed, the record will not be imported from the .CSV file and an error will be recorded to alert you of the issue

The following table provides notes about some of the imported fields. (This is not a complete list of the fields you can import).

Field	Notes
Opportunity Name	You must map this field in order to import an opportunities.
Probability	The probability for the opportunity must match either the code or the description of a probability in the drop-down list of standard probabilities. If it does not, the opportunity is imported but the Probability field is left blank.
Date Opened	Dates to be imported into the Date Opened field should be in the date format specified in the My Settings dialog box of the person who runs the import process.
Organization	If your firm sets up organizations, you have the option to assign opportunities to organizations. Each value in the organization field in your .CSV file must match an existing organization name exactly. If the organization for an opportunity you are importing does not match an existing organization , the opportunity is imported but the Organization field is left blank.
Primary Client	The import process checks for an exact match with an existing firm name or alias. If the firm already exists in DPS, the client is associated with that firm. If no match is found, it is automatically added for you.
Primary Contact	To import primary contacts for opportunities, you must map .CSV fields to Primary Contact First Name, Primary Contact Last Name, and Firm (the primary client firm). The import process checks for an existing record. Duplicates are identified by matching on one of the following: First name, last name, and firm Preferred name, last name, and firm Email address If one of the names and the firm match or if the email address matches, the record in the .CSV file is considered a duplicate. If no match is found, the contact is displayed in the New Firm Contact Records dialog box so you can indicate if you want a contact record created for it in DPS.
Project Manager Principal Supervisor	To import project managers, principals, or supervisors for opportunities, you must map first name and last name fields in the .CSV file to the corresponding first name and last name fields in DPS. The import process checks for an existing employee with the same first name and last name or preferred name and last name. If the employee already exists in DPS, he or she is assigned to the indicated role for the opportunity. If no match is found, the opportunity is imported but no employee is assigned to that role for the opportunity.
State/Province and Country	The country in an opportunity location must match a country in the drop-down list of standard country names. If it does not, the Country field is left blank. If an address includes both a state/province and a country, the state/province in the .CSV file must match either a state/province code or state/province name in the drop-down list of standard states for that country. If it does not, the State/Province field is left blank. If an address includes a valid state/province code or name but not a country, the import process assigns the country for that state to the Country field.
County	The county in an opportunity location does not have to exist in the drop-down list of standard counties in the list of Settings. If it is not in that list, it is entered in the County field for that opportunity record but is not added to the standard list of counties.
Type	The project type is imported.
Total Contract Value	The total value of the contract is imported.
Drop-down fields	Except County as noted above, a field in the .CSV file that is mapped to a field in DPS that has a drop-down list of valid values must contain a value that exactly matches one of those valid values. If the value in the import file does not match a valid value for the field in DPS, the opportunity is imported but that field is left blank.
Custom fields (general)	The format of data to be imported into a custom field must be compatible with the type of custom field. For example, you can only import numeric data into a number field. If the format is not correct, the contact is not imported and you will be notified of the issue in the error log. The import continues through the rest of the records in your source file.
Custom date field	Dates to be imported into a custom date field should be in the date format specified in the My Preferences dialog box of the person who runs the import process. For example, if your date preferences are set to include the month before the day, then the dates in the import source file should also have the month before the day.
Custom drop-down field	Values to be imported into a custom drop-down field must match one of the standard values for that field. If a value does not match a standard value, the record is not imported and you will be notified of the issue in the error log. The import continues through the rest of the records in your source file. However, you can choose to not limit any drop-down to the list of values, which means users can enter a value that is not in a list. If that option is selected, then the record is imported with that value but the value is not added to the list of values for the field properties.
Custom lookup field	Values to be imported into a custom lookup field must match a name exactly. For employee or contact lookups, they must match either a first name + last name + firm or preferred name + last name + firm. For a firm lookup, they must match either a firm name or alias. If there is no match, the record is not imported and you will be notified of the issue in the error log. The import continues through the rest of the records in your source file.
Custom check boxes	Custom check boxes are selected (checked) if the imported value is either Yes or Y and are not selected if the value is No or N.