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

From Kosmos Wiki
Jump to navigation Jump to search
 
(5 intermediate revisions by 3 users not shown)
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 ==
Line 14: Line 14:
 
* Flowdock
 
* Flowdock
 
* Campfire
 
* Campfire
* Hipchat
+
* HipChat
 
* IRCCloud
 
* IRCCloud
 
* Grove.io
 
* Grove.io
Line 20: Line 20:
 
== Notes ==
 
== Notes ==
  
* Grove.io has JSON files for single days or complete history. Resource names are guessable/common.
+
* <del>Grove.io has JSON files for single days or complete history. Resource names are guessable/common.</del> Grove has been shut down.

Latest revision as of 09:47, 5 May 2017

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. Grove has been shut down.