No ongoing sync
The import is one-off. Sync with Google or Microsoft contacts and a LinkedIn API connection are planned, not live.
You bring contacts as CSV, vCard or LinkedIn data export. Peak PRM shows likely duplicates before anything is added.
Dein erster Vorbereitungsschritt
Als Nächstes: The problem: people three times over
Preparation in sight. Your current tool stays until everything is checked.
The same person is in your phone, on LinkedIn and in an old spreadsheet.
Hier beginnenCSV from any tool, vCard from address books and the data export you download from LinkedIn yourself.
Technischer Nachweis offenPeak PRM compares name and e-mail with existing contacts.
Technischer Nachweis offenStep 1 of 4 · File
Sample data · nothing is sentSample file with 6 rows from a LinkedIn data export.
Interactive demo with invented sample data. No account, nothing is saved or sent.
01 / Deine Ausgangsbasis
You bring contacts as CSV, vCard or LinkedIn data export.
02 / Die Zuordnung
Example of a mapping when importing from CSV or vCard. The rows demonstrate the check.
One column or two? Compare order and spelling.
Peak shows duplicate addresses as possible duplicates before the import.
Review long notes first. Leave out what should stay private.
„Notiz gelesen“ bestätigt deine Sichtung. Es bestätigt weder Feldkompatibilität noch einen erfolgreichen Import.
Check columns one by one. Don't just copy names.
Lukas, a recruiter at an executive search firm, uploads his LinkedIn data export. Peak PRM shows 40 likely duplicates with his address book. He merges 35, creates 5 and starts with a clean base. Example with an invented person.
Preparation, test import and adoption stay separate steps.
The import is one-off. Sync with Google or Microsoft contacts and a LinkedIn API connection are planned, not live.
The same person is in your phone, on LinkedIn and in an old spreadsheet. After a blind import you have them three times.
03 / Kontrolliert vorgehen
The same person is in your phone, on LinkedIn and in an old spreadsheet.
CSV from any tool, vCard from address books and the data export you download from LinkedIn yourself.
Peak PRM compares name and e-mail with existing contacts.
The original export and your current routine stay in view.
Try the demo import with sample data. Nothing is uploaded, everything runs in your browser.
Start demo importInteractive demo with invented sample data. No account, nothing is saved or sent.
The checklist holds your selection and every open point.
# Peak PRM — lokale Wechselcheckliste Design-Demo. Keine Daten wurden importiert oder veröffentlicht. ## Vorbereitung - [ ] The problem: people three times over Nachweis: The same person is in your phone, on LinkedIn and in an old spreadsheet. - [ ] Three sources, live Nachweis: CSV from any tool, vCard from address books and the data export you download from LinkedIn yourself. - [ ] Duplicates before import Nachweis: Peak PRM compares name and e-mail with existing contacts. - [ ] Imported means private Nachweis: New contacts start out private. ## Vor einem tatsächlichen Wechsel weiterhin prüfen - No ongoing sync: The import is one-off. Sync with Google or Microsoft contacts and a LinkedIn API connection are planned, not live. - Only what the file contains: LinkedIn exports often lack e-mail addresses. Peak does not fill in missing data from other sources. Abgehakte Punkte sind lokale Selbstauskünfte, keine technische Validierung.
In LinkedIn’s settings under data privacy you can request a copy of your data. You then import the connections file into Peak PRM.
They are not created. The existing contact stays as it is. You can import the file again later.
Not necessarily. A small base of people who truly matter is more useful than thousands of entries you never look after.
Questions about Peak PRM, your account or the offer? This is where to go.