phranque - 4:42 am on May 12, 2012 (gmt 0)
i would treat this as similar to a hostname change.
make sure you have the proper 301 redirects in place to serve content only for the canonical scheme, hostname and an unspecified (default) port number for the specified protocol.
there should be no chained redirects - do all the scheme/hostname/port/path/parameter canonicalization in one step.
all your internal links should specify the proper secure scheme and hostname (assuming they aren't relative urls).
whenever possible try to get any inbound links changed to avoid the redirect.
also make sure that your ssl certificate is valid for your hostname so that you don't get a high bounce rate from any ssl-related browser warning popup messages.
what is your reason for each of the changes?