How long do we have to request our data from PeopleGrove?

PeopleGrove's public terms, section 11.6(c), say the customer must request the return of its data in writing within 30 days after the agreement ends. After that window, PeopleGrove has no obligation to keep the data. Your signed order form may differ, so check it and send the request early.

When do we need to give PeopleGrove notice?

Under section 11.2 of the public terms, the agreement renews automatically unless written notice of non-renewal is given at least 90 days before the end of the term. Section 11.1 says neither party may terminate for convenience during the term. Check your own signed agreement for its dates.

Can we export mentoring matches and conversations from PeopleGrove?

An export for mentoring matches and conversations is not publicly documented, and the PeopleGrove support center needs an admin login. Ask your PeopleGrove account manager for them in your written data request so your school keeps the record.

What PeopleGrove data comes over to Prentus?

Students and alumni, their profile fields and custom fields, and any events and attendance PeopleGrove provides. If your school keeps appointments, notes, employers, jobs, outcomes or resumes in another system, those can come over in the same import.

Who owns our data in PeopleGrove?

Section 7.1 of PeopleGrove's public terms says customer data is the sole property of the customer and its authorized users. Section 7.5 says PeopleGrove owns usage and performance data, including aggregated or de-identified data derived from customer data.

How long does the move take, and what does Prentus charge?

Once Prentus receives your files, students can be live in as little as 24 hours. The one-time import is free for every Prentus customer, and re-runs are handled case by case.

How to Migrate From PeopleGrove to Prentus

To move from PeopleGrove to Prentus, export your user reports from the PeopleGrove Admin Hub, send PeopleGrove a written request for a full data return, and share the files with Prentus. Prentus maps and loads your students, alumni and custom fields, plus career records you keep in other systems.

What does a PeopleGrove to Prentus migration involve? It is a one-time move of your community records out of PeopleGrove and into Prentus. PeopleGrove is a community and mentoring product, so the core export is people. Admins save Explore Users reports in the Admin Hub and export them as CSV, and PeopleGrove admins can create a secure file directory on Amazon S3 to retrieve daily exports. The PeopleGrove support center needs an admin login, and exports of mentoring matches, conversations and events are not publicly documented, so ask your PeopleGrove account manager for them. PeopleGrove's public terms give a customer 30 days after the agreement ends to request its data in writing, and the agreement renews unless notice is given at least 90 days before the end of the term. Prentus maps your files to its structure and loads them, matching students by student ID or email. Students can be live in as little as 24 hours after Prentus receives your files.

This guide is based on PeopleGrove's public terms, its public product pages, a public PeopleGrove training deck and one integration partner's guide, as we read them on October 14, 2026. PeopleGrove's own support articles sit behind an admin login (support login), so several steps below end with a question for your account manager.

Find two dates in your contract first

PeopleGrove publishes its SaaS terms, and they are the clearest data-return language of the five systems in this series (PeopleGrove terms of service). These are the public terms. A signed order form or master agreement may say something different, so check yours.

The notice date. Section 11.2 says the agreement renews automatically unless written notice of non-renewal is given at least 90 days before the end of the term. Section 11.1 says neither party may terminate for convenience during the term.
The data-return window. Section 11.6(c) says the customer must request the return of its data in writing within 30 days after termination or expiration. PeopleGrove then returns it, or destroys it if return is not feasible, and confirms in writing. After those 30 days, PeopleGrove has no obligation to keep the data.
Ownership. Section 7.1 says customer data is the "sole property of Customer and its Authorized Users". Section 7.5 says PeopleGrove owns usage and performance data, including aggregated or de-identified data derived from customer data.

The privacy policy says PeopleGrove keeps data for the period reasonably necessary, and it does not describe returning institution data (PeopleGrove privacy policy). The contract terms above are the ones to plan around.

What you can export from PeopleGrove yourself

Explore Users reports

An integration partner, uConnect, documents the steps in its own setup guide. In the Admin Hub, open Explore Users, filter to the population you want, add columns, save the report, then choose Export Report for a CSV (uConnect guide to integrating with PeopleGrove). That guide lists these columns.

PeopleGrove ID, first and last name, headline, user type and about.
Expertise, majors, industries, current company and current job title.
Optional email, location, education history, work history and custom categories.

The guide also suggests sharing the saved report with all hub admins so it survives staff changes. It is a third-party document, so check the steps against your own Admin Hub.

Daily exports to secure file storage

A public PeopleGrove training deck from December 2021 says "PeopleGrove Admins can generate a secure file directory hosted by Amazon S3" that can be used to share files, upload daily batch imports or retrieve daily exports. The same deck shows the data tools work at the hub level, so a school with several hubs plans its exports hub by hub (PeopleGrove Import Tool Training). The current steps to set up an export job are in a gated support article. Ask your account manager to walk you through them.

API and Salesforce sync

PeopleGrove has a support article titled "API and Webhook Documentation", named in the same training deck, but it needs an admin login. Authentication, endpoints and rate limits are not public, so ask your account manager. PeopleGrove also markets a two-way Salesforce sync, and its 2022 overview says sync history shows the object, keys and success or failure counts (Salesforce Integration Overview). If your school uses it, ask your account manager which objects it covers.

What to ask your PeopleGrove account manager for

Send one written request that covers everything below. If the term has already ended, send it inside the 30-day window.

A full data return. Ask for all customer data, across every hub, with custom fields.
Mentoring matches and conversations. PeopleGrove reports cover mentoring and career conversations (CASE reporting with PeopleGrove), but no export of the matches and messages is documented. Ask your account manager for them so your school keeps the record.
Events and attendance. An event export is not publicly documented. Ask your account manager.
Export job steps and the API specification. Ask your account manager for both if your team wants to pull the data itself.
Help articles. Download the admin articles you rely on while you still have access.

Things to plan for

Career records may live elsewhere. PeopleGrove's product pages describe community, mentoring and experiential learning tools. We did not find appointments, jobs, applications, resumes or first-destination outcomes there (PeopleGrove). If your school keeps those in another system, export them from there. They can come over in the same Prentus import.
Private and unapproved users. Users can be set to private, and Explore Users filters depend on approval and visibility status (training deck, uConnect guide). Include every status in your report so nobody is missed.
Several hubs, several exports. Run each report and export job once per hub, then send the set together.

Plan your move

Plan your PeopleGrove request with us

Book a demo and we will go through your contract dates, the reports to run, and how your community lands in Prentus.

Book a Demo Get a Free Outcomes Scan

What moves from PeopleGrove to Prentus

Everything in this table can come over. Where PeopleGrove documents no export, the middle column says so.

What moves from PeopleGrove to Prentus, how to export each object, and what Prentus does with it
What moves	How you export it from PeopleGrove	What Prentus does with it
Students and alumni	Explore Users report to CSV, every user type and status	Matched by student ID or email, then loaded as student and alumni records
Profile and custom fields	Columns and custom categories added to the Explore Users report	Mapped to Prentus fields
Events and attendance	Not publicly documented. Ask your account manager	Loaded as events with attendance
Appointments, notes, employers, jobs, outcomes and resumes	Exported from whichever system your school keeps them in	Loaded alongside your PeopleGrove records

Step-by-step plan

Read your contract. Find the end date, the 90-day notice date and the 30-day data-return window.
Export your users. Build an Explore Users report with every user type, every column and every status, then export CSV. Repeat for each hub.
Send the written request. Ask your account manager for a full data return, including mentoring matches, conversations and events.
Gather career records from other systems. Export appointments, employers, jobs and outcomes wherever they live.
Share the files with Prentus. Use whatever transfer method suits your team.
Prentus maps and loads. Students are matched by student ID or email. Your team approves any transfers from existing Prentus accounts.
Review, sign off and invite students. Students can be live in as little as 24 hours after Prentus receives your files.

What Prentus does on its side

Your team exports what it can, or asks the PeopleGrove account manager for a full export, and signs off on the result. Prentus maps the data to its structure and loads it.

Any format. Prentus accepts what your export produces, including CSV, XLSX and ZIP files of documents.
Student matching. Students are matched by your student ID when you have one, otherwise by email.
Existing Prentus users. Students who already have a Prentus account move into your community through a transfer queue that your team approves.
File handling. Share the files however you like. Prentus stores them once and deletes them after the import.
Timing. From the time Prentus receives your files, students can be live in as little as 24 hours.
Cost. The one-time import is free for every customer. Re-runs are handled case by case.
Your own pull. Teams that prefer to do the work themselves can use the Prentus APIs. See Prentus integrations.

The import is one part of a wider rollout. See how Prentus works with your team. If you are weighing what to run next, read our ranking of career readiness platforms for universities and our guide to AI career advising tools for understaffed teams.

Moving from a different system

Sources

All sources read October 14, 2026.

PeopleGrove is a trademark of its owner. This guide describes public documentation and is not affiliated with or endorsed by PeopleGrove.