Below is a cut and paste from SpringShare's 9/5 update. Note: they divide QP customers into 3 groups: software only, non-contributing cooperative member, and contributing cooperative member. Officially, the VCCS is a contributing cooperative member since we are responsible for answering questions from other groups; we just don't require the volunteers covering during the regular work day to do so.
The Plan for Cooperative Members: Contributing & Non-Contributing
Whether you're a contributing or non-contributing member of the Cooperative, the below plan applies to you.
We will migrate everyone at the same time - Because we can't (and you surely don't want to) maintain two Cooperatives in both QuestionPoint and LibAnswers, at the same time, our plan is to migrate everyone from QuestionPoint to LibAnswers at the same time.
In consultation with members, we'll pick a date when the entire Cooperative will cease to use QuestionPoint and solely use LibAnswers. We will provide ample announcements, emails, and information prior to that date... we promise you, you won't be blind-sided or scrambling. In fact, you might get sick of all the emails you'll get from Springys Talia and Mazen.
We are still a ways away from that date, so in the meantime here are some things that are currently occurring and our plan for the Cooperative migration.
We'll Create a Dedicated Migration Plan for each local Cooperative/BME: We'll be coming up with dedicated migration plans for each BME and how their installation(s) of LibAnswers will work. In some cases, we've already started meeting and planning out dedicated migration plans for each local Coop/BME. If we haven't chatted you yet, don't worry! We will!
**Coming Soon** Phase One: Release Cooperative Functionality to LibAnswers:
We'll be rolling out some of the Cooperative features to LibAnswers by the end of this month. This doesn't mean that the Cooperative is now suddenly in LibAnswers. Rather, we're releasing the user interface and cross-regional technology to enable the Cooperative to work inside LibAnswers.
Phase Two: Working With a Small Group of Beta Testers:
After the release, we'll create a small group of beta testers... let's call them the Test-Cooperative to actually test the functionality and provide feedback.
Phase Three: Training Sessions
We'll have dedicated training sessions for users. Whether that's attending a general 'How to use LibChat' session or individual webinars on how your LibAnswers system(s) will be setup.
Phase Four: Getting Your LibAnswers System(s) Installed and Setup Per Your Migration Plan:
Once you and any relevant staffers have attended training, the next stage is getting your LibAnswers system(s). This system will become your live LibAnswers system(s). We may, during the time-period, pre-migrate over **some** content like scripts, policy pages, etc. We don't have specifics on this area yet as the QuestionPoint-to-LibAnswers migration of content like policy pages is not one-to-one. And you might want to 'start from scratch' and make use of some new-to-you LibAnswers features. We'll discuss this more in-depth during our conversations with your BMEs.
Post-training, explore things that were covered during training like:
Setting your system including customizations and creating accounts for fellow staffers;
If applicable, building FAQs (internal and/or public);
If applicable, customizing your email form, email form notifications, etc.;
Setting-up your chat including chat departments, widgets, etc.
This is a great time for staff to explore the system, testing it out by entering fake chats or email submissions and trialing the 'answering' process.
If you do some extensive playing and your system gets full of 'test content' and you want to zero it out before going live, we can totally do that for you. Just contact us and we'll delete and 'test' content and reset your stats to zero.
Phase Five: Migration & Going Live:
Per the aforementioned TBD go-live date, the last part of the process will involve going live.
At this stage, we'll migrate over your QuestionPoint stats and transcripts so the most 'recent information' is live in your LibAnswers system.
You'll switch out any links or widgets on your websites to point from QuestionPoint to LibAnswers.
I.e. you'll replace your link to your QuestionPoint Email Form to the LibAnswers Email Form, and/or replace any QuestionPoint chat widgets;
You'll cease logging into QuestionPoint and log-in to your LibAnswers system.
And that wraps up our general overview plan for moving you from QuestionPoint to LibAnswers! Please note that these plans can and might be subject to change. So please do keep an eye on this blog and other communications from us to stay up-to-date.
Phew, this turned into a rather longer-than-intended blog post! So if you're still with us - here's some answers to some FAQs.
Question: Do we have a deadline for migrating from QuestionPoint?
Answer: There is no current deadline for migrating from QuestionPoint to LibAnswers. However, once we finalize all software functionality we will revisit this - but we will communicate all deadlines with at least a 6 month buffer window. I.e. if we announce a deadline of May 31, 2020 - we will communicate this deadline at least 6 months prior, by December 2019.
Question: We don't use Chat in QuestionPoint, do we have to use Chat in LibAnswers?
Answer: If you're a software only user and not part of the Cooperative then the answer is No. You don't have to use any tools you don't want to! Alas, if you are part of the Cooperative - there's no getting around answering some chats.
Bottom-line, you'll only use the same modules/tools you are currently using in QuestionPoint. If you don't do chat in QuestionPoint, you won't do chat in LibAnswers. However, LibAnswers has some cool functionality like social media integration, Facebook messenger live, Pinterest posting, etc. And if you are doing those things in other tools, you might want to explore how you can streamline those processes inside of LibAnswers. Contact us if you have any questions about these additional features. Email us: qp@springshare.com.
Note: depending on your subscription, these additional features may cost extra.
