Sharepoint Content Migration on MSDN
http://msdn.microsoft.com/en-us/library/bb249963.aspx

Sharepoint Content Migration on Microsoft blogs
http://blogs.msdn.com/jackiebo/archive/2007/02/23/sharepoint-content-migration-object-model-and-content-migration-packages.aspx
http://blogs.technet.com/stefan_gossner/archive/2007/08/30/deep-dive-into-the-sharepoint-content-deployment-and-migration-api-part-1.aspx

http://ethan-deng.com/SharePointContentMigration.aspx
http://blog.qumsieh.ca/2008/01/29/troubleshooting-content-migration-issues-in-sharepoint/
http://weblogs.asp.net/soever/archive/2008/01/07/sharepoint-content-management-package-cmp-explorer.aspx

[via Stefan]

Stefan Gossner is going nuts and pushing out some fantastic guidance & myth debunking on the topic of content deployment in SharePoint Server 2007. Check it out:

• Content Deployment – The Complete Guide - Part 1 – The Basics
• Content Deployment – The Complete Guide – Part 2 – The Basics continued
• Content Deployment – The Complete Guide – Part 3 - Configuration
• Content Deployment – The Complete Guide – Part 4 - Communication
• Content Deployment – The Complete Guide - Part 5 – Quick Deployment
• Content Deployment – The Complete Guide – Part 6 – Logging

I especially like the myth debunking Stefan does in the first post. Myths he addresses include:

• I need at least one full and one incremental deployment job per path as I have to run at least on full deployment at the beginning before I can run an incremental deployment.
• Full deployment is more than incremental deployment.
• It is best practice to run incremental deployments during the week and a full deployment during weekend to ensure that my content database is in sync.
• If incremental deployment fails I can do a full deployment to fix the problem.
• Quick deploy is an easy way to ensure that important content can go live easily out of sync with other content.

» Stefan - Content Deployment - The Complete Guide

Source: Fantastic blog series on SharePoint 2007 Content Deployment