Bring what you already have.
Your contacts and companies from one file, even with their stage, checked before anything is saved.
Matched, checked, then saved.
Any spreadsheet, as it is.
Bring a CSV, TSV or Excel file. Contacts or companies, one file at a time.
Columns matched for you.
Each column is matched to a field, and every match shows how it was made. What it learned from your last import is remembered.
Duplicates met, not doubled.
Rows that match an existing record are updated, not duplicated. You choose what to match by, such as phone or email.
Nothing is saved until you check.
See how many rows will import and what was skipped. Nothing is saved until you commit.
From your file to your records.
Five steps, in this order.
- 1 Upload
Drop your file.
Choose a CSV, TSV or Excel file with your contacts or your companies.
- 2 Map
Columns are matched.
Each column is matched to a field, and each match says how it was made. Mappings it has learned before come back on their own.
- 3 Check
Check the doubtful ones.
A match it is not sure of is flagged, and a column it could not place is shown as ignored. You decide what happens to both.
- 4 Preview
See every row first.
Each row shows whether it is fine or a duplicate, with the count that will import. Nothing is saved yet.
- 5 Result
Commit when it looks right.
Commit, and the result shows how many were created and how many skipped.
Where this does the most.
Maple Studio has two years of clients in one spreadsheet. One file brings them in; the doubtful column is flagged before anything is saved.
Checked · before savingRyan Adams appears twice in your list, with the same email. The preview marks the second row a duplicate, so he arrives once.
Duplicate · caught in previewSee the playbook →Mrs Keller and Mr Reed come from last year's exported list. Their columns are matched the way you matched them last time, and you only check what changed.
Matched · learned from beforeSee the playbook →What the import does not do.
And what happens instead.
- It does notIt does not import everything.InsteadContacts and companies only. Other records stay where they are.
- It does notIt does not create new fields from your file.InsteadColumns it cannot place are shown as ignored.
- It does notIt does not guarantee every stage lands where you meant.InsteadA stage value that is not one of your stages starts in your first stage. Check stages after the import.
- It does notIt does not save while you look.InsteadNothing is written until you commit, and an import over your plan's limit is refused whole.
Which files can I import?
CSV, TSV and Excel files (.csv, .tsv, .xlsx, .xls). Each file brings contacts or companies, one at a time.
Do I need to rename my columns first?
No. Felesh matches them to fields and shows how each match was made. A match it is not sure of is flagged for you to check.
What happens to people who are already in Felesh?
Rows that match an existing record are updated, not duplicated. Duplicates inside the file are caught too, and you choose what to match by.
Can I see the result before it is saved?
Yes. The preview shows every row and how many will import. Nothing is saved until you commit.
Will it bring in stages too?
A stage column can be matched for contacts. A value that is not one of your stages starts in your first stage, so check stages after the import. Companies have no stage.
Hand it the work. Keep the decisions.
Hand Felesh the work you've been carrying?14 days free, no card. Everything that needs your call still waits for your yes.