Just before you do that!! ...
... I expect there are blogs detailing any Gothcas that you may want to consider, I recommend you Google for some Good Info, but the one I would raise is Backups.
Unless things have changed (we only use the heavy Iron versions of SQL Server, not Express) there is no SQL Agent in SQL Express. SQL Agent contains a scheduler which, basically, just runs one/many SQL statement "steps" on a timed schedule, and has the ability to EMail etc. on Failure (or Success), keeps a log of the output from the tasks, and so on. The Log History makes it pretty easy to debug things that go wrong etc. - i.e. right-tool-for-right-job. There is also a Maintenance Wizard and whilst the Pros here (myself included) thrown scorn on it at least you can say "Construct a backup for all DBs every night" and "Rebuild all indexes at the weekend" and so on without having to write a line of code.
Building a backup schedule using Windows Task Scheduler, by comparison, would require both some Grunt and some Knowledge.
There are cracking 3rd party backup solutions - of those I favour Minion Backup for "small shops" because you can just plug it in, and it will "just work" out of the box - fiddle with options only when you decide you want to, your data will be safe in the meantime. But I have no idea how easily that can be scheduled WITHOUT using SQL Agent. There may also be other tasks? that you need to schedule that you will miss having SQL Agent available
Either way, I suggest:
Set the Recovery Model of ALL your databases to FULL. IF you can reconstitute a database, entirely, from external data then setting it to SIMPLE is OK.
For ANY database that is in FULL Recovery Model backup the log every 10 minutes, or more frequently. Absolutely no sense having the ability to restore to point-in-time and then only taking a LOG backup once a day! Also, in FULL mode you need to backup the log often, otherwise it will grow - possibly to rediculously large size.
Then take a FULL backup overnight.
Backup to local disk (buy more space if you need it). Backing up to a remote location complicates things and risks backups not happening (and you not realising they haven't).
Keep a weeks worth of backups online (moving them to somewhere else, with more space, after a day or so is fine). That way you can restore / investigate without having to find a backup tape, wait for the tape machine to be free, wait for the tape to restore, then discover that wasn't the backup that you needed after all!
(We keep Sunday's Backups online for 4 weeks, daily backups for a week, we actually only do DIFF backups on weekedays, FULL on Sundays, to save space).
Oh ... use COMPRESSION on all your backups. Absolutely no reason not to, and its a single "switch" in the settings, so no need to configure backups to be compressed etc., just throw the "all backups compressed switch".
We haven't written a Client APP in years. Everything is web pages now, the whole deployment thing is a joy by comparison to all the hassle we used to have of DLL-Hell et al ...