Migrating from GroupKit to SAGA

GroupKit is winding down — your group doesn't have to. Everything you collected about your members (their names, emails, and the answers they gave to your approval questions) can move into SAGA in about ten minutes. This is the whole process, step by step.

GroupKit → SAGA

Export from GroupKit, import into SAGA, and keep working the same members — now with a full CRM: pipelines, mailing lists, notes and your team on the same contacts.

📦 What you will need

• Your GroupKit export — a CSV file of your group members (Step 1).

• A SAGA account. The free trial is plenty to start.

• About ten minutes.

1️⃣ Export your data from GroupKit

1. Log in to your GroupKit account and open the group you want to move.

2. Use the Export / Download option to save your member list as a CSV file.

3. Open the file once to sanity-check it: you should see a header row, then one row per member.

2️⃣ Get your CSV ready for SAGA

SAGA's importer is flexible, but it needs headers it can read. In Excel, Google Sheets or OpenOffice Calc:

1. Make sure the first row is the header — First Name, Last Name, Email, Mobile Phone, and so on.

2. Delete anything that sits above that header row.

3. Save the file as a .csv (the upload limit is 10 MB).

Need the exact column names? Grab the ready-made template and the full field guide: Import CSV Contacts →

3️⃣ Import your members into SAGA

1. Contacts → Import — open your Contacts page and click Import.

2. Choose Upload CSV File and select the CSV you exported from GroupKit.

3. Map your fields — check what SAGA matched automatically (for example email), map the rest, and set any column you do not need to IGNORE.

4. Assign extra info — add the label GroupKit so your old group stays a clean segment, and optionally a membership or a step.

5. Check the recap — you will see the contacts ready to import, any that are missing information, and any that will be skipped for a missing name. Remove whoever you do not want, then confirm.

The import summary tells you how many members landed in SAGA. Note that if a contact already exists in SAGA, the imported information overwrites it.

4️⃣ Make SAGA feel like home

• Your group is now a segment: filter Contacts by the GroupKit label whenever you want to work that list.

• Keep the context: the answers from your approval questions can stay in the file as extra columns — during the mapping step you decide column by column what comes across.

• Email them from SAGA: build a mailing list or a broadcast, so you can drop the separate autoresponder. Email Broadcast and Mailing List →

• Bring your team: invite the moderators who helped you run the group so everyone works the same contacts.

🛠️ If something does not look right

• Members were skipped: the importer skips rows with no name. Add a First and Last name, then import that file again.

• Columns landed in the wrong field: set that column to IGNORE on the mapping screen, map it to the right field, and run the import again.

• Duplicates: re-importing a contact updates the existing record instead of creating a second one.

• Columns you do not need: set them to IGNORE — they simply will not be imported.

💬 Stuck? Let us do it together

Migration should not cost you a single member. If you get stuck at any point — exporting, formatting, mapping, or bringing your team across — grab a call and we will take it from there.

Book your free migration call →

💬 Need Help?

• Support Centre: start a chat with the Fibi AI Agent inside your SAGA. If they cannot help, a human team member takes over.

• Book a Call: Speak with our onboarding team