|
|
Kaseya 365
- Complete the actions documented in the Getting Started
- Setup KaseyaOne and Single Sign On with your Kaseya 365 components
- Complete 'Kaseya 365 Essentials' eLearning module in Kaseya University
- Complete the self-guided onboarding task walkthroughs in each component
|
|
|
Compliance Manager GRC
- Complete the actions documented in the Getting Started
- Log in to the RapidFire Tools Portal at your IT Portal using your credentials
- Click on "Organizations" from the top menu
- Select "All Organizations" from the side menu and click "Add Organization"
|
|
Network Detective PRO
- Complete the actions documented in the Getting Started
- Log in to the RapidFire Tools Portal at your IT Portal using your credentials
- Click on "Organizations" from the top menu
- Select "All Organizations" from the side menu and click "Add Organization"
|
|
|
Autotask
- Complete the actions documented in the Getting Started
- Ensure the customer has received Autotask login credentials and can successfully log in to Autotask
- Setup Autotask Integration.
- Add branding logo into Autotask by navigating to Admin > Application Wide Features > logos.
- Review and implement the Allowlist requirements for IP addresses and URLs
- Bring a sample invoice and contract to the session.
- For Data Migration Purposes, review available import entities and import templates in Autotask by navigating to Admin > Application Wide Features > Downloads
BMS to Autotask Data Migration: Requirements and Caveats
- Any HTML Formatting contained in BMS Ticket Time Entries will be converted to plain text, including but not limited to HTML flags and formatting. This does not affect BMS Ticket Descriptions or Notes.
- Attachments are not transferred.
- Following entities are migrated with the BMS Migrator Tool:
- Companies
- Contacts
- Tickets
- Ticket Notes
- Ticket Time Entries
All of the above, including timelines will be covered in detail during the Project Kick-Off Call.
BMS to Autotask Data Migration: Checklist
- Ensure the customer has received Autotask login credentials and can successfully log in to Autotask
- Setup Autotask Integration.
- Add branding logo into Autotask by navigating to Admin > Application Wide Features > logos.
- Review and implement the Allowlist requirements for IP addresses and URLs
- Bring example of current invoice and corresponding customer contract to Scheduled Consulting Session
- Provide Go-Live Target Date & current subscription end date
- Review BMS dataset and overall state of data to be migrated
ConnectWise to Autotask Data Migration: Requirements and Caveats
- To run the CW to Autotask Migration tool you will need to request the following: ConnectWise Client ID (This can be generated here: https://developer.connectwise.com/ClientID
- Requesting the CW Client ID could take up to 5 business days to be processed by CW and this could impact onboarding timelines. Please take this into consideration.
- Depending on the volume of data to be synced from ConnectWise Manage, the migration can take as many as 7 to 12 business days to fully complete.
- If your ConnectWise Instance is on premise whitelisting of IP addresses may be required. This will be confirmed by your Autotask Consultant.
📌 Here is a list (not exclusive) of items the migration tool will not migrate from ConnectWise Manage:
- Unapproved or Approved billing items (Tickets Time entries, Project Tasks/tickets charges, Recurring services, Block /Retainer purchase, Milestones)
- Expenses
- Invoice History & Invoice Templates
- Contracts and Billing Agreements
- Product Catalogue (Products) & Service Catalogue (Services)
- Charges on Tickets/Projects/Contracts
- Timesheets
- Procurement Items & Purchase Orders
- Ticket Schedules/Service Calls
- Tax configurations
- Tickets Issues and Sub Issue Types (All Tickets will be migrated across with a ‘blank’ issue and sub issue type)
- Tickets Boards
- Reports
- Configuration Items
ConnectWise to Autotask Data Migration: Checklist
- Ensure the customer has received Autotask login credentials and can successfully log in to Autotask
- Setup Kaseya One & Autotask Integration.
- Add branding logo into Autotask by navigating to Admin > Application Wide Features > logos.
- Review and implement the Allowlist requirements for IP addresses and URLs
- Bring example of current invoice and corresponding customer contract to Scheduled Consulting Session
- Provide Go-Live Target Date & current subscription end date
- Review CW dataset and overall state of data to be migrated
- ConnectWise Client ID (This can be generated here
- ConnectWise Base URL and Company ID
- ConnectWise API user public Keys
- ConnectWise API user Private Keys
- Create in Autotask, an API User, in Admin> account settings & users> Resources /Users (HR) here)
- In the API user, Tracking Identifier section, please select “Generic Import Utility” as the Integration Vendor
- Provide Go-Live Target Date & current subscription end date
|
|
BMS
- Complete the actions documented in the Getting Started
- Setup BMS integration
- Add branding logo to BMS
- Review/implement allowlist requirements
- Bring invoice/contract example to session
|
|
ConnectBooster
|
|
IT Glue
- Complete the actions documented in the Getting Started
- Highly recommend completing IT Glue Deployment Guide
|
|
MyGlue
- Complete the actions documented in the Getting Started
- Require access to non-business email for test MyGlue user
|
|
myITprocess
- Complete the actions documented in the Getting Started
- IT Provider Admin enters integration credentials/API keys
|
|
Network Glue
- Complete the actions documented in the Getting Started
- Ensure target network and Windows 10/Server machine for Collector
|
|
Kaseya Quote Manager
- Complete the actions documented in the Getting Started
- Confirm access and supplier feed setup
- Customer reviews supplier integration and product feed setup guides
- Customer reviews help documentation on setup and featured videos
|
|
Vorex
- Complete the actions documented in the Getting Started
- Setup Vorex integration
- Add branding logo to Vorex
- Review/implement allowlist requirements
- Bring invoice/contract example to session
|
|
|
Datto Networking
|
|
Datto Secure Edge
- Complete the actions documented in the Getting Started
- Login to portal.dattobackup.com
- Register devices to Partner Portal
- Build new network along with name for networking device
- Device powered on and connected for call
-
NOTE: Ensure DHCP, routing, VLAN 1 set up for devices to get IPs
|
|
|
Datto RMM
- Complete the actions documented in the Getting Started
- Log into your DRMM instance and setup Kaseya One & DRMM Integration
- Add custom branding to your Datto RMM account, including the web interface, the Agent and the Agent Browser, and the end-user support request form.
- Review and implement the Allowlist requirements for IP addresses and URLs – required for seamless connectivity to the Datto RMM web interface and between Agents. Agents.
- Review the DRMM Management Hierarchy (Global/Site/Device) - Fundamentals and terminology
- Create AV exclusion for the RMM Agent. Agent.
- Bring working example of policy, script, custom component to be configured in DRMM to Scheduled Consulting Session
Migration Purposes
- Review structure of sites in existing RMM Platform.
- Complete Site Import Spreadsheet
- Review deployment methods – Network Discovery, Azure and GPO
-
Footnote: This is a tool we use internally to assist with the initial onboarding of customer devices into DRMM, provided as a convenience for people who pay for an implementation.
- The onboarding accelerator tool can generate DRMM sites, if desired, from a CSV list. It can also generate a deployment script that can be imported into the old RMM in order for the customer to use the old RMM to deploy DRMM, for Windows/Mac/Linux machines.
- The tool is used by Datto consultants internally and the script it generates is provided as is. It's expected that the customer will make use of the other deployment methods post implementation, such as AD GPO deployment, network discovery, or manual installation where necessary.
|
|
Traverse
Traverse Cloud
-
Ensure you have received all necessary account details and login credentials from Kaseya for your Traverse Cloud instance.
-
Log in to your Traverse Cloud instance using the provided credentials and set up two factor authentication.
-
Change your password for both your traverse and superuser accounts.
-
Familiarize yourself with the interface and navigation.
-
Install your DGE-Extension.
|
|
VSA 10
VSA 10 Cloud
VSA 10 On-Prem
|
|
VSA 9
VSA 9 Cloud
VSA 9 On-Prem
|
|
|
BullPhish ID
- Complete the actions documented in the Getting Started
- Verify logins are created/available for all needing access to the tenant
|
|
Cyber Hawk
- Complete the actions documented in the Getting Started
- Verify logins are created/available for all needing access to the tenant
|
|
Dark Web ID
- Complete the actions documented in the Getting Started
- Verify logins are created/available for all needing access to the tenant
|
|
Datto AV
- Complete the actions documented in the Getting Started
- Verify RMM agent installed and added in RMM
|
|
Datto EDR
- Complete the actions documented in the Getting Started
- Verify logins are created/available for all needing access to the tenant
|
|
Datto Ransomware Detection
- Complete the actions documented in the Getting Started
- Ensure at least one Datto RMM agent deployed
- Ensure ability to create monitoring policies
- Only use ransomware in Datto EDR if both are used Datto RMM
|
|
Datto SaaS Defense
- Complete the actions documented in the Getting Started
- Log into your Datto Partner Portal. Review walkthrough prompts for:
- Opting into SaaS Protection
- Review the license schedule | here
- Complete the Kaseya Store transaction
- Enroll organizations in SaaS Protection
- Manage and restore organization data
- Activate SaaS Defense for clients with SaaS Protection
|
|
Graphus
- Complete the actions documented in the Getting Started
- Verify logins are created/available for all needing access to the tenant
- Add at least one internal or customer organization and activate the corresponding Microsoft 365 or Google Workspace domain. (24-hours prior to your onboarding session)
|
|
Passly
|
|
RocketCyber
- Complete the actions documented in the Getting Started
- Verify logins are created/available for all needing access to the tenant
|
|
Vulscan
- Complete the actions documented in the Getting Started
-
Verify access to portal via RapidFire Tools Portal
|
|
vPenTest
- Complete the actions documented in the Getting Started
- Ensure you have received an invite to your vPentest account and can access the portal
- Review onboarding videos | here
- Configure branding | here
- Create user accounts for additional members in your team | here
- Permitting access for the Agent (Allow List)
- Deploying the agent, requirement to install Ubuntu | here
|
|
|
Backupify
- Complete the actions documented in the Getting Started
- Click "Opt-in" to begin the self-guided setup within Backupify
- Follow the on-screen instructions to add your first Backupify client
- Perform sample restores of backed up data to familiarize yourself with Backupify tools
- Note any steps or configurations you have questions about
- Refer to the online knowledge base for assistance by clicking the "?" Icon
|
|
Datto BCDR
|
|
Datto Cloud Continuity for Microsoft Azure
- Complete the actions documented in the Getting Started
- Log in to portal.dattobackup.com
- Ensure you have a supported server to install the Endpoint agent
|
|
Datto Endpoint Backup for PCs
- Complete the actions documented in the Getting Started
- Log in to portal.dattobackup.com
- Ensure you have a supported server to install the Endpoint agent
|
|
Datto Endpoint Backup with Disaster Recovery
|
|
Datto File Protection
|
|
Datto SaaS Protection
- Complete the actions documented in the Getting Started
- Upon logging in as an Administrator for the first time, a pop-up will appear on your screen to initiate the onboarding process.
- You can access the walkthroughs again by navigating through the menu and locating the onboarding task.
|
|
Datto Workplace
- Complete the actions documented in the Getting Started
- Log in to Workplace Manager – Ensure that you can log in to Workplace. You should have a welcome email with login instructions.
- Review your account settings – Configure the region and time zone settings for your account.
- Set your Team defaults - Set the default settings for any new Teams you create for customer data.
- Configure Workplace branding - Customize your branding so that your end users know who is managing Workplace for them.
- Set up your support information – Configure the contact details on the Workplace application so that users know where to reach out if they have issues.
- Configure notification recipients - Ensure that your team will be alerted to issues that arise once Workplace is deployed.
- Create accounts for your admins - Give access to internal users that will be helping create and manage customer teams.Review the Configuration settings at help.workplace.datto.com
|
|
Spanning
- Complete the actions documented in the Getting Started
- Upon logging in as an Administrator for the first time, a pop-up will appear on your screen to initiate the onboarding process.
|
|
Unitrends
- Complete the actions documented in the Getting Started
- Deploy a virtual appliance into your Hypervisor
Configure VM via Hypervisor with valid IP and can browse via web browser to IP
|
|
|
Help Desk
- Review the provided customer onboarding success resources. The Onboard Team will provide checklists, templates and documentation that will help prepare your team for the discussion and exercises undergone during the onboarding process.
- Complete the customer onboarding welcome questionnaire. This will provide the onboarding team with some introductory information about your business and the goals you wish to achieve by partnering with the Kaseya Help Desk.
- Update clients’ point-of-contact information in your databases and ensure all syncs of this data are up to date. Centralize client specific documentation and
- Standard Operating Procedures (SOPs) into an easily accessible location for review and discussion with the onboarding team.
- Invite a member of your service delivery team to the sessions. They can provide insight into the daily operation and what can make collaboration between our teams most productive.
|
|
NOC
- Ensure that the RMM solution is installed and operational on every supported device.
- List any specific requirements, configurations, or limitations related to applications or software.
- If you wish to integrate NOC services with your Autotask PSA instance: Kaseya will forward un-resolved alerts to your PSA instance.
- You’ll need to set up workflows in PSA to map these notifications according to your requirements.
- Document and share any unique considerations, specific challenges, or critical knowledge that only your team possesses about your organization.
Gather and share any documented procedures or solutions for resolving common issues or troubleshooting problems encountered at the site.
|
|
|
TruMethods
- Complete the actions documented in the Getting Started
- Self-guided onboarding is available when the first administrator log in. The onboarding will walk the first administrator through each part of the application that needs to be configured for your company to start using the product right away.
|
|
|
What to expect with?
1. Advance 360
- Structured migration program from a compete product stack to a Kaseya landscape
- End-to-end health check, optimize and configure your Kaseya assets
2. Review 360
- Comprehensive audit and analysis, provide the recommendations, and implement the key actions
3. Manage 360
- Engage in monthly consulting sessions with your dedicated expert mentor
- Assess progress, evaluate results, and refine your action plan for the next quarter
4. Expert Assist & Custom Request
- Expert led Consulting session for ad hoc request or training
Checklist Ahead of Engagement
- Designate a Project Champion who will lead the engagement (technical decision maker)
- Provide supplemental details ahead of your intro/discovery engagement that will facilitate your engagement
|