Import Tickets - Revision history

Dina at 08:33, 8 July 2020

2020-07-08T08:33:42Z

Dina at 09:49, 12 July 2015

2015-07-12T09:49:38Z

← Older revision		Revision as of 09:49, 12 July 2015
Line 15:		Line 15:

	==Before importing your Tickets==		==Before importing your Tickets==
	Before you import your Tickets for the first time, we recommend that you go over the following checklist to make sure you perform the import in the most efficient way		Before you import your Tickets for the first time, we recommend that you go over the following checklist to make sure you perform the import in the most efficient way:

	* '''Backup your database''' – it is very important to backup your data before performing any imports. This will assure that you can undo the import if needed very easily. [[Backup_and_Restore_FAQ\|Click here]] for more details about performing a backup to your database		* '''Backup your database''' – it is very important to backup your data before performing any imports. This will assure that you can undo the import if needed very easily. [[Backup_and_Restore_FAQ\|Click here]] for more details about performing a backup to your database
	<br>		<br>

	We recommend to import the following data '''before''' importing Tickets into CommitCRM:		We recommend to import the following data '''before''' importing Tickets into CommitCRM:

Line 44:		Line 43:

	==Deleting imported Tickets==		==Deleting imported Tickets==
	'''Important''': It is highly recommend to backup your data before using this tool.		'''Important''': It is highly recommend to backup your data before using this tool.<br>
	Imported Tickets can be un-imported/deleted using ''Tools > Import and Export > Delete Imported Tickets..''. This tool ~~allow~~ to delete all Tickets that were imported in a single batch import. Note: this action will also delete Accounts/Contacts/Assets that were created by this single import.		Imported Tickets can be un-imported/deleted using ''Tools > Import and Export > Delete Imported Tickets..''. This tool allows to delete all Tickets that were imported in a single batch import. Note: this action will also delete Accounts/Contacts/Assets that were created by this single import.

	''Tip: Updating Existing Tickets''		''Tip: Updating Existing Tickets''<br>
	The primary key for a Ticket is the Ticket Number field. You can re-import Tickets after they already exist in CommitCRM, using the same Ticket Number, ~~and~~ existing tickets will be updated with the new data from the input file. Again, always backup your database before performing imports.		The primary key for a Ticket is the Ticket Number field. You can re-import Tickets after they already exist in CommitCRM, using the same Ticket Number, as a result existing tickets will be updated with the new data from the input file. Again, always backup your database before performing imports.

Dina: Created page with "{{importandexport}} TOC ==Introduction== Import Tickets allows you to import all customer support tickets and saves your time: * Import closed Tickets from an old sys..."

2015-07-12T09:44:32Z

Created page with "{{importandexport}} __TOC__ ==Introduction== Import Tickets allows you to import all customer support tickets and saves your time: * Import closed Tickets from an old sys..."

New page

{{importandexport}}

__TOC__

==Introduction==

Import Tickets allows you to import all customer support tickets and saves your time:

* Import closed Tickets from an old system into CommitCRM and keep service history of your customers.
* Import open Tickets from an old system into CommitCRM and continue to work on them in CommitCRM
* Imported Tickets are linked to existing Accounts or new Account records are created during the import.
* Easily undo the import and deleted all imported records

You can import Tickets from various data sources including Excel® files, CSV files.

==Before importing your Tickets==
Before you import your Tickets for the first time, we recommend that you go over the following checklist to make sure you perform the import in the most efficient way

* '''Backup your database''' – it is very important to backup your data before performing any imports. This will assure that you can undo the import if needed very easily. [[Backup_and_Restore_FAQ|Click here]] for more details about performing a backup to your database
 

We recommend to import the following data '''before''' importing Tickets into CommitCRM:

#[[Import_Accounts|Import Accounts]] - when importing Tickets they will be linked to existing Account if it was recognized based on one of the following Account fields: File As, Account # (Number), internal Record ID. In case Account does not exist or could not be found or if there are duplicate Account records - new Account will be created.
#[[Import_Accounts#Importing_Secondary_Contacts|Import Secondary Contacts]] - when importing Tickets they will be linked to existing Secondary Contact, otherwise new Secondary Contact will be created for Account
#[[Import_Assets|Import Assets]] - when importing Tickets they will be linked to existing Asset if it was recognized based on Asset Code or internal Record ID. In case Assets does not exist - new Asset will be created.

 

==Importing Tickets from Excel/CSV/Text Files==
You can import Tickets into CommitCRM from almost any data source that you may have, including Excel sheets, and exported files from other software.

To import Tickets:
#On the Main menu go to '''Tools > Import and Export > Import Tickets''', and select the type of file to be imported (MS Excel®, Text (CSV), Paradox tables, dBase tables) .
#Map the fields in the input file to the equivalent database fields in CommitCRM. [[File:Import_tickets_mapping_fields.png]] 
#Guidelines in matching fields when importing Tickets: (''Tip'': fields with name identical or similar to field name in CommitCRM will be mapped automatically.
## Ticket Description field is mandatory for importing Tickets into CommitCRM.
## Ticket Status - if mapped the status can be matched by name or numeric code. See the possible values [[API_Reference_Manual#Ticket_Fields|here]]. If status is not mapped or cannot be determined, user can select the status to be set for the imported Tickets: [[File:Import_tickets_set_status.png]]
## Ticket Manager - if mapped the Manager can be matched by nickname or Employee internal Record ID. If the Manager is not mapped or cannot be determined, user can select the Manager to be assigned for the imported Tickets: [[File:Import_tickets_set_manager.png]]
## Ticket Account - if Account field is not mapped, the imported Tickets will be linked to the 'Business Account' record. (Tickets can be then moved to the correct Account using ''Tickets > Tools > Move Ticket to Another Account'' ). If Account field is mapped and Account exists in CommitCRM, the Ticket will be linked to existing Account. In case mapped Account does not exist in CommitCRM or does not match any Account, new Account will be created and Ticket will linked to the newly created record. Note: In the import wizard there is an option to skip Ticket creation if the Account is not found in CommitCRM): [[File:Import_tickets_account_options.png]]
#Your Tickets will now be imported.
 

==Deleting imported Tickets==
'''Important''': It is highly recommend to backup your data before using this tool.
Imported Tickets can be un-imported/deleted using ''Tools > Import and Export > Delete Imported Tickets..''. This tool allow to delete all Tickets that were imported in a single batch import. Note: this action will also delete Accounts/Contacts/Assets that were created by this single import.

''Tip: Updating Existing Tickets''
The primary key for a Ticket is the Ticket Number field. You can re-import Tickets after they already exist in CommitCRM, using the same Ticket Number, and existing tickets will be updated with the new data from the input file. Again, always backup your database before performing imports.

==See Also==
*[[Import Accounts]]
*[[Import_Accounts#Importing_Secondary_Contacts|Import Secondary Contacts]]
*[[Import_Assets|Import Assets]]
*[[Ticket Management]]
*[[Backup_and_Restore_FAQ|Backup & Restore FAQ]]

[[Category:Import and Export]]

← Older revision		Revision as of 08:33, 8 July 2020
Line 7:		Line 7:
	Import Tickets allows you to import all customer support tickets and saves your time:		Import Tickets allows you to import all customer support tickets and saves your time:

	* Import closed Tickets from an old system into ~~CommitCRM~~ and keep service history of your customers.		* Import closed Tickets from an old system into RangerMSP and keep service history of your customers.
	* Import open Tickets from an old system into ~~CommitCRM~~ and continue to work on them in ~~CommitCRM~~		* Import open Tickets from an old system into RangerMSP and continue to work on them in RangerMSP
	* Imported Tickets are linked to existing Accounts or new Account records are created during the import.		* Imported Tickets are linked to existing Accounts or new Account records are created during the import.
	* Easily undo the import and deleted all imported records		* Easily undo the import and deleted all imported records
Line 19:		Line 19:
	* '''Backup your database''' – it is very important to backup your data before performing any imports. This will assure that you can undo the import if needed very easily. [[Backup_and_Restore_FAQ\|Click here]] for more details about performing a backup to your database		* '''Backup your database''' – it is very important to backup your data before performing any imports. This will assure that you can undo the import if needed very easily. [[Backup_and_Restore_FAQ\|Click here]] for more details about performing a backup to your database
	<br>		<br>
	We recommend to import the following data '''before''' importing Tickets into ~~CommitCRM~~:		We recommend to import the following data '''before''' importing Tickets into RangerMSP:

	#[[Import_Accounts\|Import Accounts]] - when importing Tickets they will be linked to existing Account if it was recognized based on one of the following Account fields: File As, Account # (Number), internal Record ID. In case Account does not exist or could not be found or if there are duplicate Account records - new Account will be created.		#[[Import_Accounts\|Import Accounts]] - when importing Tickets they will be linked to existing Account if it was recognized based on one of the following Account fields: File As, Account # (Number), internal Record ID. In case Account does not exist or could not be found or if there are duplicate Account records - new Account will be created.
Line 28:		Line 28:

	==Importing Tickets from Excel/CSV/Text Files==		==Importing Tickets from Excel/CSV/Text Files==
	You can import Tickets into ~~CommitCRM~~ from almost any data source that you may have, including Excel sheets, and exported files from other software.		You can import Tickets into RangerMSP from almost any data source that you may have, including Excel sheets, and exported files from other software.

	To import Tickets:		To import Tickets:
	#On the Main menu go to '''Tools > Import and Export > Import Tickets''', and select the type of file to be imported (MS Excel®, Text (CSV), Paradox tables, dBase tables) .		#On the Main menu go to '''Tools > Import and Export > Import Tickets''', and select the type of file to be imported (MS Excel®, Text (CSV), Paradox tables, dBase tables) .
	#Map the fields in the input file to the equivalent database fields in ~~CommitCRM~~.<br> [[File:Import_tickets_mapping_fields.png]]<br>		#Map the fields in the input file to the equivalent database fields in RangerMSP.<br> [[File:Import_tickets_mapping_fields.png]]<br>
	#Guidelines in matching fields when importing Tickets: <br>(''Tip'': fields with name identical or similar to field name in ~~CommitCRM~~ will be mapped automatically.		#Guidelines in matching fields when importing Tickets: <br>(''Tip'': fields with name identical or similar to field name in RangerMSP will be mapped automatically.
	## Ticket Description field is mandatory for importing Tickets into ~~CommitCRM~~.		## Ticket Description field is mandatory for importing Tickets into RangerMSP.
	## Ticket Status - if mapped the status can be matched by name or numeric code. See the possible values [[API_Reference_Manual#Ticket_Fields\|here]].<br> If status is not mapped or cannot be determined, user can select the status to be set for the imported Tickets: <br>[[File:Import_tickets_set_status.png]]		## Ticket Status - if mapped the status can be matched by name or numeric code. See the possible values [[API_Reference_Manual#Ticket_Fields\|here]].<br> If status is not mapped or cannot be determined, user can select the status to be set for the imported Tickets: <br>[[File:Import_tickets_set_status.png]]
	## Ticket Manager - if mapped the Manager can be matched by nickname or Employee internal Record ID. <br> If the Manager is not mapped or cannot be determined, user can select the Manager to be assigned for the imported Tickets:<br>[[File:Import_tickets_set_manager.png]]		## Ticket Manager - if mapped the Manager can be matched by nickname or Employee internal Record ID. <br> If the Manager is not mapped or cannot be determined, user can select the Manager to be assigned for the imported Tickets:<br>[[File:Import_tickets_set_manager.png]]
	## Ticket Account - if Account field is not mapped, the imported Tickets will be linked to the 'Business Account' record. (Tickets can be then moved to the correct Account using ''Tickets > Tools > Move Ticket to Another Account'' ).<br> If Account field is mapped and Account exists in ~~CommitCRM~~, the Ticket will be linked to existing Account. <br>In case mapped Account does not exist in ~~CommitCRM~~ or does not match any Account, new Account will be created and Ticket will linked to the newly created record. <br>Note: In the import wizard there is an option to skip Ticket creation if the Account is not found in ~~CommitCRM~~): <br> [[File:Import_tickets_account_options.png]]		## Ticket Account - if Account field is not mapped, the imported Tickets will be linked to the 'Business Account' record. (Tickets can be then moved to the correct Account using ''Tickets > Tools > Move Ticket to Another Account'' ).<br> If Account field is mapped and Account exists in RangerMSP, the Ticket will be linked to existing Account. <br>In case mapped Account does not exist in RangerMSP or does not match any Account, new Account will be created and Ticket will linked to the newly created record. <br>Note: In the import wizard there is an option to skip Ticket creation if the Account is not found in RangerMSP): <br> [[File:Import_tickets_account_options.png]]
	#Your Tickets will now be imported.		#Your Tickets will now be imported.
	<br>		<br>
Line 47:		Line 47:

	''Tip: Updating Existing Tickets''<br>		''Tip: Updating Existing Tickets''<br>
	The primary key for a Ticket is the Ticket Number field. You can re-import Tickets after they already exist in ~~CommitCRM~~, using the same Ticket Number, as a result existing tickets will be updated with the new data from the input file. Again, always backup your database before performing imports.		The primary key for a Ticket is the Ticket Number field. You can re-import Tickets after they already exist in RangerMSP, using the same Ticket Number, as a result existing tickets will be updated with the new data from the input file. Again, always backup your database before performing imports.

Import Tickets - Revision history

Dina at 08:33, 8 July 2020

Dina at 09:49, 12 July 2015

Dina: Created page with "{{importandexport}} __TOC__ ==Introduction== Import Tickets allows you to import all customer support tickets and saves your time: * Import closed Tickets from an old sys..."

Dina: Created page with "{{importandexport}} TOC ==Introduction== Import Tickets allows you to import all customer support tickets and saves your time: * Import closed Tickets from an old sys..."