aC forum: Import Basecamp XML

Post #14 by [user deleted]

[user deleted] — Mon, 25 Dec 2006 14:53:26 CST

It could quite easily be extended to include tasks and milestones - Basecamp exposes this in their API - you could also run the SQL query on the database after its been generated (rather than just output the SQL to a file or the screen)

Post #13 by mikemanh

mikemanh — Tue, 19 Dec 2006 05:13:20 CST

Awesome Matthew! Would it be hard to add tasks and milestones?

I realize that ac isn't 1.0, but it would be good for users who need to get away from basecamp now to get all their stuff moved over, and then use upgrade scripts from that point on. It's a stopgap solution

Post #12 by Ilija Studen

Ilija Studen — Mon, 18 Dec 2006 09:42:27 CST

Hi Matthew,

Thanks for the effort. Code looks pretty good. It can also be ported to almost any platform in pretty short amount of time (most important thing is loop through API responses and inserting collected data into database).

You are right about the current status of activeCollab project. Its pre-1.0 and unlike some open source projects that will never hit 1.0 milestone because they like 0 so much in this case it really means that activeCollab is not ready for its primetime.

Hopefully one day activeCollab will be good enough so you find it worthy to do the switch ;)

Post #11 by [user deleted]

[user deleted] — Mon, 18 Dec 2006 04:31:04 CST

I created a little Ruby Class using the Basecamp API that generates SQL for importing Projects, Users, Messages, Comments and Tags (Categories) into ActiveCollab;

http://matthewhutchinson.net/articles/2006/12/18/basecamp-activecollab-importer

Post #10 by [user deleted]

[user deleted] — Thu, 10 Aug 2006 04:59:20 CDT

I can see this as something interesting and useful. I'm hesitant to really go with the double interface idea where you pull/update the data back and forth with the external data item. The performance hit of having to do remote calls in addition to the local ones already being run would just suck. Not to mention the rules needed to disable fields of data that activecollab supports that basecamp doesn't etc.

Post #9 by [user deleted]

[user deleted] — Wed, 09 Aug 2006 20:33:10 CDT

I'd like to second the OP's original request.

I'm about to dump Basecamp in favour of activeCollab and I'd love an import feature. (in due time of course)

cheers

Post #8 by [user deleted]

[user deleted] — Fri, 04 Aug 2006 06:56:56 CDT

Throwing an idea here. With Basecamp's new API, we should be able to build a plugin that can login and grab live data from Basecamp. What I think would be really cool is if we could find a way to integrate Basecamp data into aC and make it feel native. e.g. Task items show up in the respective lists or milestones show up on the calendar. I figured there could be a tiny icon or some identifying factor that would show it was external data. But nothing obtrusive.

So if you altered any Basecamp data in aC it would update it in Basecamp and vise versa. Considering the syncing issue, if someone went to alter a Basecamp item it would do a check first before allowing you to alter an item.

Food for thought. If we could work this idea out, it could easily expand to other platforms as well.

Post #7 by Ilija Studen

Ilija Studen — Fri, 14 Jul 2006 07:27:31 CDT

As I said, it is too early for such a tool. activeCollab is not feature complete product and if anyone writes that kind of tool he'll need to update it as aC codebase changes through time.

Post #6 by [user deleted]

[user deleted] — Fri, 14 Jul 2006 05:28:41 CDT

This would be a really awesome !

Has anyone tested this out, transferring from basecamp to collab?

Post #5 by Ilija Studen

Ilija Studen — Mon, 10 Jul 2006 02:47:34 CDT

Export will be provided but I can't promise when. Also, API is one of the priorities so you will have access to your data from any platform you want if you have proper permissions.