= Move, Copy and/or Synchronize Parts or all of Trac Instance =

There are some use cases where moving, copying, synchronizing trac instances (or part of trac instances) might be benefitial:
 * single persons working disconnected:
   * they would need to get the latest information they have access right to onto a laptop.
   * when reconnecting to the network they need to merge their changes into the central trac instance
 * InterTrac:
   * information is entered into the wrong instance and should be moved to another one.
   * information should be moved to a newly created trac instance

related tickets are: #1465, #1465

== some solution ideas grabbed from the mailing list and the tickets ==

 * use import/export with csv
 * use (implement) versioning backenends as trac storage backend
 * use (implement) synchronisation based on the xml-rpc based on timeline information

== challenges which may come up ==

 * stable ticket numbering must be guaranteed (either provide prefixes or numbering ranges for the instance which created it or invent something else)
 * in the intertrac configuration, there might be links on a moved object. these links would have to be changed. is there any "backlink" or "where did it get used" in trac to find this information?
 * different trac instances might have different ticket fields and field contents, i.e. administrative settings. but [h:EmailtoTracScript] also has this problem, and it anyway works.