Database format for Yahoo Groups migration to Google Groups via API

[entilza72]

Hi team,

Seeking advice from those who know this product well. I am migrating a Yahoo Group to Google Groups via Google's new-ish API, and PG Offline looks like it is well suited to the task of gathering the data before I pipe it to Google's API:
https://developers.google.com/admin-sdk/groups-migration/v1/guides/manage-email-migrations#managing_migrations

My main concern is: given recent Yahoo "sale" news, Yahoo Groups could possibly disappear "any day now"(TM). I need to start archiving now before I have my plan and the Google side ready, and its plausible I may only get one chance to "get it right". Thus, I want to choose the most flexible archive format I can, without having the luxury of testing.

The Google API wants rfc822 compliant emails (which could be an issue in itself) fed to it one at a time. Thus, I need to be able to traverse through the message list in my code, one email at a time.

My question is: what end-database format should I be choosing to aid flexibility? I'd think it would be Access, but as I will be using an Amazon Web Services image, I assume I will not have access to MS Access.  Are there other options available to me with the DB3 or PG4 formats?

Kind regards,
Ent.

[Wilson Logan]

The PGO database format is SQLite.

You will be able to install SQLite on AWS.

If you get stuck I can migrate your group to phpBB or Wordpress.


Cheers,

Wilson.

[entilza72]

Thanks Wilson - I appreciate the insight.

After I figure it out, I'll report back with my workflow for others

Ent.

[Wilson Logan]

PGO offers an Export to SQL Dump option so if you needed the data in, say, MYSQL, you could choose the SQL dump and load it to, well, any SQL type database.

Cheers,

Wilson.