Import Assets - Revision history

Dina at 08:32, 8 July 2020

2020-07-08T08:32:09Z

Dina at 10:18, 3 October 2018

2018-10-03T10:18:19Z

← Older revision		Revision as of 10:18, 3 October 2018
Line 1:		Line 1:
	{{importandexport}}		{{importandexport}}
	~~==Importing Assets==~~		__TOC__


			==Introduction==
	[[Assets\|Asset Management]] in CommitCRM lets you track and manage customer equipment and software licenses/subscriptions.		[[Assets\|Asset Management]] in CommitCRM lets you track and manage customer equipment and software licenses/subscriptions.

	You can import Assets from various data sources including Excel® files, CSV files, QuickBooks, etc.		You can import Assets from various data sources including Excel® files, CSV files, QuickBooks, etc.

			==Before importing Assets==
			Before you import Assets 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
			<br>
			We recommend to import the following data '''before''' importing Assets into CommitCRM:

			#[[Import_Accounts\|Import Accounts]] - when importing Assets 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 Assets they will be linked to existing Secondary Contact, otherwise new Secondary Contact will be created for Account

			<br>

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

	To import Assets:		To import Assets:
	#~~Please always '''backup your database''' prior to importing data.~~		#On the Main menu go to '''Tools > Import and Export > Import Assets''', and select the type of file to be imported (MS Excel®, Text (CSV), Paradox tables, dBase tables) .
	~~#From~~ the Main menu ~~select~~ '''Tools > Import and Export > Import Assets'''.		#Map the fields in the input file to the equivalent database fields in CommitCRM.You can find more information on assets fields and their usage in the Assets Management Guide, under the [[Assets#Asset Fields\|Asset Fields section]].<br> [[File:Import_assets_mapping_fields.png]]<br>
	~~#Select the file format.~~		#Guidelines in matching fields when importing Aseets: <br>(''Tip'': fields with name identical or similar to field name in CommitCRM will be mapped automatically.
	~~#Select~~ the type of ~~assets you want~~ to ~~import: '''Hardware~~, ~~Software~~, ~~or Other'''.~~		##Asset Name field is mandatory for importing Assets into CommitCRM
	#Select whether to link all imported assets to a selected Account or import them without assigning an Account to them (You can also import assets from the Assets tab in the Accounts window by right-clicking and selecting '''Import Assets'''. In this case all the imported assets will be linked to the selected Account).		## Asset Type - if mapped the type can be matched by name. <br> If type is not mapped or cannot be determined, user can select the type to be set for the imported Assets: <br>
	#Map the fields in the input file to the equivalent database fields in CommitCRM~~. Make sure to include mandatory asset fields, such as Asset Name~~. You can find more information on assets fields and their usage in the Assets Management Guide, under the [[Assets#Asset Fields\|Asset Fields section]].		## Asset Account - if Account field is not mapped, the imported Asset will not be linked to any Account. <br> If Account field is mapped and Account exists in CommitCRM, the Asset 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 Asset will be linked to the newly created record. <br>Note: In the import wizard there is an option to skip Asset creation if the Account is not found in CommitCRM): <br> [[File:Import_assets_set_status.png]]
			#Your Assets will now be imported.
			<br>


	<br>		<br>
	''Tip: Updating Existing Assets<br>		''Tip: Updating Existing Assets<br>

Sheli at 13:09, 28 January 2012

2012-01-28T13:09:44Z

← Older revision		Revision as of 13:09, 28 January 2012
Line 6:		Line 6:
	You can import Assets from various data sources including Excel® files, CSV files, QuickBooks, etc.		You can import Assets from various data sources including Excel® files, CSV files, QuickBooks, etc.

	To import Assets~~, on~~ the Main menu select '''Tools > Import and Export > Import Assets''':		To import Assets:
			#Please always '''backup your database''' prior to importing data.
			#From the Main menu select '''Tools > Import and Export > Import Assets'''.
	#Select the file format.		#Select the file format.
	#Select the type of assets you want to import: '''Hardware, Software, or Other'''.		#Select the type of assets you want to import: '''Hardware, Software, or Other'''.
	#Select whether to link all imported assets to a selected Account or import them without assigning an Account to them (You can also import assets from the Assets tab in the Accounts window by right-clicking and selecting '''Import Assets'''. In this case all the imported assets will be linked to the selected Account).		#Select whether to link all imported assets to a selected Account or import them without assigning an Account to them (You can also import assets from the Assets tab in the Accounts window by right-clicking and selecting '''Import Assets'''. In this case all the imported assets will be linked to the selected Account).
	#Map the fields in the input file to the equivalent database fields in CommitCRM. Make sure to include mandatory asset fields, such as Asset Name. You can find more information on assets fields and their usage in the Assets Management Guide, under the [[Assets#Asset Fields\|Asset Fields section]].		#Map the fields in the input file to the equivalent database fields in CommitCRM. Make sure to include mandatory asset fields, such as Asset Name. You can find more information on assets fields and their usage in the Assets Management Guide, under the [[Assets#Asset Fields\|Asset Fields section]].
			<br>
			''Tip: Updating Existing Assets<br>
			The primary key for an Asset is the '''Asset Code''' field. You can re-import Assets after they already exist in CommitCRM, using the same Asset Code, and existing assets will be updated with the new data from the input file. Again, always backup your database before performing imports.
			''

	==See Also==		==See Also==

CmtWikiAdminSysop at 14:19, 11 September 2009

2009-09-11T14:19:48Z

← Older revision		Revision as of 14:19, 11 September 2009
Line 15:		Line 15:
	*[[Assets]]		*[[Assets]]

	~~[[Category:New Users]]~~
	[[Category:Assets]]		[[Category:Assets]]
	[[Category:Import and Export]]		[[Category:Import and Export]]

Sheli: /* Importing Assets */

2009-09-11T12:34:07Z

Importing Assets

← Older revision		Revision as of 12:34, 11 September 2009
Line 1:		Line 1:
	{{importandexport}}		{{importandexport}}
	==Importing Assets==		==Importing Assets==
	~~__NO_TOC__~~
	[[Assets\|Asset Management]] in CommitCRM lets you track and manage customer equipment and software licenses/subscriptions.		[[Assets\|Asset Management]] in CommitCRM lets you track and manage customer equipment and software licenses/subscriptions.

Sheli at 12:25, 11 September 2009

2009-09-11T12:25:31Z

← Older revision		Revision as of 12:25, 11 September 2009
Line 1:		Line 1:
	{{importandexport}}		{{importandexport}}
			==Importing Assets==
			__NO_TOC__
	[[Assets\|Asset Management]] in CommitCRM lets you track and manage customer equipment and software licenses/subscriptions.		[[Assets\|Asset Management]] in CommitCRM lets you track and manage customer equipment and software licenses/subscriptions.

Yarden at 07:56, 13 August 2009

2009-08-13T07:56:07Z

← Older revision		Revision as of 07:56, 13 August 2009
Line 1:		Line 1:
			{{importandexport}}

	[[Assets\|Asset Management]] in CommitCRM lets you track and manage customer equipment and software licenses/subscriptions.		[[Assets\|Asset Management]] in CommitCRM lets you track and manage customer equipment and software licenses/subscriptions.

Yarden: /* See Also */

2009-08-11T12:14:34Z

Yarden at 09:04, 29 July 2009

2009-07-29T09:04:32Z

← Older revision		Revision as of 09:04, 29 July 2009
Line 8:		Line 8:
	#Select whether to link all imported assets to a selected Account or import them without assigning an Account to them (You can also import assets from the Assets tab in the Accounts window by right-clicking and selecting '''Import Assets'''. In this case all the imported assets will be linked to the selected Account).		#Select whether to link all imported assets to a selected Account or import them without assigning an Account to them (You can also import assets from the Assets tab in the Accounts window by right-clicking and selecting '''Import Assets'''. In this case all the imported assets will be linked to the selected Account).
	#Map the fields in the input file to the equivalent database fields in CommitCRM. Make sure to include mandatory asset fields, such as Asset Name. You can find more information on assets fields and their usage in the Assets Management Guide, under the [[Assets#Asset Fields\|Asset Fields section]].		#Map the fields in the input file to the equivalent database fields in CommitCRM. Make sure to include mandatory asset fields, such as Asset Name. You can find more information on assets fields and their usage in the Assets Management Guide, under the [[Assets#Asset Fields\|Asset Fields section]].

			==See Also==
			*[[Assets]]

			[[Category:New Users]]
			[[Category:Assets]]

Yarden at 09:03, 29 July 2009

2009-07-29T09:03:00Z

← Older revision		Revision as of 09:03, 29 July 2009
Line 1:		Line 1:
	Asset ~~management~~ in ~~Commit~~ lets you track and manage customer equipment and software licenses/subscriptions.		[[Assets\|Asset Management]] in CommitCRM lets you track and manage customer equipment and software licenses/subscriptions.

	You can import Assets from various data sources including Excel® files, CSV files, QuickBooks, etc.		You can import Assets from various data sources including Excel® files, CSV files, QuickBooks, etc.

← Older revision		Revision as of 08:32, 8 July 2020
Line 4:		Line 4:

	==Introduction==		==Introduction==
	[[Assets\|Asset Management]] in ~~CommitCRM~~ lets you track and manage customer equipment and software licenses/subscriptions.		[[Assets\|Asset Management]] in RangerMSP lets you track and manage customer equipment and software licenses/subscriptions.

	You can import Assets from various data sources including Excel® files, CSV files, QuickBooks, etc.		You can import Assets from various data sources including Excel® files, CSV files, QuickBooks, etc.
Line 13:		Line 13:
	* '''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 Assets into ~~CommitCRM~~:		We recommend to import the following data '''before''' importing Assets into RangerMSP:

	#[[Import_Accounts\|Import Accounts]] - when importing Assets 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 Assets 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 21:		Line 21:

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

	To import Assets:		To import Assets:
	#On the Main menu go to '''Tools > Import and Export > Import Assets''', 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 Assets''', 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~~.You can find more information on assets fields and their usage in the Assets Management Guide, under the [[Assets#Asset Fields\|Asset Fields section]].<br> [[File:Import_assets_mapping_fields.png]]<br>		#Map the fields in the input file to the equivalent database fields in RangerMSP.You can find more information on assets fields and their usage in the Assets Management Guide, under the [[Assets#Asset Fields\|Asset Fields section]].<br> [[File:Import_assets_mapping_fields.png]]<br>
	#Guidelines in matching fields when importing Aseets: <br>(''Tip'': fields with name identical or similar to field name in ~~CommitCRM~~ will be mapped automatically.		#Guidelines in matching fields when importing Aseets: <br>(''Tip'': fields with name identical or similar to field name in RangerMSP will be mapped automatically.
	##Asset Name field is mandatory for importing Assets into ~~CommitCRM~~		##Asset Name field is mandatory for importing Assets into RangerMSP
	## Asset Type - if mapped the type can be matched by name. <br> If type is not mapped or cannot be determined, user can select the type to be set for the imported Assets: <br>		## Asset Type - if mapped the type can be matched by name. <br> If type is not mapped or cannot be determined, user can select the type to be set for the imported Assets: <br>
	## Asset Account - if Account field is not mapped, the imported Asset will not be linked to any Account. <br> If Account field is mapped and Account exists in ~~CommitCRM~~, the Asset 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 Asset will be linked to the newly created record. <br>Note: In the import wizard there is an option to skip Asset creation if the Account is not found in ~~CommitCRM~~): <br> [[File:Import_assets_set_status.png]]		## Asset Account - if Account field is not mapped, the imported Asset will not be linked to any Account. <br> If Account field is mapped and Account exists in RangerMSP, the Asset 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 Asset will be linked to the newly created record. <br>Note: In the import wizard there is an option to skip Asset creation if the Account is not found in RangerMSP): <br> [[File:Import_assets_set_status.png]]
	#Your Assets will now be imported.		#Your Assets will now be imported.
	<br>		<br>
Line 36:		Line 36:
	<br>		<br>
	''Tip: Updating Existing Assets<br>		''Tip: Updating Existing Assets<br>
	The primary key for an Asset is the '''Asset Code''' field. You can re-import Assets after they already exist in ~~CommitCRM~~, using the same Asset Code, and existing assets will be updated with the new data from the input file. Again, always backup your database before performing imports.		The primary key for an Asset is the '''Asset Code''' field. You can re-import Assets after they already exist in RangerMSP, using the same Asset Code, and existing assets will be updated with the new data from the input file. Again, always backup your database before performing imports.
	''		''

← Older revision		Revision as of 12:14, 11 August 2009
Line 14:		Line 14:
	[[Category:New Users]]		[[Category:New Users]]
	[[Category:Assets]]		[[Category:Assets]]
			[[Category:Import and Export]]