PSA to Propel Your MSP Asset Mapping

PSA to Propel Your MSP Asset Mapping

Concept

Assets in the PSA normally have an associated type (Workstation, Firewall, Switch, etc.). Each type can be (but does have to be) mapped to an Asset Category in Propel Your MSP.

Example:


You can create / modify Asset Categories to better suit your own MSP specifics.

Company Company vs Account Asset Mapping Template

Two levels of mapping exist:
  1. Account "Master" Asset Mapping
    Sidebar: PSA Integration / Asset Mapping
  2. Each Company's individual Asset Mapping
    Sidebar: Selected Company / Asset Categories / Manage Company Asset Mapping
When accessing a Company for the very first time, the Account's "Master" Asset Mapping is copied over to the Company and becomes a distinct copy (i.e. modifying the Account's Master Asset Mapping will not modify the Company's Asset Mapping and vice-versa).

The same two-level concept goes for Assets Categories as well. When first accessing a Company, the Asset Categories in use are copied over to the Company.

How to use New Account Asset Categories in a Company?

When modifying any Company's Asset Mapping, some Asset Categories may have the "Account" badge beside them. This means that this particular Asset Category does not yet have its own copy in the Company's Asset Categories. Mapping a PSA type to it will simply cause a copy to be created in the Company. From then on, it will evolve independently as all the other Company Asset Categories.


Autotask PSA Considerations

Autotask PSA has both a Configuration Item Category and a Configuration Item Type. Propel uses the Configuration Item Type when configuring the asset mapping. In the example below, the asset's Category is "Standard", but its Type is "Workstation".

Configuration of Configuration Item Types

You can configure Configuration Item Types in "Admin / Features & Settings".
Note: Some instances have renamed "Configuration Item" to another terms, like "Asset" or "Device" in their "Local Terms & Symbols" configuration

Autotask PSA's User Defined Fields

Depending on your RMM, Autotask PSA may use different fields to store asset-related information. Some may be stored in User Defined Fields and you will need to map those to the corresponding field to have it imported in Propel Your MSP.


    • Related Articles

    • PSA Opportunity Sync Back to Propel

      Project Opportunities created in Propel can be pushed to the PSA. Once pushed, the following fields become read-only in Propel and are refreshed (during the daily sync) from the PSA: Material Cost Labor Cost Expected Start Date* Customer Response** ...
    • How to Structure your Asset Categories?

      A Budget is not a Quote One of Propel Your MSP's goals is to create a precise budget for the next 3 or 5 years. But a budget is not a detailed quote, nor should it be. It's a tool to help MSPs have a productive discussion with their client about the ...
    • Autotask PSA: Import Manufacturer and Model Number from the Autotask Product

      Autotask PSA Propel Your MSP, if no User Defined Field has been set in PSA Integration / Asset Mapping , will now import the Manufacturer and Model Number from the Autotask Product assigned to the Configuration Item. This often has more ...
    • How to Un-Propel a Company?

      Once a Company is Propelled, it must remain in that state for a minimum of 45 days. You can un-Propel any Company from the "Settings / Billing" page if that initial 45-day period is over. From the "Settings / Billing" screen Un-Propelling a Company ...
    • FAQ - PSA Integration

      How do I limit the number of companies imported in Propel Your MSP? You have full control over which Company Types are imported in Propel Your MSP from your PSA. The following example from ConnectWise Manage will only import customers with an ...