If you're working with Amazon AWS and trying to move stuff from some kind of big EC2 instance down to a t2.micro one (since the t1.micro is no longer offered), here are a few helpful hints to get you started.
First of all, be sure to start up the new micro instance in the same exact region as the old instance - not just us-east, but us-east-1 or whatever.
Then, because the old instance is a "classic" instance and the new one is only available on the blankety-blank "vpc", they will only talk to each other v-e-r-y s-l-o-w-l-y over the public internet; so if you want to use the private ip addresses to get that data over (Yes! You do! Otherwise you'll get charged for the data transfer and it will take days!) then you need to turn on the blankety-blank ClassicLink for your vpc, then enable ClassicLink for that old instance, linking it to that vpc, then ensure that it's in the same vpc security groups as your new instance, and that those security groups allow the right connections. If you try to ssh between the servers and nothing happens, don't worry; that just means you did it wrong, so try again.
Finally, you won't be able to move your blankety-blank-blanking "elastic" IP address from the "classic" to "vpc" services unless you use "the [blankety-blank] Amazon EC2 Query API, an AWS SDK, or the [blanking] AWS CLI" - so no migrating that IP address from the web console! - and in order to use those command line tools you'll need some other blankety-blank security thing that I didn't have the account level permissions to grant myself because it was a team account.
You can read all about this in Amazon's "help" section; a good place to start would be this page, which has very helpful links to the 1,000,000,000 other help pages that you'll need to read anytime you want to perform the simplest blankety-blanking-blank-blank task with Amazon AWS.
Alternatively, you can set up a $5/month server in about 5 minutes on DigitalOcean--but hey, if you really care about that IP address, it's your life. Go for it.