{"id":68095,"date":"2023-07-17T13:22:44","date_gmt":"2023-07-17T17:22:44","guid":{"rendered":"https:\/\/jumpcloud.com\/?p=68095"},"modified":"2023-08-30T08:42:58","modified_gmt":"2023-08-30T12:42:58","slug":"defining-integration-for-msp-centralization","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/defining-integration-for-msp-centralization","title":{"rendered":"The MSP\u2019s Guide to IT Centralization: Defining Integration"},"content":{"rendered":"\n

This article is part two of a three-part blog series that expands upon our recently released MSP\u2019s Guide to IT Centralization eBook. <\/em>Get your free copy today<\/em><\/a>. <\/em><\/p>\n\n\n\n

In order to give your clients the most streamlined, efficient user experience possible, you need to be utilizing a top-of-the-line, all-in-one tech stack. IT centralization is the path to those efficiencies. This series explains the three steps to IT centralization. So far, we\u2019ve covered step 1: identification<\/a>, This week, we\u2019ll cover step 2: integration. <\/p>\n\n\n\n

Today\u2019s modern environment is more interconnected than ever, from our phones talking to our air conditioning and security systems at home to our business software communicating with external applications. This integration is made easy with cloud-native software and open APIs. But before you jump to connect your core IT platform to all the other applications in your company, you need to take a few things into consideration. <\/p>\n\n\n\n

In this article, we\u2019ll walk you through what integration is, and a few best practices to make sure you do yours right. <\/p>\n\n\n\n

What is Integration? <\/h2>\n\n\n\n

In step 1, identification, we walked you through how to understand your current tech stack\u2019s gaps, and how to compare it with modern solutions \u2013 and the solutions to one another. Now that you\u2019ve decided on a new core, it\u2019s time to bring it into your tech stack to fill in the gaps. <\/p>\n\n\n\n

In this step, you\u2019ll use your new core to address the most critical issues within<\/em> your tech stack, and then expand it to work with other applications, like your billing, sales, and people management systems. This integration is critical to the centralization process. While multipurpose platforms like 探花大神 allow you to conduct a good chunk of your business from a single pane of glass, it\u2019s not a one-stop shop. Since the end goal is a streamlined approach, your integration efforts should result in your core being able to \u201ctalk\u201d to all your other business applications.<\/p>\n\n\n\n

\n
\n \"Client\n <\/div>\n
\n

\n MSP Onboarding Best Practices <\/p>\n

\n How to Impress New Clients <\/p>\n <\/div>\n

\n Get the Guide<\/a>\n <\/div>\n<\/div>\n\n\n\n\n

Phase 1: Incorporate your Core to Fill in Gaps <\/h2>\n\n\n\n

We recommend integrating your new core in phases. In the first phase, you\u2019ll train your team on your new core and use it to fill the gaps in your tech stack. In the second phase, you\u2019ll incorporate your new core into other business platforms and systems. For Phase 1, follow these three simple steps.<\/p>\n\n\n\n

1: Train on the New Core and Incorporation<\/h3>\n\n\n\n

To ensure your MSP team is fully up-to-speed and confident working with the new core and solutions, first release it to a small test group. Have several team members pilot the new software and offer feedback and potential roadblocks or questions they encountered. This way, you can create training for your larger employee base that addresses those issues, and your team can be better prepared to serve your clients when they come with the same questions. <\/p>\n\n\n\n

    \n
  1. Unroll the new product(s) to a small group of MSP employees. <\/strong>Use this group to gauge the overall mood of the changes and to see in real-time how much (or little) the new software will affect the end-user experience. <\/li>\n<\/ol>\n\n\n\n
      \n
    1. Solicit feedback from the test group. <\/strong>Have your test group give their opinions on the usability of the new products, how much downtime clients should expect from the changes, and common questions that arose for them (both as admins and \u201cclients\u201d) during the transition. <\/li>\n<\/ol>\n\n\n\n
        \n
      1. Use the test group results to proactively train your support teams. <\/strong>Compile the test group feedback into training materials and FAQs for your admins and customer success teams. Make sure they are proactively prepared to first, use the new software themselves, and second, answer the most common questions that arose during incorporation. Coming to the transition prepared will increase clients\u2019 trust, and make for an easier experience for your employees, too. <\/li>\n<\/ol>\n\n\n\n

        2: Go \u201cLive\u201d with the New Core Internally <\/h3>\n\n\n\n

        Once you\u2019ve utilized your test group feedback to create internal training programs and materials, it\u2019s time to go live with your new core within your organization. Expect this transition to take a few weeks for everyone to get used to using the new platforms and to get up to speed on its functionality. <\/p>\n\n\n\n

        Note that (while it\u2019d be nice!) it\u2019s not realistic to assume all employees will accept the transition easily or quickly. As your team gets onboarded, expect some team members to need more training or assistance to get comfortable (especially if they worked with the legacy tech stack for a long time). <\/p>\n\n\n\n

        After the set adoption period (and before you roll your new software out to your clients), solicit another round of questions and troubleshooting from your broader team. This gives you one more chance to plan for FAQs and contingencies, and be proactive about any potential stumbling blocks in the adoption.<\/p>\n\n\n\n

        3: Release the Updates to Clients <\/h3>\n\n\n\n

        Depending on how you centralized your tech stack and what products you changed, your clients\u2019 user experience may or may not change with the new release. <\/p>\n\n\n\n