MIGRATION GUIDE
How to migrate from Basecamp to AgencyPro
Basecamp's export is an HTML archive you can browse but not re-import anywhere, so moving to AgencyPro means importing your clients and services by CSV and rebuilding active work by hand. This guide covers each step.
Why agencies switch from Basecamp
Requests instead of message boards
Clients submit work as requests with a service, status and history, rather than as messages scattered across project tools.
Invoicing and payments built in
Invoices, Stripe and PayPal payments and retainer subscriptions are on every AgencyPro plan.
A portal branded as your agency
Every plan includes portal branding and a custom domain. The Plus plan removes AgencyPro branding entirely.
Services and pricing in one catalog
Sell fixed-price, subscription, credit-based (Pro) or hourly (Pro) services from a catalog clients can order from.
Example migration timeline
DAYS 1-2
Export and plan
Export from Basecamp, count active clients and open work, and pick a cutover date at the start of a billing period.
DAYS 3-4
Import clients and services
Fill AgencyPro's CSV templates, test with a few rows, then import the full files.
DAYS 5-9
Rebuild active work and payments
Recreate open work as requests, connect Stripe or PayPal, and set up subscriptions.
DAYS 10-14
Parallel run and cutover
Invite clients, run both tools for one billing cycle, then cancel Basecamp.
Step-by-step migration process
Export your data from Basecamp
Only the Basecamp account owner can export. Open Adminland, choose to export the whole account or a single project, and wait for the email. The export is an HTML archive (open index.html) with active and archived projects, calendars, files and your list of people.
Prepare your client CSV
In AgencyPro, open Imports > Clients and download the template. Every row needs a contact name, an email and an organization (company) name; the import runbook below shows which Basecamp field goes in which column. Keep each file under 1,000 rows and test with a few rows first.
Import clients
Upload the CSV under Imports > Clients, map any columns the importer did not match automatically, and check the preview. Import stays disabled until the preview shows no errors. Rows whose email is already in AgencyPro are skipped, so a corrected file can be re-run safely.
Import services
Download the template from Imports > Services and add the services you sell. Each row needs a name, a type (one_time or recurring) and a pricing type (standard, time_based or credit_based); prices go in as plain numbers. Upload, check the preview and confirm. Credit-based and hourly services need the Pro plan, and recurring services get their billing period in the service editor after import.
Connect payments and subscriptions
Connect Stripe under Payments > Stripe Connect or add PayPal, then recreate retainers as service subscriptions. Clients enter payment details again, because saved cards do not move between platforms.
Recreate active work
Use the archive as a reference and recreate each active project's open to-dos as AgencyPro requests (or a project) for the right client. Archived projects stay in the HTML export.
Invite your team and clients
Invite team members (each seat after the first is billed per plan), then send clients their portal invitation with a short note on where to submit requests and find invoices.
Run in parallel, then cancel Basecamp
Run both tools for one billing cycle. When new requests and payments are running in AgencyPro, save a final Basecamp export and cancel.
What moves to AgencyPro, and how
Import runbook: Basecamp to AgencyPro
AgencyPro's CSV importer takes two files: clients (Imports > Clients) and services (Imports > Services). Each has a downloadable template, and each file can hold up to 1,000 rows. Projects, tasks, files, messages, invoices, payment history, saved cards and time entries are not imported; they are set up by hand or with the migration service on the Plus plan. Where a vendor does not publish its export headers, the left column describes the data, and you match the real header in the importer's mapping step.
1. Client file
Where it comes from: The account export is an HTML archive with your list of people. There is no CSV, so copy each client contact into the AgencyPro template by hand. Basecamp: exports
| From Basecamp | AgencyPro column | Notes |
|---|---|---|
| Person's name (People list in the archive) | name | Required. |
| Person's email, or from your CRM if not shown | Required. | |
| Company you recorded for the person, or the project name | organization_name | Required. |
| Title, if you recorded one | position |
Rows with the same organization_name become contacts of one organization, and the first of them becomes its owner. The match is exact, so "Example Co" and "Example Co." create two organizations. Address and billing details are taken from the first row of each organization. Columns you do not map are ignored.
2. Service file
Where it comes from: Basecamp has no price list. Build the services file from your proposals or invoices.
| From your offer | AgencyPro column | Notes |
|---|---|---|
| Service or package name | name | Required. Must be unique; a name already in AgencyPro is skipped. |
| Short description | description | |
| One-off or ongoing | type | Required: one_time or recurring. |
| How it is priced | pricing_type | Required: standard, time_based or credit_based. Time-based and credit-based services need Pro. |
| Price | price | A plain number such as 2500.00. A currency sign or thousands comma leaves the price empty. |
| Hours in a time block | hours | For time_based services. |
| Credits per purchase | credits | For credit_based services. |
| Shown to clients in the catalog | show_in_catalog | true or false. Defaults to true. |
The CSV sets the basics only. After import, open each recurring service and add its pricing tier (billing period and price per period), and set intake form fields, images, turnaround and FAQs in the service editor.
3. Sample files
Example data, in the column names AgencyPro's templates use. Download the real templates from Imports > Clients and Imports > Services; they include every optional column.
clients.csv
name,email,phone,position,organization_name,billing_city,billing_country
"Jane Example","jane@example.com","+1 555 0100","Marketing Lead","Example Co","Austin","US"
"Sam Example","sam@example.com","","Founder","Example Co","Austin","US"
"Lee Sample","lee@sample.org","","Owner","Sample Studio","Leeds","GB"services.csv
name,description,type,pricing_type,price,hours,credits,show_in_catalog
"Website audit","Technical and content audit","one_time","standard","1500.00","","","true"
"SEO retainer","Monthly SEO work","recurring","standard","2000.00","","","true"
"Development hours (10)","Prepaid block of 10 hours","one_time","time_based","1200.00","10","","true"4. Permissions
- Basecamp: Only the Basecamp account owner can export the account. If the owner has left, transfer ownership first.
- AgencyPro: importing clients needs the create clients permission, and importing services needs the create services permission, in your workspace role.
- Importing does not email anyone. Clients get portal access when you send their invite from the client record, so you choose when they see the portal.
5. Validate
- Import a test file of three to five rows first, then check those clients and services in AgencyPro.
- In the mapping step, check every column. Headers such as Email, Company and Phone are matched automatically; map the rest by hand.
- The preview checks the first 100 rows for missing required values, invalid emails and invalid type values, and the import stays disabled until it shows no errors. Later rows with errors are skipped and listed by row number in the results.
- Rows whose email (clients) or name (services) already exists in the workspace are skipped, not overwritten.
- Each imported client fires the Client Created event. If you run Zaps on that trigger (Zapier is on the Plus plan), pause them during the import.
- After the import, export clients and services from Exports and compare the row counts with your Basecamp file.
6. Roll back
- There is no undo button. Select the imported clients or services in their lists and delete them in bulk, fix the CSV, and import again.
- To correct a client that imported with wrong details, delete or edit it first: re-importing the same email skips the row.
- Keep Basecamp running until the parallel run ends. Your Basecamp data is the fallback if anything needs re-checking.
Common migration challenges
Challenge: The export is HTML, not CSV
There is no spreadsheet of clients or tasks in a Basecamp export. Fix: build the client CSV by hand or from your billing tool, using AgencyPro's import template.
Challenge: Only the owner can export
If the account owner has left, nobody else can run the export. Fix: transfer ownership first, then export before you cancel, and let the download finish.
Challenge: Clients used to message boards
Clients may keep emailing as they did in Basecamp. Fix: in your invitation, show them where to submit a request and where to find files.
Post-migration checklist
Frequently asked questions
What can I import from Basecamp into AgencyPro?
Clients and services, by CSV. AgencyPro's importer (Imports > Clients and Imports > Services) gives you a template, validates the file and shows a preview before you confirm, up to 1,000 rows per file. Projects, tasks, files, comments and history are not imported automatically. Use the archive as a reference and recreate each active project's open to-dos as AgencyPro requests (or a project) for the right client. Archived projects stay in the HTML export.
Can I export my data from Basecamp?
Yes, if you are the account owner. In Adminland you can export the whole account or one project. Basecamp emails you when it is ready, and the download is an HTML archive with projects, calendars, files and people. Basecamp notes the export cannot be imported back into Basecamp, and it does not import into AgencyPro either; it is your archive.
How long does the move take?
It depends on how much active work you have. The client and service imports are quick once your CSVs match AgencyPro's templates. Rebuilding open work is the bigger job, so count your active clients and open items in Basecamp before you pick a cutover date, and plan one billing cycle of parallel running. The timeline on this page is an example for a small agency.
What does the AgencyPro migration service include?
The migration service is part of the Plus plan ($149 a month, or $124.17 a month billed annually). The AgencyPro migration team helps you move from Basecamp, including setting up the projects, tasks, files and history that the CSV importer does not bring in. On Basic and Pro you use the CSV importer and rebuild active work yourself.
When is it better to stay on Basecamp?
If your team values Basecamp's simplicity, clients rarely need to log in, and invoicing lives happily in your accounting tool, staying on Basecamp is reasonable. AgencyPro is a better fit when you want requests, invoices and payments in the same client portal.
Continue learning
AgencyPro project management
Run tasks and timelines alongside billing and CRM →
Agency project management guide
A practical playbook for running agency projects →
Best project management for agencies
See how leading PM platforms compare for agency work →
AgencyPro vs Basecamp
Side-by-side feature and pricing comparison →
Outgrowing Basecamp for client work?
Book a call and we will help you plan the client CSV, your service list and which active projects to rebuild first.