Close migration pack

Moving from Close to Myra. This guide assumes you have never touched an API key in your life. Follow it top to bottom and you will be fine.

Total hands-on time: about 20 minutes. The import itself then runs on its own in the background - usually 1-4 hours depending on how much history you have.

0. The whole thing in six lines

1. Make a Close API key (5 minutes, section 2).
2. Paste it into Myra → Migrations (section 3).
3. Run a dry run and read the counts (section 4).
4. Start the real import and walk away (section 5).
5. Spot-check ten contacts (section 8).
6. Rebuild automations, connect your phone/email, go live (sections 7 and 9).

Nothing is ever written back to Close. The connection is read-only. Your Close account keeps working exactly as it does today for the whole migration - there is no cutover moment where both are broken.

1. Before you start

You need three things:

About "one organisation, one client". Close calls your whole workspace an organisation. Myra calls each business you manage a client. If you run several Close organisations, you run this process once per organisation, each into its own Myra client. Don't try to merge two Close organisations into one Myra client - you'll get duplicate contacts.

2. Get your Close API key

An API key is just a long password that lets Myra read your Close data. It is not your Close login and it can be deleted at any time without affecting your account.

Steps

1. Sign in to Close at app.close.com on a desktop browser. (The mobile app cannot create API keys.)

2. Click your profile picture / name, bottom-left, then Settings.

3. In the settings menu on the left, scroll down to the Developer section and click API Keys. Direct link: app.close.com/settings/developer/api-keys

4. Click the + New API Key button (top right of that panel).

5. Give it a name you'll recognise later - type exactly: Myra migration

6. Click Create / Generate.

7. Close shows you the key once. It looks like this:

   api_1a2b3c4d5e6f7g8h9i0j.KLmnOPqrStUvWxYz1234567890abcdef
   

8. Click the copy icon next to it. Paste it somewhere safe for the next five minutes (a note, a password manager - not a public chat).

 Close → Settings
 ┌──────────────────────────────┬────────────────────────────────────────┐
 │ Your Account                 │  API Keys                  [+ New API] │
 │ Organization                 │  ─────────────────────────────────────  │
 │ Customizations               │  Name              Created     Actions │
 │ Connected Accounts           │  Myra migration    just now    ⧉  🗑    │
 │ DEVELOPER                    │                                        │
 │  › API Keys        ← click   │                                        │
 │    Webhooks                  │                                        │
 │    OAuth Apps                │                                        │
 └──────────────────────────────┴────────────────────────────────────────┘

Things that go wrong here

• I can't see the Developer section. You are not an admin on that Close organisation. Ask an admin to either promote you or create the key and send it to you privately.
• I closed the box before copying the key. You cannot get it back. Delete that key and create another. No harm done.
• Which key do I use if there are several? Make a new one called Myra migration anyway. That way you can delete it after the migration without breaking anyone else's tools.
• Is this safe? The key is stored encrypted in Myra and only ever used to read. When your migration is finished, go back to that same screen in Close and click the bin icon next to Myra migration. Deleting it stops Myra reading anything, forever.

Reference: Close's own documentation - API Keys & OAuth and Authentication with API keys.

3. Connect Close to Myra

1. In Myra, open Migrations from the business sidebar.
2. Click New migration.
3. Choose Close as the source platform.
4. Paste the key into the API key box.
5. Choose the destination client from the dropdown.
6. Click Validate & scan.

Myra now calls Close once to check the key works, then counts everything in the account. This takes 10-60 seconds. You'll see something like:

 Connected to: Acme Sales Co.        (Close organisation)
 ──────────────────────────────────────────────────────
 Contacts            4,812
 Leads (companies)   3,109
 Opportunities         874
 Notes              11,540
 Calls               6,201   (2,118 with transcripts)
 Emails             19,006
 SMS                 3,455
 Meetings            1,092
 Tasks                 611
 Users                  14
 Custom fields          22
 Pipelines               3   (17 stages)

Read these numbers. Compare them to what you see in Close. If contacts say 12 and you have 5,000, the key is scoped to the wrong organisation - make a new key while signed into the right one.

If a row shows "couldn't count" rather than a number, that is not zero - it means Close refused that request. Retry the scan. If it keeps failing, contact support before importing; running an import off a failed scan hides problems.

4. Do a dry run first

Always. It costs you nothing.

Click Dry run. Myra walks the same import, decides what it would create, update and skip, and writes none of it. When it finishes you get a report:

 DRY RUN COMPLETE
 Contacts        4,640 create   172 merge into existing   0 skip
 Opportunities     874 create
 Pipelines           1 create   2 match existing
 Conversations  28,662 create
 Appointments    1,092 create
 Tasks             611 create
 ⚠ 47 contacts have no phone or email and will import as name-only

What to look at:

• Merge into existing - contacts Myra already has. It matches on email, then on the last 10 digits of the phone number. If this number is unexpectedly large you may be importing into the wrong client.
• Pipelines: match existing - Myra will reuse a pipeline you already have rather than making a second one with the same name. Check that's what you want.
• Warnings - name-only contacts are fine, they just can't be called or emailed until someone adds a number.

Happy? Click Start import. Not happy? Change the destination client or fix the data in Close and dry run again.

5. Run the import

Click Start import. Then close the tab if you like - it runs on our servers, not in your browser.

A worker processes the run continuously and paces itself well under Close's rate limits, so your Close account stays fast for your team while it runs.

Order of work. Structure lands first so records have somewhere to go, then people, then history:

 users → custom fields → pipelines → contacts → opportunities
   → notes → tasks → meetings → calls → emails → SMS

Contacts land early on purpose: your team can start using Myra while the heavy conversation history is still streaming in.

The progress screen shows each stage with a live count and one of: waiting, running, done, failed. You can leave and come back any time.

Safe to interrupt. The import is resumable and idempotent - fancy words meaning: if it pauses, it picks up exactly where it stopped, and if you run it twice you get one copy of everything, not two.

Nothing fires. Every imported record is stamped as imported, so automations, live transfers, notifications and conversion events do not run on historical data. Nobody gets a text from 2023.

6. What comes across

Everything keeps its original timestamp, so inboxes and timelines read the same as they did in Close.

What does not come across

If it isn't in the first table, assume it needs rebuilding.

7. Rebuilding your sequences

Three routes, fastest first:

1. Start from a template. Automations → New → From template. Most follow-up, no-show, reminder and nurture flows already exist. Edit the copy and the timings.
2. Describe it to the AI builder. Plain English works: "email on day 0, SMS on day 2, create a task on day 5 if they haven't replied". Myra builds the steps.
3. Screenshot to prompt. Open the sequence in Close, screenshot the whole thing including each step's settings, paste the screenshots into the AI builder. It reproduces the structure for you to check.

Before switching any automation on, check three things: the trigger, every delay, and the from-number / from-address on each send step. Then test it end to end with a dummy contact using your own phone and email.

8. After the import - the ten-contact check

Pick ten contacts at random and open them side by side in Close and Myra. For each, confirm:

• Name, phone, email match
• Company / business name is there
• Deal value and pipeline stage match
• Tags (from Close lead statuses) are present
• The timeline shows notes, calls and emails at the right dates
• Open tasks are there and assigned sensibly

Then check the structure:

• Pipelines exist with the right stages, in the right order
• Opportunity counts per stage look roughly right
• Custom fields exist and have values

Found a problem? Note the contact and the migration ID and send both to support. Do not delete and re-import - re-running the migration is safe and will not duplicate.

9. Go-live checklist

• Ten-contact check passed
• Team invited in Settings → Team and permissions set
• Phone number bought or ported, A2P registration submitted
• Email sending connected and verified
• Calendars connected, availability set
• Automations rebuilt, tested with a dummy contact, switched on
• Old Close sequences paused so nothing double-sends
• Close account kept read-only for 30 days as a fallback
• Close API key Myra migration deleted once you're settled

10. Troubleshooting

"Invalid API key" when I click Validate. Whitespace is the usual culprit - re-copy the key with the copy button rather than selecting it by hand. If it still fails, the key was deleted or belongs to a different organisation; make a fresh one.

The scan counts look far too low. The key is scoped to one user and one organisation. If you have several organisations, sign into the right one before creating the key.

The import stalled. Open the run and click Resume. It restarts from the last completed page, not from the beginning.

I imported into the wrong client. Stop the run and contact support with the migration ID before starting another. Importing the same organisation into a second client creates two copies across two workspaces.

Duplicate contacts appeared. Check Client settings → Contacts → duplicate matching. If matching is set to require all fields, a contact with a phone but no email won't match an existing record that has both. Loosen the rule, then re-run - the merge is idempotent.

Transcripts are there but I can't play the call. Expected. Close keeps the audio; we import the text. The player shows a transcript-only badge.

Still stuck? Contact support with your migration ID (top of the migration page) and we'll look at it with you.