Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Comments on Database migration between Codidact and SO for Teams

Parent

Database migration between Codidact and SO for Teams Question

+3
−0

If I have my "own instance of the Codidact software (QPixel) locally, on a server" (cited from here), can I easily migrate the overall database (user accounts, Q&A, etc.) to a Stack Overflow for Teams site ("SE's hosted, proprietary service") and vice versa?

Context

I'm trying to convince my boss to use a Q&A site for his company and I'd like to make him understand that Codidact is the best choice ;).

Since, if I understood correctly, Codidact does not currently offer this service (I mean: a private site) I am going to suggest that my boss use a local Codidact software on a server.

But, he will be afraid of what might happen if we realize (after using it for a long time) that a local Codidact is "not convenient" ultimately and we want to switch to a commercial solution like SO for Teams.

So I would like to be able to tell him: "don't worry, if a local Codidact doesn't suit us, we'll switch to SO in a minute!".

So the question is, can I tell my boss something like in the previous sentence? In other words, is it "easy" to migrate a users and Q&A database between these two platforms... What can be the lost during the transfer (reputation points, comments, chat, etc.)?

BTW, I don't know anything about databases, so I don't really understand what data must be "migrated" exactly (but this is maybe another question).

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+4
−0

I'm afraid this is not really a use case that was envisioned and that Codidact has no support for this. But actually the problem in doing this at all is that SO for teams (to my knowledge) does not offer any import functionality. We are no longer using it at the university where I work, so I can't double check, but I don't recall seeing such an option.

Note that the other way around, SO to Codidact is possible (we've done it a year ago). I wouldn't call it easy to do, and the process could be improved, but it is possible at least.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

2 comment threads

Q&A export in Markdown format? (3 comments)
I was going to add an answer, but this pretty much says everything I would have said anyway. SO hasn'... (1 comment)
Q&A export in Markdown format?
zetyty‭ wrote 11 months ago

Ok thanks a lot! I would never guess that SO has no import functionality, I'm so naive... About the export facility of Codidact, are the Q&A exportable directly in Markdown text format? (same question for SO export if you know the answer)?

Taeir‭ wrote 11 months ago · edited 11 months ago

SO for Teams uses a JSON based export format which has the posts in it in markdown format. Codidact I don't think has any file export possibility at the moment, but that could be added if there is an interest for defining a proper import/export format. I think the main reason this was not done before, is that you are also in control over your own MySQL database, so you already have a way to move the data (not the case for SO for teams).

Extracting the posts using the rails console or the database should be pretty doable. However, at the moment there is a bug that you do get it in HTML format rather than explicit markdown (markdown renderers would still render it correctly, as they also support basic HTML).

ArtOfCode‭ wrote 11 months ago

zetyty‭ It'd be easy enough to export posts in Markdown form - it could be done with one SQL query, which you could then export into any format you like.