Assembla FAQ and Documentation

Moving a project to Assembla is as easy as starting a new project.

Post new procedures for the team

Transitions are a little smoother when people know what they are supposed to do. Post policies and procedures 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: E.g., If you are using the Time and Scrum tools, explain the procedure for time and status reporting.

Move tickets 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 to Assembla Tickets via the API in the Milestones page, Import/Export tab.  If you have an existing Trac project, you can upload the Trac dump in your Trac Admin-Import page.

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:

Plan backups

Assembla has never had an instance of data loss. That said, it is still a good idea to backup your work. You can set up an automated daily backup to your Amazon S3 account via your Admin-Resources page.