Bringing Your Data In
Importing from a Spreadsheet
If your list lives in a spreadsheet, or in a system that can export one, the import brings it into ORCA. You match the file's columns to ORCA's fields, look at what will happen, and only then press Import.
It also works for a file you load more than once. Tick Update existing records and rows already in ORCA are matched and updated, not added twice, so a fresh export from the system you are moving from can go in every week until you switch over.
Where to Find It
Go to Settings > Import. If you are setting up a new account, the Bring your list in step of Your First Days has an Import a spreadsheet button that goes to the same place.
You don't need Settings access to add records. Without it, the import opens in the main app rather than inside Settings, and works the same way, except for Update existing records, which is only for people with Settings access.
The page is headed Import, with the four steps along the top: Upload a file, Say what it holds, Match the columns and Review and import.
What the File Should Look Like
One sheet, as a CSV or Excel file (.csv, .xlsx or .xls). The column headings go in the first row, with one record on each row below.
| Company | First name | Last name | |
|---|---|---|---|
| Lantern Partners | Priya | Shah | priya@lantern.example |
| Copperfield Advisory | Tom | Wren | tom@copperfield.example |
A title, notes or blank rows above the headings will be read as data, so take them out first. The headings themselves can say anything you like. You match each one to an ORCA field at step 3.
Step 1: Upload a File
Choose a file, or drop one on the box under Your file, and press Next. Nothing is brought in until you have reviewed it at step 4.
Step 2: Say What It Holds
One kind of record in each file. Under Each row is one, choose:
- Account
- Contact
- Account, with its key contact, where each row is a company and the person you deal with there
- one of your sections, such as a Deal or a Project. Only sections you can create records in are listed.
This is also where you choose Update existing records, if you have Settings access. See Updating existing records below.
Step 3: Match the Columns
ORCA lists its fields for the kind of record you chose. For each one, pick the column of your file that holds it. A field left on Skip brings nothing in.
Press Review import when you're done, or Start again to go back to the beginning.
Step 4: Review and Import
The first few rows shows your file as the columns are matched. If a value sits under the wrong heading, the matching is wrong. Go back and change it before you import.
Press Import when it looks right. The last page says what happened, with buttons to Import another file or go Back to the dashboard.
Without Update existing records, every row is added as a new record. Load the same file twice and you'll have everything twice.
Updating Existing Records
This is for a file you load more than once, such as an export from the system you are moving from. Rows already in ORCA are matched and updated, not added again. It's only offered to people with Settings access, because the file's values replace what is in ORCA.
Turning it on
At step 2, tick Update existing records, then fill in Where the file comes from, for example "Zoho". Use one name for each system and stick to it. ORCA keeps that system's IDs and your column matching under the name, so the next file from the same place needs no choices. Names you have used before are offered as you type.
It works on one kind of record at a time. Account, with its key contact can't be updated, and choosing it with the box ticked brings you back with "Updating works on one kind of record at a time. Choose Account, Contact or one of your sections."
Match on
Step 3 gains a Match on card: how ORCA tells that a row is already here. The old system's own ID is the surest way, so choose the column that holds it under ID column.
- Contacts can also match on email. With Email, when the ID finds nothing ticked, a contact someone typed in by hand is found by their email and takes the ID from then on, so they aren't added twice. If more than one contact in ORCA has that email, the row is skipped rather than guessed.
- Accounts can also match on name. With Company name, when the ID finds nothing ticked, a company typed in by hand is found by its name and takes the ID from then on. Small differences such as "Ltd" and "Limited", or capitals, don't count, so "Lantern Partners Ltd" and "LANTERN PARTNERS LIMITED" are one company.
- Records in a section match on the ID and nothing else. A row with no ID is skipped.
If there's nothing to match on, ORCA says so before you go any further, for example "Choose the column that holds the ID. Records in a section are matched on it and on nothing else."
What an update changes
For every row that matches, the file's values replace ORCA's, in the columns you have matched. An empty cell changes nothing, and a field left on Skip is left as it is. Nothing is ever deleted: a row missing from this week's file leaves its record exactly where it was.
The review shows what will happen first
With Update existing records ticked, step 4 opens with What this import will do. It's worked out from the whole file, with nothing written yet:
- To add: rows ORCA doesn't have yet.
- To update: rows that match and would change something.
- Already match: rows that match and would change nothing.
- To skip: rows that can't go in, with the reason and the row numbers under Rows to skip.
Below the counts, ORCA also tells you:
- how many companies named in the file aren't in ORCA yet and will be added;
- how many stage changes will be left out, because the stage needs a sign-off you can't give. The rest of the row still goes in;
- Values ORCA has no match for: picklist options or people named in the file that ORCA doesn't have, with how many rows each. The field is left as it is on those rows. Add the option in ORCA and load the file again to bring them in.
If something looks off, press Change the column matching. Otherwise press Import.
Loading the next file
ORCA remembers the column matching for each source and each kind of record, by the column headings. Next time you load a file from the same place, with the same name under Where the file comes from:
- if every column you matched last time is in the new file, you go straight to the review, which says the columns are matched as they were the last time;
- if some are missing, step 3 opens with what it could find already filled in.
Change the column matching on the review takes you back to step 3 whenever you want to change it.
Why a row is skipped
Each skipped row comes with its reason. The ones you're most likely to see:
- "No ID in this row, so there is nothing to match it on."
- "Its ID has been rounded by a spreadsheet (it reads like 5.2E+18). Export the ID column as text."
- "More than one contact in ORCA has this email, so there is no telling which one to update."
- "Its record is frozen, so it is left as it is." See Freeze and Revise.
- "Your role can't change this record."
- "Its record is behind a barrier, where only its deal team can change it." See Barriers.
- "This ID is already linked to a record in another section under the same source name. Give each section its own source name."
The import works as you: your access to sections, your own-records rule, barriers, frozen records and sign-offs all apply, as they would if you changed each record by hand.
Tips
Export IDs as text. Spreadsheet programs like to turn long ID numbers into things like 5.2E+18, which no longer match anything. Format the ID column as text before you save the file.
Give the source the same name every time. "Zoho" and "zoho" are the same, but "Zoho export" is a different source, with its own IDs and its own remembered matching.
Load accounts before the records that point at them. A company named in a contacts or records file that ORCA doesn't have is added along the way, but it's tidier to bring the accounts in first and let everything else find them.
Rather not export files at all? Where it is switched on for your ORCA, you can connect the system you are moving from instead, or have your own AI assistant bring the data across through the API. Moving to ORCA compares the three.
Related
- Moving to ORCA : the three ways to bring your existing data across
- Connecting Another System : bringing data across from your old CRM with no files
- Using the ORCA API : the upsert endpoints, for scripts and AI assistants
- Business Card Import : adding one contact from a photo of their card
- Sign-offs : stages only named roles can move a record to
- Data Export : taking your data out again
