Turtini

Importing existing members from Givebutter or another system

If your members paid dues in another membership system before you moved to Turtini, you can carry them over so they are current members here from day one, including for member ballots. Each imported member counts as current until the paid-through date from your old system, and lapses after that unless they renew on Turtini.

Before you start:
- Export your members as a CSV from Givebutter (or your previous system). One row per member with an email address and a paid-through or expiration date is what matters. Names, phone, membership name and join date are picked up when present.
- Have the membership tiers they should land on set up first (Subscriptions, plan type Membership). A partner bundle cannot receive imported members.
- Only organization admins can import members.

Importing:
1. Open Membership and go to the Import members tab.
2. Choose your CSV file. Columns are matched from the file's headers (for example Email, First Name, Last Name, Phone, Membership, Join Date, Expiration Date). If one is matched wrong or missed, pick the right column by hand.
3. Choose where the members are coming from, and the Turtini tier they join. If your file has a column that says which kind of membership each person holds (for example Type: Individual or Business), map it as "Tier by row" and choose a tier for each of its values; every value must have one, or nothing is imported.
4. Optional: tick "Also keep past members as history" to record people whose membership has lapsed (see below), and set the year tag prefix.
5. Preview. Nothing is written yet. The preview shows, row by row, who will be imported and who will not, and why.
6. Confirm the import. You will get one confirmation when it is done.

What the preview checks:
- Already a member: anyone who already holds a current membership here, whether they joined on Turtini or came in an earlier import, is skipped and never duplicated. The preview says which.
- No paid-through date: skipped. A membership with no end date would never lapse, so it is not created on a guess. If those rows really are paid up, enter one paid-through date for all of them; each such record notes that the date was entered by an admin rather than taken from the file.
- Paid-through date already passed: skipped, unless you chose to keep past members as history. Those people are not current members; they can rejoin on Turtini.
- Unreadable dates and invalid emails are skipped and listed.
- The same email twice: if the name matches, it is the same person and is imported once (with history on, their years are combined on one record). If the names differ, they are two payers sharing an address. Each payment is that payer's own membership, so the first is imported and the second is listed as needing its own email. It is never merged or dropped without telling you.
- A tier with a member cap refuses an import that would overfill it.

Dates are read as written in common export formats, including 2026-10-31, 10/31/2026 and Oct 31, 2026. Numeric dates are read month first. A member paid through October 31 stays current through the end of October 31.

Join dates and ballots:
If the file has a join date, it is kept as the member's start date. If it does not, no start date is recorded rather than an invented one. That member still counts as current and can vote where your rules allow any current member, but a rule that requires members to have joined a number of days before voting opens cannot confirm them; they will see a message saying their start date is not on record.

Past members as history:
With "Also keep past members as history" on, a person whose paid-through date has passed is recorded as a past membership on their tier, with the year it covered. A past membership is ended: it does not make anyone a current member, it cannot vote, it gets no renewal reminders, and no Turtini account is created for it. Someone who was a member in 2025 and renewed in 2026 is one membership, current, with both years kept on it.

Contact tags:
Every person in the file gets a tag on their CRM contact for each year they were a member, such as "DNCL 2025 Member" and "DNCL 2026 Member". The prefix defaults to your organization's name and can be changed for the import. When tiers are chosen by row, each value can also add its own tag, such as "Business Member". Tags are only ever added, so uploading again changes nothing. A tag group (Campaigns) made of these tags reaches current and past members together.

Uploading again is safe:
Each imported member is keyed by their email and the system they came from. Uploading the same file again changes nothing. Uploading a corrected file updates those same records, for example a new paid-through date, instead of creating duplicates.

What an import does not do:
It does not charge anyone, create a subscription, or set up automatic renewal. It records dues that were paid elsewhere. Imported members appear in your Subscriptions member list marked "Imported from" the system they came from, so members who joined on Turtini are always distinguishable from those carried over. Each imported member is also matched to, or added as, a contact in your CRM by email.

Accounts for imported members:
Each current imported member also gets a Turtini account under their email, or is linked to the account they already have, so they can sign in to see their membership and vote without creating a password. Nobody is emailed during the import. When it finishes, choose "Send sign-in emails" to send each member a one-time sign-in link now, or do it later from Membership > Members. See "Member accounts and sign-in emails".