Will you be able to upgrade to Ver. 3 ?

[pipedragon]

Will you be able to upgrade your site to version 3 without causing any problems to your existing customers? :)

[Mike]

I can almost gaurantee that the upgrading process will be smooth. That's the purpose of an upgrade. It suppose to strengthen the program without degrading its database.

[Peter]

There will be import / migration tools available in terms of the users, and their accountdata (online account information), feedback and rating information.

The Subscription system was also re-written. It now supports the ability to allow the admin to define access-rights, permissions per resources per subscription plans (user groups), as well as the ability to allow any length or duration for any plan that is available.

Templates are 100% different than the existing framework, but I'm 100% positive our existing customers will absolutely love the new design-flow, and the ability to easily change every aspect of the HTML only templates within a minimal amount of time.

As per your original question, customers are not forced to upgrade to version 3.0.0. To be honest, we feel the new version should be installed as a fresh copy perhaps on a subdomain aside from the existing version installed (we are in the process of modifying our license agreement that allows multiple subdomains per licensed domain). ILance has been working with many customers, younger and older and we try to meet a realistic budget with all of our customers. Many of our customers will receive ILance v3.0.0 as a FREE upgrade, and others will be required to purchase this 'Upgrade' for $199.

So yes, there will be some migration tools from v2.1.7 to v3.0.0, and I'm not sure on the entire process yet. We'll post an annoucement when we're ready to let everyone know.

ulocha: --

There will be a script to let you upgrade v2.1.7 to v3.0.0 db tables but it's recommended to install fresh version of v3.0.0 first then use a script import v2 users to v3 db user table. You'll still be able to launch v3 on any of your subdomains to do this process, then if you want to keep running v2 on your main domain and v3 on your subdomain, this is no problem.

Either way it's looked at, yes there will be upgrade scripts and yes you can launch ILance on multiple domains under the root domain (using same db), and there will be no problems to existing customers since the current version of ILance already does what they require and may not want to jump to version 3 until they need to.

If they want to upgrade to version 3 when it's available, the customer is freely available to do so, but there will be some knowledge of PHP required since this upgrade process will be in the form of PHP scripts that they can execute on their servers to do the upgrades (with the same server running the original v2 database), and no this will not be supported by ILance within the standard 12 months of support available to each customer via trouble ticket.

What would most likely happen is our novice customer would request our advanced support services that would assign them a technical ILance developer to handle this entire process from start to finish and would be invoiced via ILance member area.

[pipedragon]

You people seem to know what you are doing and your product looks solid. Thank you so much for answering all of my questions quickly and this user forum is also very helpfull. I think I have found a gold mine here. I have looked at a few other freelance software offerings but yours is leaps and bounds ahead of them. I am pretty much sold on your software, now I just need to figure out my bussiness plan and make sure it is solid. I am currently stuck on figuring out how to get enough providers ready before I start advertising. Any tips there would help a lot. The last thing I want to do is launch the site and fail to deliver what is offered. I will be in touch with sales shortly . I need to talk to my business partners and work out some logistics but at least the web front end is in the bag! :)

[john]

Can anyone tell me the estimated date for v.3 the only reason this is tough is because I would like to roll this app out at the begining of the year but I do not want to change the gui and the management of the app right after we deploy, this would feel strange to the users and new members. Is there anyway to get a rough date. Also if I spend significant amount of money on customization of things it would be terrible to see these replaced or incompatitable shortly after completion.

Just curious
John