Update help text to reflect current reality

@attheshow - Have you installed the table wizard module?

See http://drupal.org/project/tw

I suspect the text means to refer there since Table Wizard and Migrate were once together in a single module.

Right - the Table Wizard (formerly "Sources") has just been extracted out of the Migrate module, and I haven't updated the help text yet. Changing the title, we'll use this issue to track that task.

Thanks.

here is the text as it is now, should we move this out to help, advanced help, the README.txt?:

Above are tools for managing the migration of external data into Drupal. A typical
migration process would work as follows:

1. Under Sources, upload the external data. The raw data is imported
   without filtering into database tables on your server.
2. Analyze each imported table. Each column of data in the table is scanned,
   identifying uniqueness (implying a potential primary key),
   empty columns (automatically hidden by default), possible data types, and data ranges
   and sizes. Each column may be annotated to document its meaning, any special handling, etc.,
   and may be checked Ignore to omit from views and the migration process.
3. View the data for each imported table, to aid in the analysis and to mark Excluded
   any rows you don\'t want to import.
4. Under Destinations, define mappings from the imported data to
   Drupal objects (nodes, users, comments; plus any other types you define through hooks).
   First specify an imported table (with optional SQL selection criteria) and destination
   kind (node, user, comment) and type (story, page, etc.). Then map fields in the imported
   table to fields in the Drupal object.
5. Under Process, start the actual migration of data into Drupal and
   monitor its progress (if necessary, the processing will continue via cron). Migrated
   data may be cleared and re-imported any number of times as you refine the migration
   process.

Yes, I definitely want to make use of Advanced Help. The currently README is out-of-date, and this module really needs substantially more documentation than belongs in README.

I'm closing #392382: Document Migrate in favor of this issue... One note to carry over from that issue:

Include a Best Practices guide. Sample topics:

Using flag module to exclude specific source rows from a migration

I've delved further into the code to try to learn exactly how the module is working so I can make the modifications I need for a project. I really appreciate your responses to my various questions in the issue queue, I think this isn't the worst place if people are looking for answers to similar questions. I can help out by adding documentation. I've started with hooks at the moment so I have a good reference myself for the code I need to write.

The hooks documentation is here
http://drupal.org/node/415190

the new documentation interface is a little weird to me, will try to get a group of these pages under one "Migrate" section.

setup main documentation page here http://drupal.org/node/415260, and made the "migrate:hooks" page a child.

Thanks for getting that start on the documentation! Looks great so far (haven't reviewed it thoroughly yet...).

Just capturing some important info for anyone working on user migration - user_delete() performance suffers greatly from a couple of missing indices, you'll want to apply these patches:

#289504: user_delete() performance: index comment uid columns
#289510: user_delete() performance: index dblog uid column

I've committed the first round of support for advanced_help - still plenty to fill in.

I am working on help docs ...

I committed an improved set of docs. Much more can still be done.