Add Projects from Existing Pipeline

Moving a project to Assembla is as easy as starting a new project (that’s the Assembla magic).

Post new procedures for the team

Transitions are a little smoother when people know what they are supposed to do. Post policies and handling requests on a wiki page so that everyone knows what they are supposed to do. A few good topics to start with:

Creating tickets: Who creates them, assigns them and what do the statuses mean?
Procedure changes: If you are switching to the Time tool, tell people what the new policy is for invoicing. Similar for any other tool changes.

Move tickets/tasks and milestones

If you have a large number of tickets in another tool and wish to import them to the new workspace, contact Assembla Customer Support. You can automatically import tickets and milestones from BaseCamp via the API.

Assembla organizes tickets by milestone. Agile projects use two milestones:

Next Release / Iteration
Product Backlog

Move code

If it's a software project, you will need to load the repository. This can be either loaded from an existing repository, or imported from local code. There are two ways to upload your code to our host:

Upload an existing repository, or
Run "SVN import" to load the first version of code

Plan backups

Assembla has never had an instance of data loss. That said, it is still a good idea to backup your work. Assembla offers commercial upgrades which allow you to backup data posted to Assembla to your Amazon S3 account.

Assembla Support