Continuity

Keeping your Glint scores comparable after you switch

Both platforms publish their confidentiality floors, so this comparison is checkable rather than asserted. That is unusual, and it is why the thresholds lead the page.

Trusted by 500+ organizations across 30+ countries
Thresholds

Matching Glint’s confidentiality floors

  • Glint needs three responses for a confidential survey, five for rated items. Your organization chooses the number, and Microsoft notes it might differ for survey items versus comments. Below the threshold, group scores are suppressed.
  • CultureMonkey’s survey floor is three and cannot be set lower. The manager-dashboard default is five, which can be raised but never dropped below three, and it changes by contacting your account manager rather than in a settings screen.
  • Glint applies a separate, higher floor to write-in comments, and we do not. Its default statement reports comments verbatim at ten or more. Glint is stricter, and that changes which comments survive the move rather than which scores do.
Questions

Carrying your question set over

  • Your Glint question wording can be carried over word for word. It is re-created in the survey builder rather than imported in bulk, so someone types each one in and assigns it to a driver as they go.
  • Benchmarks are keyed to drivers rather than to your exact wording. A question you wrote yourself can still roll up to a standard driver. Whether it then appears in benchmark comparisons depends on that mapping, and it is worth confirming for your own question set before the first cycle.
  • A survey uses the standard driver set or your own, never a mix. Custom driver names mean no external comparison pool, so the Benchmark tab does not appear for that survey. Decide before the first cycle.

What to export first

Driver set · survey settings

A survey uses one set or the other, never a mix.

2 modes
SummaryReportQuestionsBenchmark
Standard drivers compare against your industry and employee-size band on the Benchmark tab.
Gaps

What does not travel

  • Past results stay attached to the org structure as it stood then. The hierarchy is a snapshot tied to that survey, so a reorg does not rewrite history. Whether one person’s answers re-attribute on a team move is not documented.
  • Comments can be exported with an English translation column, a gap a Capterra reviewer names on Glint’s side. The column holds a translation where translation is enabled and one exists. A People Analytics Manager names the gap on Glint’s side as a limitation.
  • The anonymised export is aggregated and de-identified, not row-level. Anonymous batches export aggregates. A row-level file exists only as the identified Confidential Report, which is unavailable for anonymous surveys by design.
Trend

Reading a line that spans both platforms

State the scale change on the line

Put the switch date on the chart and label the axis on both sides of it. A trend nobody annotated is the one your leadership questions hardest.

PDF history loads into nothing

One prospect had exactly that. Those files become a manual comparison report and nothing more, so build it once and circulate it as a document.

Compare direction, not absolute numbers

Whether recognition still outranks growth is a question both platforms answer the same way. Whether the score reads 7.8 or 78 is a reporting convention.

Participation

The variable nobody accounts for

  • If people were holding back before, the old score was already distorted. A shift after the move can reflect who felt safe answering rather than any change in engagement, and the two are indistinguishable after the fact.
  • Threshold perception changes behaviour even when the threshold is sound. A reviewer describes colleagues holding back because they believed a manager on a small team could pick out whose survey was whose from voice or writing style.
  • So brief people with the documented numbers, never a recollection. Glint’s confidential minimum is three and its rated default is five. What that review proves is that perception moves participation, not what any floor actually is.

The full Glint migration guide

Still deciding where to go? Our roundup of Glint alternatives compares the field. Everything on this page holds whichever one you pick.

FAQ

Score continuity after Microsoft Viva Glint

The numbers

Thresholds sourced to Microsoft on one side and the Help Center on the other.

Will the number move when you leave Microsoft Viva Glint?
Yes, it can, and suppression thresholds are the reason nobody explains. Glint reports rated items at five by default and write-in comments at ten or more. Change either floor and identical responses produce a different group score. Direction and relative driver standing still carry across.
Will our engagement score drop when we leave Viva Glint?
Not necessarily, but the number can move for reasons unrelated to engagement. Suppression floors, question wording, question count and the reporting scale each change an aggregate. Brief your leadership on the scale change before the first new result rather than after it.
Why do group scores differ on the same responses?
Because the suppression floors differ. Glint suppresses a group that falls below its confidentiality threshold, with three the confidential minimum and five the default for rated items. If your new platform uses a different floor, a different set of groups qualifies to be reported.
Can we keep our existing Glint questions?
You can keep the wording. Questions are re-created in the survey builder rather than imported in bulk, and each one is assigned to a driver as it is added. Questions on standard drivers appear in benchmark comparisons; questions on custom drivers do not.
Can we load our old Glint PDF reports into a new platform?
No. A rendered report is a document, not data. If your only history is PDFs, the practical outcome is a one-off manual comparison report you circulate alongside the first new result. Export the raw and aggregate files while you still have access.
Does a reorg rewrite our historical results?
No. The reporting hierarchy is captured as a snapshot tied to each survey, so past reports stay stable through an org change. Whether one individual's past answers re-attribute after a team move is not documented, so do not plan around either outcome.

Brief your leadership before the first new result.

Bring your current thresholds and your last two Glint reports. We will map what changes arithmetically, what changes because of participation, and what does not change at all.

4.7 / 5 on G2