Difference between revisions of "Feature:Migration from existing systems"

From Kosmos Wiki
Jump to navigation Jump to search
m (Administrator moved page Feature2:Migration from existing systems to Feature:Migration from existing systems without leaving a redirect)
Line 1: Line 1:
 
== Summary ==
 
== Summary ==
  
In order to make migration from other systems/services easy and enjoyable, both for just trying out the software as well as transferring all data for a complete org migration to 67P, there will be a subsystem for importing data and configuration.
+
In order to make migration from other systems/services easy and enjoyable, both for just trying out the software as well as transferring all data for a complete org migration to Kosmos, there will be a subsystem for importing data and configuration.
  
 
== Features ==
 
== Features ==

Revision as of 15:37, 6 June 2015

Summary

In order to make migration from other systems/services easy and enjoyable, both for just trying out the software as well as transferring all data for a complete org migration to Kosmos, there will be a subsystem for importing data and configuration.

Features

  • Import user names/accounts
  • Import channels, including their chat history
  • Import shared files

Migration sources

  • Slack
  • Flowdock
  • Campfire
  • Hipchat
  • IRCCloud
  • Grove.io

Notes

  • Grove.io has JSON files for single days or complete history. Resource names are guessable/common.