For getting data into beehive, there is the powerful beehive migration tool (BMT), that can batch import from sources like OCS, MS Exchange, Lotus Notes and IMAP.
For getting data out of beehive, the options are somewhat limited. E.g. we have no open protocol access to mail or calendar data stored in team workspaces (see my lasts posts).
There are some beectl commands that do a proprietary export of beehive content: this may help in some scenarios, like when you would like to export some selected artifacts for easier recoverability or transfer to a testing / demo platform.
These commands, export_workspace and export_email_data (there also is a "beectl export_icalendar") currently have somewhat limited functionality, though.
There are a couple of enhancement requests addressing this, at least the following:
ER 12598791: EXPORT_WORKSPACE TO EXPORT ALL WS DATA
ER 12589908: EXPORT_EMAIL_DATA SHOULD WORK FOR TWS
ER 12589881: EXPORT_WORKSPACE SHOULD CONTAIN EMAIL DATA
ER 12589989: EXPORT_EMAIL_DATA SHOULD BE ENHANCED TO USE (OPTIONAL) SHARED FOLDERS
ER 12589944: EXPORT_EMAIL_DATA SHOULD BE ENHANCED TO USE DEDICATED FOLDERS ONLY
ER 12589966: EXPORT_EMAIL_DATA SHOULD BE ENHANCED TO BE USED INCREMENTAL
So if you feel beehive export functionality should be enhanced in one of these ways, I invite you to second these enhancement requests through appropriate calls to Oracle support.
Specifically there is no means to export contacts out of Beehive without recourse to using clients like OBEO.
We launched an enhancement request for this:
14371129 - EXPORT OF CONTACTS FOR WORKSPACE EXPORT SHOULD BE IMPLEMENTED
Please do consider seconding this ER through MOS.
Tom says "Thanks"
ER 14371129 (EXPORT OF CONTACTS FOR WORKSPACE EXPORT SHOULD BE IMPLEMENTED) has changed its status to
97 - Suggestion Rejected
Probably because nobody seconded?
We all will have an issue when we need to get contacts migrated out of team workspaces!