First of all I'm not sure that archiving is the best solution. The feasibility depends on why you're doing this. If it's because of performance reasons, I would strongly suggest searching other alternatives and optimizing the database and it's usage.
What comes to archiving, you have multiple choices. You can:
- copy the data elsewhere using replication
- detach the database, make a copy elsewhere and reattach, the detached database can be used as a separate database.
- use SSIS to create data copy jobs etc
Of course you could also write a VB program to do at least part of the job, but I'd use SQL Server capability as much as possible.