I'd say to attempt this on almost any kind of home broadband connection is a non-starter.
Even with a 10Mbit upload, we're looking at 4GB per hour at best so a transfer would take minimum of 2 days solid (longer if the connections are used for other things meantime). The method would need to allow restarting part way through (some but not all FTP implementations support this).
If this was to become a regular thing they could try something based on rsync at both ends, possibly involving setting up a VPN between the two locations and letting the transfers run in the background.
Services like Dropbox would be another possibility if both ends aren't online at the same time, or one party could buy some hosted server / webspace and send a link / credentials to download when ready.
As per the previous reply I think the practical method is for the files top be copied onto an NTFS formatted drive and posted / couriered. For any format other than NTFS or FATs Windows normally needs needs a filesystem driver.
If either end doesn't have free drive bays in their computer then they can buy a suitable caddy (you can get them with eSATA or USB3 as well as USB2 depending on what the computer supports).
Hard drives need to be well padded for transport - an SSD would be somewhat more rugged but would be rather more expensive for 200GB of usable storage.
But ultimately if someone has a use case (or business case) that requires shifting this much data they have to budget for it either way in terms of high speed internet bandwidth or transport costs as well as local storage (and backup).
prompt $P - Invalid drive specification - Abort, Retry, Fail? $G
prlzx on n e w n e t: ADSL2+ / 21CN at 2.5Mbps / 800k