Develop back end for a website, Front end is already designed

The website front end is designed, we need the following back end functions developed in ASP or ASP.NET. Front-End ------------------------------------------------ HTML5 conversion of visual design Hunter/Landowner Registration/Subscription Google Analytics, AdSense and Adwords AddThis social media share/follow Standard SEO Password Recovery Property searching Front/Back-End ------------------------------------------------ Property listings with location map (self-hosted maps - [login to view URL]) Ability to save 'favorite' locations Ability to use geolocation to find properties nearby Ability to setup email notifications for new properties based on search criteria Ability to update personal info Landowner Back-End ----------------------------------------------- Ability to update property details Ability to update personal info Ability to renew property listing Admin Back-End ------------------------------------------------ Ability to make leases unavailable after a certain time Auto generated email to landowner after X number of weeks with renewal link; customizable timeframe Ability to email members Ability to export user data Ability to change pricing and time span General ------------------------------------------------ Fix SSL Integrated user subsciptions via Stripe Adjust DNS to accept www prefix if contained in URL Database schemas The first order of business would be to export the current SQL db into MySQL. One thing to note is that we are going to focus on only two sets of users with this relaunch - hunters and landowners. We will no longer need the guide data that is in the db. Known database issues encountered that need to be addressed that caused this to derail. Timestamps and date issues in the current database. They didn't store the dates correctly and then had to use code to parse the dates in a usable way. I'd have to do it wrong too in order for the old dates to work. Then new dates going forward would also be wrong. They're saved as text and not timestamps. By parsing each date with code I assume, which requires a lot more code than if the dates are stored correctly as timestamps. Timestamps are computer readable which means the dates can be used easily for all sorts of common tasks without a bunch a manipulation and correction first. All the 'tools' I have to build with require timestamps because that's the correct way of storing dates. There's about 32,500 dates that must be fixed.