Now that Gmail has IMAP, email migration via IMAP will give you better results that POP3 did.
Same thing, you'll have to first enable IMAP in Gmail for the old account, and then go to Advanced tools > Set up mail (IMAP) migration in the control panel to kick off the migration. http://www.google.com/support/a/bin/answer.py?answer=61369 Also, to avoid missing emails received immediately after migration, set up the forwarding (or routing) rule before the migration. Ask the Calendar API group to see if there is anything admins recommend for migrating calendars: http://groups.google.com/group/google-calendar-help-dataapi -alex On Jan 3, 6:25 am, "Sam Johnston" <[EMAIL PROTECTED]> wrote: > Try enabling POP3 in the old account and pulling mail across via the Gmail > interface in the new account. Once you've done the initial transfer you can > remove this and set up forwarding from the old account to the new account, > optionally with filters to tag and/or archive as you can with the POP3 > client. > > For calendars try sharing from the old account to the new account, or > [ab]use a client side sync tool. > > Sam > > On Jan 3, 2008 3:13 PM, Jon.Mitchiner <[EMAIL PROTECTED]> wrote: > > > > > We are interested in this feature. While this is off the point from > > Google APIs, what is the best way to migrate e-mails (and calendar > > data) to a new name until the feature is added back into the > > Provisioning API? > > > Thanks! > > Jon > > > On Nov 17 2007, 8:55 pm, "Alex (Google)" <[EMAIL PROTECTED]> wrote: > > > Renaming usernames was removed from the Provisioning API, but because > > > of the high interest in this feature we will look into adding it back > > > in. No estimates on when though. > > > > The current workarounds are: > > > > - Create an email alias/nickname. > > > -or- > > > - Create a new user, migrate email, create a forwarding rule (either > > > in Gmail, or through email routing in control panel). > > > > We haven't gotten many requests for renaming domains. Domain aliases > > > and Gmail accounts allow you to receive and send mail from a different > > > domain. > > > > -alex > > > > On Nov 14, 2:57 pm, "Tim P. Gaynor" <[EMAIL PROTECTED]> wrote: > > > > > I too would be very interested in a real, not a patch type solution. I > > > > actually made a spelling error, forgot to ad an s (pluralize) a word > > in my > > > > domain. > > > > T > > > > > -----Original Message----- > > > > From: [email protected] > > > > > [mailto:[EMAIL PROTECTED] On Behalf Of Sam Johnston > > > > Sent: Wednesday, November 14, 2007 3:55 PM > > > > To: [email protected] > > > > Subject: [google-apps-apis] Re: provision APIrenamefeature > > > > > On 11/14/07, xnih13 <[EMAIL PROTECTED]> wrote: > > > > > > I hope your wrong, but based on a few posts digging around I fear > > you > > > > > may be right. > > > > > Actually one of my SE's just changed their name so I will check with > > > > them how they handled it with Apps. I'm almost certain it would have > > > > been a new account altogether but I may be pleasantly surprised. > > > > > Sam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
