What Can I Expect from the SumoQuote Migration to JobNimbus?

What will be migrated?

The below items will be migrated:

• Layouts
  • ‘My’ items will be converted to ‘Shared’ items during migration
  • 'My’ items will be prepended with the SQ Users Email Address
  • ‘My’ items will not be checked for duplicates, and all will be migrated, it's important to have the customer clean up their ‘My’ items
  • Duplicates found in Shared items will be identified using a Name Match, and prepended with ‘SQ Duplicate -’
•  Templates
  •  Includes: Introduction, Quote Details, Authorization, Custom Text Page & Email Templates
  •  ‘My’ items will be converted to ‘Shared’ items during migration
  • ‘My’ items will be prepended with the SQ Users Email Address
  • 'My’ items will not be checked for duplicates, and all will be migrated, it's important to have the customer clean up their ‘My’ items
  • Duplicates found in Shared items will be identified using a Name Match, and prepended with ‘SQ Duplicate -’
• Quick Text
  • ‘My’ items will be converted to ‘Shared’ items during migration
  • ‘My’ items will be prepended with the SQ Users Email Address
  •  ‘My’ items will not be checked for duplicates, and all will be migrated, it's important to have the customer clean up their ‘My’ items
  • Duplicates found in Shared items will be identified using a Name Match, and prepended with ‘SQ Duplicate -’
• PDF Library
  • ‘My’ items will be converted to ‘Shared’ items during migration
  • ‘My’ items will be prepended with the SQ Users Email Address
  •  ‘My’ items will not be checked for duplicates, and all will be migrated, it's important to have the customer clean up their ‘My’ items
• Measurement Categories
  • Any identified duplicates will not be migrated from SQ
  • Any categories in SQ, but not in JN will be created in JN
• Measurement Tokens
  •  Any identified duplicates will not be migrated from SQ
  •  Any missing tokens will be merged into the categories that have been configured inside of JN
• Product List
  • Default pricing
  • Calculations
  • Duplicate items will be identified based on a Name & UoM (unit of measure) match, in the event of a duplicate item, the SQ product will not be migrated over, instead it will be matched up with the JN product, and mapped to any Templates or Layouts that use the SQ product
  • JN Pricing will be taken as the source of truth, meaning any item found in both JN and SQ, the pricing of JN will be observed
  • Due to the fact that SQ has Material and Labor costs, if there are values in SQ’s Labor cost, and Material/Labor tracking is not enabled in JN, we will abort the migration, and require the customer to turn on Material/Labor tracking in JN
  • JN Requires that a product has a UoM, if a SQ product does not have a UoM, it will be migrated using “Items”. This can be updated at any time in JN Settings.
•  Email Settings
  • CC / BCC including the set filters
  • Duplicates will be ignored, and missing email addresses will be added from SQ

What will not be migrated?

The following items will not be migrated over:

• Projects
• Reports (Estimates)
• API Keys - new ones can be created within JN if needed.
• Webhooks
• Measurement Documents (EagleView, Hover, RoofScope, or File Uploads)
  • If you have ordered EagleView reports through SQ, these will not automatically show up in JN.
    However, you will be able to Search for these reports and add them to a Job or Contact within
    JN. No information is lost.
  • If you have RoofScope, Uploaded files, or Hover measurement documents applied to any
    projects in SQ, these will not be migrated to JN jobs or contacts. Hover measurements can be
    searched and applied in JN.
•  Price Lists (the lists created from the main product list where you can change pricing)
  • No custom built price lists
  • No supplier related price lists
• Users
  • These will need to be set up within JobNimbus, we will not create users based on the team page
• Locations
  • SQ is a 1 location account that leveraged Multi-Pricelists to achieve Multi-Location like functionality
  • the migration will not create or change any JN locations
  • all SQ account content will be migrated to your JN Primary location.

• Solar related artifacts (this was an optional add-on, and will not affect most SQ customers)
  • Layouts & templates specific to the Solar add-on will not be migrated
• Email Settings
  • Email Templates - this refers to the Send for Signing, Quote Signed, Send for Review, etc emails listed under email settings.
  • Modifications to these templates within SQ will not show up in your JN account

• Financing settings - Sunlight & manual entries in financing
  • Financing plans from your SQ account will not be migrated to your JN account
  • Financing when enabled on layouts and templates will be disabled during the migration. Financing will need to be manually re-enabled once the migration is completed.

• Page/Notification Settings
  • Profit settings (margin slider, min margin, profitability)
  • Title Page settings
  • Price Adjustments - discounts and markups
    
    • discounts will remain on layouts and templates - the settings will not update in JN. Once your JN settings have been updated, you will be able to edit discounts within your estimates, layouts and templates.
  • Email notifications for clicks, opens & bounces
• Taxes
  • Required and Optional taxes will be removed from all layouts and Estimate Details templates
  • Taxes will need to be configured through JN settings
• Orders
  • Templates
  • Layouts
  • Page Settings
• Invoice Templates modified within layouts
• Dashboard
  ○ no data from won/lost/open projects will be migrated
• Billing / Subscription Details

Will I lose functionality when I migrate to JobNimbus?

Generally speaking, no! The New Sales Experience in JN will function and have the same features (maybe even a few new ones) as SQ. Navigation to estimates, estimate settings, calculations & measurements will be different, but all of the features you love about SQ are part of the JN estimating experience. That being said, there are a few differences that may impact your workflow and these are outlined below:

• Markups are not available in the new sales experience within JN as a price adjustment option.
  • All markups will be removed from your layouts and templates. There will not be a way to update these.
  • All discounts will remain available on layouts and templates, and will become editable once settings have been updated in JN.

• Taxes
  • Although you can configure taxes and apply taxes to estimates once using JN, the experience will be different.
  • You will only have the option to select a single tax on estimates, and will not have the option of creating required taxes.
  • You will still be able to apply a tax to a layout and template and save this, however after you have configured your tax settings in JN, you will need to go through each layout and template and select the tax again.

• Branding
  • Tag lines from the branding page in SQ are not currently available in JN. These will not show up on your Cover page of estimates
  • Company Info will no longer show up on your cover page. This has been replaced by Sales Rep info. Each cover page will have the phone and email of the job’s sales rep included.
  • We are working on a plan to allow for this content, but as of yet, you will notice it is not available.
  • Logo & Account colors - these will not be updated from SQ. These will remain whatever has been set up in your JN account.
  • Report Theme - this will need to be set up through your JN Estimate settings. All the themes are the same as SQ, but this will need to be set in your JN account.
• Integration with RoofScope
  • JN does not support the SQ direct integration with RoofScope. CSV files from RoofScope will also not be uploaded into the measurements page.

What will be the state of the SumoQuote Account after migration?

The SumoQuote account will remain operational for 30 days to support businesses that have in-flight jobs that may require Homeowner signatures, or edits to existing estimates already sent out. It is important to note that the migration is not an ongoing sync, so any changes made to the SQ account after the data migration will not be reflected in JN. It is also imperative to note that the integration/automation that allows for the creation of a Project in SQ when a JN Job is created will be disconnected, meaning that JobNimbus needs to be leveraged for estimating purposes.

In-flight estimates in which the project is already linked to the JN job/contact will still update with signed estimates for that 30 days. If there are estimates in which that 30 day period may not be sufficient, we recommend recreating these estimates within JN so that your workflow is not interrupted.

After the 30 days, the SQ account will become Read-Only. Users will still be able to login and access historical data, but no changes can be made within the account. Users will not lose access to their accounts and will be able to login as they normally would.