Getting started
Bring your members in: ServTracker or Focus import
If you're coming from ServTracker or Focus, you don't have to reshape a single spreadsheet by hand. NestPoint reads those systems' exports the way they come out, so your people — and the badge numbers already on their cards — cross over intact.
Why this import is its own thing
NestPoint has a friendly Imports wizard for everyday spreadsheets — see Bring your members in: CSV import for that. This article is for the specific case of leaving ServTracker or Focus. Because those exports have a known shape, NestPoint has a purpose-built importer that recognizes their columns on sight, so there's no column-matching to do. It's a one-time migration run by an administrator from the imports area, not the everyday wizard.
What comes across
The importer reads the fields your old system already tracks and lines them up with NestPoint's.
- Names and email
- First and last name come from your export's name columns. Email comes across when it's present and looks like a real address.
- Mailing address
- Street, apartment or building, city, state, and ZIP map from the residential address columns in your export.
- Their Client ID
- Each person's ServTracker or Focus Client ID becomes their stable identity in NestPoint. That's what keeps the second pass — badges — matched to the right people, and it's why the importer never merges two records on a guess.
- Badge numbers
- The number already printed on each member's card carries over in a second pass, so members can scan in on day one without new badges.
Run it in two passes
People first, then badges. The order matters: badges attach to members by Client ID, so the people have to exist before their badge numbers have anywhere to land.
Open the imports area and choose the ServTracker / Focus members import.
This is the workspace-admin imports area, separate from the everyday Imports wizard. If you don't see it, ask whoever set up the workspace to grant admin access or run the import for you.
Upload your export and let NestPoint do a dry run.
A dry run reads every row and shows you exactly what would happen — without saving anything. You'll see how many people would be added, updated, or left unchanged, plus any rows that need a second look.
Read the summary, then commit.
When the numbers look right, commit the import to save it. Now your roster is populated.
Run the badges import the same way.
Upload the file again — this time choosing the ServTracker / Focus badges import — dry run, review, and commit. Each badge number attaches to the member with the matching Client ID.
Rows that need a look
A clean export usually goes through without a hitch, but the importer is deliberately cautious. It flags rather than guesses, and it tells you exactly which row is involved so you can fix the source file and re-run.
- A missing Client ID
- Every row needs one. Without it there's no safe way to tell people apart, so the row is flagged instead of guessed at.
- A blank or zero badge
- In the badges pass, rows with no real badge number are simply skipped — they're people who haven't been issued a card yet.
- The same badge on two people
- A badge number that appears on two different members is a conflict, since one card can't belong to two people. Sort out which person it belongs to in the file, then re-run.
After the import
Your members land with a starting membership level already assigned, so nothing is left in an invalid state. From here you can adjust levels, fill in any details your old system didn't carry, and set up who scans in at the front desk. When you're ready to check people in, Assign scannable badges to members covers cards for anyone who wasn't in the export.