28 Nov Migrating from a portal to a community #1 — Develop a plan
by Chris Gardner
The Salesforce Cloud can be a great benefit, and if you have an existing Partner or Customer Portal built into Salesforce, it’s vital to ensure you’re taking full advantage. Modern Lightning communities make helpful features and capabilities available to your users. Access to Chatter, community member permission sets, and SSO, along with increased partner record and feature access, are all valuable tools available to Salesforce Cloud users.
It’s critical to have a plan in place to migrate your portal to the newer framework. In this first installment of a three-part series, we’re going to look at developing an effective migration plan to help you move to your new community. And any solid plan begins with some critical decisions.
1. What is the transition timeline and plan?
2. Who are our users?
3. What functionality will we retain from the existing portal?
4. What new functionality are we adding?
Let’s go over each decision.
Typically, it’s best to leave the existing portal in place as you open your new community and relocate power users. This process is also an excellent opportunity to solicit valuable feedback from your users before completing the migration.
When you’re ready to implement your plan, managing URL’s can be a challenge. However, we have found….
Want to keep reading? Download the full ebook here!
Chris is a Salesforce Consultant and Developer with Simplus. He is an experienced leader with a focus on implementation, best practice consulting, and marketing. Chris has over ten years of experience in consulting for small to large businesses. He fosters healthy client relationships from initial engagement through handoff. Chris is skilled in turning client requirements into actionable system designs and following best practices to implement and optimize Salesforce solutions.