I love .NET, so I would try hard to make the SQL Server replication solution work, but failing that ...
Here are two NoSQL solutions I would consider for replication:
CouchDB
They have pretty good replication and it will resume where it left off when connectivity is lost. There is a learning curve if you're coming from an RDBMS background, but it can work.
MongoDB
You can use a replica set with Mongo that syncs with a central (primary) node. When secondary nodes in the replica set go offline, you can bring them back and pick up where you left off.
The problem is that if the primary node gets a lot of writes, it might not be able to sync up again with a secondary node that has been down for a long period of time. It basically remembers all writes on the main/central node and eventually older writes get flushed out.
General Advice
Both Mongo and Couch are document databases. If you want to move to NoSQL you'll need to switch all your code to denormalized structures instead of normalized structures, which is what you're probably used to in the relational world.
It's a big shift and I know I've had trouble nailing models I feel good with in the document database world.
As far as moving data around in general, I've found Mule (http://www.mulesoft.org/) to be really good at connecting very different types of systems/databases.