I have a group who has a Lotus Notes database they'd like to migrate
to SharePoint. Good news is that the "documents" in Notes contain
no attachments and are essentially just forms with metadata.
(25,000 of them!! ugh.) Bad news is that they've made extensive use
of "child" documents which attach underneath the main forms and use
one of 3 different child forms. Also, one main document may have
any number of children of various types.

So, I'm wracking my brain for options. Here's what I have so far.
I'd appreciate any further ideas you may have.

1) Create 4 different lists and rely on web part pages and
connections to tie the "child" forms with the main form. Seems
extremely clunky compared to what they have now in Notes.

2) Create a "button" on the viewform.aspx of the main form that
creates the appropriate child list item (in a separate list) and
inserts a hyperlink to it in the main form item. (I'd have several
generic reference fields there and can set the view styles with
FrontPage to get a pseudo-heirarchical view.) This would involve
coding and would almost force users to go to the main docs first,
although I suppose we could still use web part pages and connections
as a backup.

3) Infopath?? I don't know much about it, but can I create a forms
library with a dummy template that just actually allows the user to
select which real type of form to complete. Then, I'd just rely on
grouping and metadata to establish the heirarchical views?