1) How does the pricing work?
When creating a new project, there are 2 options.
a) Create a new project or copy over an existing project in your organization. Copying projects includes the porting over of any data (system or otherwise) for no additional charge. With either a copy or an additional project, however, you will not be assigned a project manager at this price tier, and you will be responsible for making any edits or changes to your copy, as well as building out your own new project. Support for this will only be available through our email support service. All new or copied projects are FREE of charge.
b) $350: This is an optional service that will assign a Project Manager for your newly created project. A Project Manager to be assigned to your build if you respond “Yes” and they will be available to assist you with your project set up, and generally serve as an adviser for any questions you might have about your new application, similar to the first time you set up your application. They can help review form flow, provide recommendations, and ensure triggers and products are setup to work as you intend.
2) What happens to the original version of our system?
It’s stays put! You’ll be able to access your old system by clicking the drop down next to your project name at the top right of the page.
3) Will I still have access and for how long?
Yes! You will still have access to your old system, and you’ll be able to switch back and forth as desired by clicking on the project name in the bottom left corner of the screen.
You can simply set the old project to “closed” for registration to prevent any additional signups. You have the option as well to archive the old project, however archiving it will prevent data from porting over to it’s new copy.
4) Will I need new iFrame codes that link to the new the system copy?
Yes, you will need to switch out your iFrame code on your website. See this article for more one accessing your iframe code.
Each system in Regpack has a unique iFrame code, so ensure you use the code on your website from the system you’d like to present.
5) How does the user data porting work?
When you copy your project, you have the option to copy over your applicants data. This means that when your applicants log in to the new system, their answers to their questions from the previous registration cycle will automatically appear in the new system.
In order for this porting to occur, two things need to happen:
a) the applicants in the “source” system (the project you copied the information from) must remain as active applicants. This means you cannot archive the old project or set a status to users that marks them as inactive in the old project.
b) You need to make sure User data is turned on when copying the project.
Go to settings –> project settings –> create new project –> copy project –> project settings –> user data porting turned on.
6) If I have outstanding payment plans going in the old system, how will the system copy affect that?
When you copy a project, your original project is not changed in any way. So if I expected incoming payments from an autobilling installment two days from now in my original project, and then I copied that project today, then my applicants would still be charged in the original project on schedule, and they would not be charged in the new project (since they haven’t logged in yet, ordered products, made payments, etc…).
7) Will users still be able to login and complete forms in the old system?
Yes – you will have two systems, each with its associated iFrame code. This means that when accessing a page with the code (or directly on the regpacks.com URL), they will login to that system. Ensure that you put the correct code on your website for each unique project.
8) How does the having a copy of the system affect our billing moving forward?
It doesn’t! All new projects are free of charge. You can have as many projects and as many users as you’d like across all projects in your account.
You will be charged only if you opt to have Project Manager assistance and this is per project, so you can request it only for certain projects if you wish.
9) Do I have to manually archive users in the original project if I don’t want their data to be ported?
No! Just turn off user data porting when copying the project (settings –> project settings –> create new project –> copy project –> copy settings) and data porting will NOT happen when you create the copy of the project.
10) I would like to be able to see a User’s history from past semesters. Is that still available to me when returning customers register on the new project?
If you want to see past semesters you can look up the information in the original project. Follow the steps to switch between projects here.
11) Most of the information transferred over: products, emails, forms, etc. The only information that didn’t transfer over is all of the student/parent info?? All of the those who registered last year, their info didn’t transfer over. Where are my users?!?!
Users will populate in the system as they log into the new project. This is great because the only users in your new system are those who are registering in that new project.
12) Do my returning users need to fill out their information again if the data is ported over? What about questions I want them to answer again this year?
When an applicant creates an account within any project of your organization, they will be able to use the same login email and password for any other projects within your organization.
If you port data between two projects (ie last years project, and this year’s copy, etc…), then when they log into the new project any of the fields which are fixed that don’t trigger anything (such as addresses) will automatically port over, and the user will appear in your new project. If they never log in to the new project, they won’t appear (so they don’t clutter your new project).
Archiving an applicant in the original project will *not* affect the applicant’s ability to log in to the copied project, but means that their answers to questions won’t port over.
There is a way to ensure users answer a question again in the new project if you’d like them to (did their age/grade change for this season?). To disconnect the user data porting from the original project for one question, delete the field and then add it back to the form in your new project.
Go to settings –> forms –> edit form fields –> click on the field –> delete. Click add field and add it back to the form. Users will be taken to their first incomplete form when they log in, so if the question is mandatory they will see it and need to complete it for their form to be marked complete.
Do you have other questions? Email support: email@example.com