Import Assets: Difference between revisions

From RangerMSP Wiki - PSA software for MSPs and IT services providers
Jump to navigation Jump to search
No edit summary
No edit summary
 
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.
''
''



Latest revision as of 08:32, 8 July 2020

Import and Export > Import Assets


Introduction

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.

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. Click here for more details about performing a backup to your database


We recommend to import the following data before importing Assets into RangerMSP:

  1. 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.
  2. Import Secondary Contacts - when importing Assets they will be linked to existing Secondary Contact, otherwise new Secondary Contact will be created for Account


Importing Assets from Excel/CSV/Text Files

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:

  1. 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) .
  2. 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 Asset Fields section.

  3. Guidelines in matching fields when importing Aseets:
    (Tip: fields with name identical or similar to field name in RangerMSP will be mapped automatically.
    1. Asset Name field is mandatory for importing Assets into RangerMSP
    2. Asset Type - if mapped the type can be matched by name.
      If type is not mapped or cannot be determined, user can select the type to be set for the imported Assets:
    3. Asset Account - if Account field is not mapped, the imported Asset will not be linked to any Account.
      If Account field is mapped and Account exists in RangerMSP, the Asset will be linked to existing Account.
      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.
      Note: In the import wizard there is an option to skip Asset creation if the Account is not found in RangerMSP):
  4. Your Assets will now be imported.




Tip: Updating Existing Assets
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.

See Also