Migrate to Kolab, now! - How to simplify the complex task of migrating data between groupware platforms (Kolab Summit 2015)

1. Migrate to Kolab, Now!
How to simplify the complex task of migrating
data between groupware platforms
2015-05-03
Kolab Summit, The Hague

2. 2www.groupware-umzug.de

3. Agenda
►about audriga
►Migrate to Kolab, Now!
3

4. audriga – groupware migration as a service
►Based in Karlsruhe, Germany
►Award-winning service
►Leading telcos and hosters as customers
4

5. Data liberation / data portability
"Plus, we can ensure there is competition in the market. You
shouldn't be locked in, married to one Cloud provider
for life. That would mean less consumer choice, and less incentive
to innovate and improve Cloud services. It should be easy to
switch Cloud providers, if you find a more suitable offer.
And for that, you need to be able to take your data with you: data
portability."
5
Former EU-Commissioner Neelie Kroes

6. Kind of imapsync in the cloud,
on stereoids
► Migrate IMAP to IMAP
► With…
 Cloud-based scalability
 A web-based, white-labeled UI
 A REST API
► Plus…
 POP3, EWS, PST, MBOX, MailDir/EML (Email)
 Groupware data (see next slides)
6

7. Supported data types
►Email
►PIM-Data (Contacts, DistributionLists,
Calendars, Tasks, Notes)
►Files
►Folder permissions
►Settings (Signature, Forward, Vacation reply, …)
7

8. Supported source/destination systems
Native connectors
► IMAP/POP3
► Exchange 2007+
► Exchange 2000+
► Google Apps
► Zimbra
► OpenXchange
► IBM Notes
► Novell GroupWise
► CommuniGate Pro
► Windows Live/Outlook.com
Generic connectors
► CardDAV/CalDAV
 Kolab, iCloud, Yahoo, Atmail,
eGroupware, Kerio Connect,
SoGo, Zarafa …
► File-based connectors
 (read/write files from/to FTP,
S3, …)
 PST
 MailDir/EML, mbox, …
 vCard, iCal, CSV, LDIF, …
8

9. Offerings
Self-service migrations
► UI (can be white-labeled)
► Typical scale: 1 to 1000s of
mailboxes
► Example: Customer moving 50
mailboxes from Google Apps to
KolabNow
ISP migrations
► Supporting large-scale migrations
of ISPs
► Typical scale: 100s to millions of
mailboxes
► Example: Cable provider moving
>10.000 mailboxes from Google
to OpenXchange (Contacts,
Calendars, Tasks, Files, Settings)
9

10. 10
Migrate to…

11. Migration scenarios
►One by one
►„Big bang“ (over night/weekend)
►Big switch with pre-migration („archive first“/email
first)
►Limiting factors
 Support capacity
 System availability requirements
 Collaboration requirements
 Authentication options
11

12. Physical limits
►Bandwith limits
►Hardware limits
►Throttling limits
12

13. Data people tend to overlook
►Public folders, ressource mailboxes, etc.
►Aliases
►Rules
►„This special field responsible for CRM
integration“
13

14. Mappings!
►User/group/ressource ids
►Different concepts (ressources, public folders)
►Special folders (Sent, Drafts, …)
►Special data fields
►Weird legacy data
14

15. Cross-Migration tipps
►Do Dry-runs!
►Migrate before switching your MX
►Consider your users!
15

16. Thank for listening!
►Any questions?
►What are the migration experiences and
requirements of the Kolab Community?
16
“We found the service to be exceedingly easy to use. It is literally enter
credentials and then point, click and migrate.”
“A migration tool like audriga helps hosters get more email hosted”
“audriga solves problems that hosters need to solve”

17. audriga GmbH
Hans-Jörg Happel
happel@audriga.com
+49 (0)721 170 293 16

18. Web-based User Interface
18