I'm not sure what you have or haven't done so far. I came up with this quick checklist for my company's domain migration and all (or should I say most) went well. I don't remember where I got the info, but I can try to find it if you need it. It should send you in the right direction though.
1.ADMT requires an explicit trust from the source domain (trusting) to the target domain (trusted).
2.ADMT requires that the target domain be running in Windows 2000 native mode, since only this domain type supports the sIDHistory attribute. For interforest migrations, the tool must be run on a Windows 2000 domain controller in the target domain (for intraforest migrations, the tool can be run on either the target or source domain controller).
3.The user running the program must be a member of the Domain Admins group in both the source and target domains. This should be done by adding the Domain Admins group from the target Windows 2000 native mode domain to the source domain?s Administrators local group.
4.Auditing of success and failure of account management operations must be enabled in both the source and target domains.
5.A registry DWORD value must be created on the PDC in the source domain, setting the value name to TcpipClientSupport and the value data to 1. The registry path is HKLM\System\CurrentControlSet\Lsa. This setting enables all communications between source and target domains to use remote procedure calls (RPCs).
6.A new local group, $$$, must be created in the source domain for auditing purposes.
7.Keep your fingers crossed and hope this works!!!
Let me know if you need anything else.
Norm