How to Migrate from Close to Attio
Close organises everything around Leads that hold Contacts and Opportunities. Map each Lead to an Attio Company, export activities as JSON, and rebuild Smart Views and calling workflows by hand.
- Difficulty
- Medium; activity history is the hard part
- Typical duration
- Estimate after a representative sample
- Downtime
- None for reading; agree a cutover for calls and emails in progress
- Native importer
- Import2 via Attio on paid plans (Close is a supported source); CSV and API are alternative routes
| Close | maps to | Attio | What to watch |
|---|---|---|---|
| Lead | Company (or Person for single-person leads) | A Lead is the container record in Close. Use the website or email domain to match it to an Attio company. | |
| Contact | Person | Contacts belong to a Lead. Close exports them from the Leads page, one row per contact, not from a Contacts Smart View. | |
| Opportunity | Deal | Enable the Deals object first. Map Opportunity Status to a deal stage and keep the value, currency and close date. | |
| Lead or Contact custom field | Attribute | Common fields in the export include All Custom Fields. Check in a sample that lead-level and contact-level fields both appear. | |
| Note, Email, Call, SMS (Activity) | Note, or archive | Close exports all activity types only as JSON. Attio's CSV importer takes no notes; load them with the migration tool or the API. | |
| Task | Task | Close shows tasks only as activity dates in the All fields export. Treat task content as a separate check. | |
| Smart View | Saved view (rebuild) | Not exported. Rebuild each view in Attio from its filters. |
What transfers cleanly
- Leads, contacts and opportunities, with custom fields mapped to Attio attributes.
- Notes, through the migration tool or the Attio API.
- Email and calendar history, rebuilt from each user's connected mailbox.
What doesn't come across
- Activities are JSON-only. CSV is not suitable when you need emails, calls, SMS and notes; JSON is the one format that exports all activities.
- Call recordings. Attio's migration tool does not include call recordings; keep the Close files.
- Contacts export source. A Smart View built on the Contacts tab cannot be exported. Start from a Leads Smart View.
- Opportunities export. The Export button sits only on the legacy Opportunities list view; from the Leads page you get the opportunities of matching leads.
- Smart Views, templates and sequences. Smart Views and templates need a separate support-tool export or manual rebuild; they do not map to Attio objects.
Migration order that works
- Count Leads, Contacts, Opportunities and activities by type; save a Smart View for each group to migrate.
- Export from the Leads page: Leads and Contacts as CSV with All Custom Fields, activities as JSON. The download link expires after 7 days.
- Decide per Lead: company, person, or both; add the company domain to every contact row.
- Enable Deals and create custom attributes in Attio.
- Run the migration tool on a sample, or import companies, people and deals by CSV in that order.
- Load notes and other activity you keep from the JSON file through the migration tool or the Attio API.
- Compare lead, contact and opportunity counts with Close, and reconcile open opportunity values.
- Rebuild Smart Views and calling workflows, connect mailboxes, then retire Close after sign-off.
Decide what a Lead is
Close has no separate company record. A Lead can be a company with several contacts, or a single person with a made-up company name. The export gives one row per lead for the lead file and one row per contact for the contact file, so both fit Attio, but you choose the mapping.
For each group of leads, decide: company with people, or person only. Companies need a domain. Add it to the contact rows before import, because Attio matches people to companies by domain and to people by email.
Pick the format by what you need
Use CSV for leads, contacts and opportunities. Choose Common fields for the core columns and All Custom Fields, or All fields for address data, activity dates and Smart Fields such as email counts. Smart Fields are calculated values, so skip them.
Use JSON for activities. Close names it the only route that exports emails, calls, SMS, notes and custom activities together, and the best for large exports. Attio's CSV importer does not import notes, so plan the note load through Import2 or the API.
What stays behind
Smart Views, templates, sequences and call recordings do not arrive. Export call recordings from Close and store them in a drive linked from the Attio record. Rebuild each Smart View as an Attio view from its filter, and keep a written list of the Close workflows to recreate.
Need help moving from Close to Attio?
Craftt, the CRM team behind weekcrm, plans and runs the migration: field mapping, deduplication, history and a cutover your team won't notice. You get a fixed quote within one business day.

