Home » Help Center » Create a New Project FAQ

Create a New Project FAQ

 

1) How does the pricing work?

 

When creating a new project, there are two pricing options:

 

a) $50 – this is the minimum mandatory cost necessary to create a new project. If you choose this option then you will be able to copy your current project or build one from scratch. 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.

 

b) $50 + $150 – this includes the mandatory fee of $50 as well as a $150 fee for a project manager to be assigned to your build. The project manager 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.

 

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.

 

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

 

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 occur:

 

a) the applicants in the “source” system (the project you copied the information from) must remain as active applicants

 

b) You need to make sure User data is turned on when copying the project.

 

6) If I have outstanding payment plans going in the old system, how will the system copy effect that?

 

It won’t! 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? as long i maintain the same iframe code in website?

 

Yes – you will literally have two systems, each with its associated iframe code.

 

8) And how does the having a copy of the system affect our billing moving forward? Is the $50 a flat rate? Or is that added to a monthly?

 

The $50 charge is a one time charge, and there are no additional fees specifically associated with having numerous projects (ie, if you’re the admin of two projects, you’re not charged two admin fee’s). That said, your full time admin costs are determined by the total number of applicants you have across all of your systems. So if in your new project you have enough applicants register to bump you up to the next billing tier (brackets are 0 – 200, 200 – 2,000, 2,000 – 5,000, 5,000 – 15,000, etc…), then you could see an increase in your monthly bill.

 

9) I’m looking to create a new project based on the recent update you rolled out. I can do it on my own, and I see the fee is $50. My only question is will I then be paying an additional $50 Admin fee once I create the new project, or can I build it and not be charged the Admin fee until it’s ready to roll out.

 

Nope – no additional admin fees are assessed for having an additional project, and since your copy will have no new applicants until you release, there is no financial reason to hold off!

 

10) However, I then learned from RegPack Payments that I was being charged for any Users on the “old” project as well as the “new” project. I do not want to be double-charged for people who are listed on both projects. I understood that when returning customers login, their data would load into the new project (seems to be working fine)…… but a bit confused as to why I am charged for these Users on both projects.

 

Porting over applicants information from one project to another used to be a time consuming and costly process. With this in mind, our development team did a lot of extra work to ensure that user data could be ported over automatically from one project to its copy.

 

At the technical level, the system treats applicants who are archived differently than active applicants, which means that in order for the porting connection to function, the applicant in the original project must be active in order for the connection to remain open. Archiving an applicant in the original system will close this connection, and applicant’s information will not port over.

 

As to the notion of “double-charging”, data porting between projects used to be a very costly feature, and what we have done here is actually to substantially lower the price. If you would not like to port user data (which used to be quite normal), then you would be free to archive all of the applicant’s in the original project and avoid any potentially higher admin fee’s. The three main points we’d make about this are:

 

(a) It is technically necessary to allow the porting feature to work

 

(b) It can be easily avoided by archiving your applicants

 

(c) In terms of monthly fees, it only affects clients on the threshold of a higher billing tier. If you’re firmly within one billing tier, or it’s worth it to you to have your applicant’s data ported over, then you should take advantage of it. If it’s not worth it to you, or you just don’t want their data ported over, then feel free to archive all previous applicants.

 

11) Do I have to manually archive them in the original project if I don’t want their data to be ported?

 

Yes, you would need to select all applicants in your original project and archive them. If you do that, when your users log into the news system, they will fill out the forms from scratch.

 

12) 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 just need to go back to the original project to look up that information.

 

13) Most of the information had transferred over, products, email, 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 login for the new registration. This is actually a great thing in terms of management, since it means that the only users which will ever appear in your new system are those who are actually registering in that new project (and you’ll avoid the problem of trying to distinguish who is in this year, and who is in last year).

 

14) Oh OK, gotcha! Well, what about the recurring user? The people who registered last year? They won’t have to fill out all the forms again right? But, then how does the system recognize that they are registering for a new year if they don’t have to fill out any of the forms?? Because they aren’t creating a new account so how does that work then?

 

They way it works is that 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 you host.

 

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, and things like that) will automatically port over, and the user (who previously did not appear on the new project’s user management page) 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.