Many thanks for your quick reply! On 2018-01-16 13:14, RjOllos wrote: > * Git repository is very simple: Just add the Git repository to the > configuration and resync if you have a cached repository type.
Yes, that's what I imagined. > * Wiki is simple if there are no page name collisions. You can just > export/import using TracAdmin. However, you can also do this by dump/load > of the wiki table, and since you have to handle a number of other tables, > that is the way to go. Will export/import include history? If not, I'll go for dump/load. I will check name collisions before and do renames if necessary. > * Milestones are stored in the database, so you can do a database dump/load > of the table, and it will go smooth assuming there are no naming collisions OK, renames will be necessary anyway for usability. > * You can dump and reload tickets from the database, but the ticket > numbering will change, assuming the ticket numbering of both system started > at 1. You could dump the ticket table, change the numbering by an offset > and load into the new system. You'll need to modify the attachments, > ticket_custom and the ticket_change tables as well, to account for the new > ticket ids. Sounds like the fun part :~) > * There are some other tables you should be concerned with, like Versions, > Priorities ... and other associated with the ticket system. Also, the > permissions table. Here is the list of tables: > https://trac.edgewall.org/wiki/TracDev/DatabaseSchema This is very helpful! > * You can ignore: auth_cookie, cache, node_change, revision. As mentioned, > I'd also ignore the repository table and just add the new repository > manually. Yes, there are only few repositories anyway. > * Users - depends on the authentication mechanism. It might just be a > matter of merging htpasswd or htdigest files. Most users have access to both systems anyway. I'll probably just add the missing ones manually. > I'd start with a backup of both systems and start working on a script. Feel > free to post here for advice on the script as it progresses. If you refine > the script it could be posted as a script on trac-hacks.org, so happy to > help you get it refined. This sounds like the way to go. > The trac-admin hotcopy utility can be used to dump the database on the > system you are migrating away from. > > Which Trac version and which database type? Do you have plugins installed? 1.2 and PostgreSQL 9.6. There are some plugins, but IIRC, they are all purely UI related. No tables involved. Thanks again for the help and all the specific hints! Cheers -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
