Content migration, import, and export

I am taking a look at using feeds to push content from one site to another.
Reading the pages for Feeds Atom, Views Atom, and Push_Hub it looks like push hub will notify if someting changes on the host server.

I was wondering how I make the feed only available to another machine of my choosing and not allow it to be world readable?

Services allows for key authentication.

Does feeds module have a similar option?

Doing a migration to Drupal 7 from another CMS and trying to import content and users. Can import basic fields just fine, but custom fields aren't working. Tried two ways: direct to MySql database and using drupal cmds.

(1) using sql insert

"INSERT INTO users (name, mail, uid, pass, ...) VALUES (blah, blah, blah, blah, ...), (...); " -- works great. able to login with old user id and password (pass is pre-hashed by Drupal routine).

Have a website that is using the Date and Calendar modules. Need to allow user to upload these events into their personal calendars (or a Google calendar). Can export initial events via the Views ICAL display type but subsequent uploads create duplicate calendar entries. Anyone have a method to synch calendars?

I have a project that involves a nightly importing of data from an external source, and from what I've seen Migrate module would be a more robust solution that me writing code. I've been looking at it but haven't been able to figure out how to implement it to fit my needs, so I'm hoping someone here might be able to shed some light on it for me.

Hi

First, I'm sorry if this is the wrong place to post. It was the best I could find ;)

Now, I need to build an "Art on Demand" website. This is a system that sells reprints of art. The site can be seen at http://advancedimaging.artondemand.eu

Now, there's nothing I can do about this system, but my client wants additional pages with information, so at least a top menu with more or less static pages. He might also want a preview of shopping basket on one of these pages.

Hello brothers!
I want to discuss data synchronization between drupal sites with you. I mean more specific problem - data synchronization between fields in few drupal installations. In my case I have something strong intranet or database and I want to give someone users ability to send data into another drupal site which has same cck architecture. And I don't want to send whole node, i want to send datа from some fields. No, I don't want to send them. I want to synchronize them. For example with checkboxes near by cck fields and sync button.

I'm posting this because I just spent way too long trying to figure out why all CCK fields were suddenly missing (absent, not showing up) as destination fields on the mapping page of a content set for the Migrate module. The answer is in plain site on the Migrate project page and discernible in the CHANGELOG.txt.

Migrate Extras. Optional, but for releases after Beta 4 you need this module to be able to migrate CCK fields, as well as other contrib modules previously supported natively in Migrate.

Last year, jpetso created the Field Tool project to provide a low-level API for (among other things) getting data in and out of fields in a simple and consistent way (also Transformations for further up the stack, but first things first...). Unfortunately since then he's had had a lot less spare time, so this is a call for help on this obvious Good Idea. Ever been frustrated by the many different ways fields can store values of varying complexity, and having to code your own data import/export handlers for every module you might be using that provides field types? You can help solve this problem!