Solutions
Experience measurement
Track sentiment and KPIs with AI-driven gap analysis
Strategic & foundational discovery
Uncover market whitespace with AI-led foundational studies
Journey & behavioral research
Connect user actions to motivations across the lifecycle
Market & consumer Insights
Understanding markets, audiences, & opportunity
Concept & prototype testing
Test designs and prototypes with rapid feedback
Agents
Design
Structure rigorous studies
Field
Run adaptive studies at scale
Analyze
Get statistical analysis you can trust
Synthesize
Turn results into research reports
Deploy
Panels
Recruit from 300K+ verified participants
Email
Reach external audiences with native deliverability
Web apps and websites
Embed studies in web experiences
Mobile apps
Run studies in iOS and Android apps
Customers
Community
Events
Join curated gatherings shaping the future of research
Blog
Insights on integrating AI into research craft
Book icon
Guides
Ultimate playbooks for enterprise survey research
Pricing
Sign in
Book a demo
Sign in
Book a demo
Guide

Migration Guide: From Alchemer to Sprig

November 18, 2026

By James Villacci

Example H2
Example H3
Example H4
Example H5
Example H6

Introduction

Migrating from Alchemer to Sprig takes six moves: audit which surveys are still fielding, export every response before your Alchemer term ends, map Alchemer’s 43 question types to Sprig’s documented set, rebuild logic without custom scripts, run a bridge study for any tracker, and then cut over.

Last updated November 2026.

What a Migration From Alchemer Actually Involves

An Alchemer migration is three projects running on one calendar: an instrument rebuild, a data archive, and a measurement transition.

Teams often plan only the first, because it’s the visible one, and discover the other two when an executive asks why the satisfaction score dropped in the month the platform changed.

The instrument rebuild covers questions, logic, branding, translations and distribution. The data archive covers every response you’ve collected, in formats you can still open in five years.

The measurement transition covers any metric you report as a trend, because changing platforms changes how respondents see and answer the same question.

Run these in parallel with separate owners, not as sequential phases. The archive has a hard deadline set by your Alchemer contract. The rebuild has a soft deadline set by your next survey launch. The measurement transition has no deadline at all, which is why it’s typically the one that gets skipped.

Each workstream needs a different owner. A research operations lead typically owns the archive, because it’s an inventory and a contract problem. A survey researcher owns the rebuild. The measurement transition belongs to whoever presents the trended number, because that person will have to explain any break.

This is Sprig’s independent guide. It isn’t affiliated with, endorsed by or produced in partnership with Alchemer. If you’re still deciding, the Sprig vs. Alchemer comparison guide covers that choice.

This guide assumes the decision is made and covers the work: what moves, what breaks, what can’t be recovered afterwards, and how to prove your numbers survived the move.

Decision rule: if any survey you’re moving feeds a number someone reports as a trend, the migration has three workstreams, not one. Assign an owner to each before you export anything.

What Does Not Port From Alchemer

Several Alchemer question types, survey flow constructs and operational settings have no documented equivalent in Sprig. The table below lists each one with what to do instead.

"Not documented" means the capability is absent from published documentation, not that it’s proven impossible, so ask your vendor contact before you redesign a study around its absence. "Partial" means an equivalent exists with a restriction named in the row.


| What you have in Alchemer | Does it port | What you do instead | Source |
|:---:|:---:|:---:|:---:|
| Continuous Sum | Not documented | Rebuild as Rank Order plus a separate importance rating, or move the study to MaxDiff | Alchemer Question Types and Sprig Questions docs |
| Image Heatmap | Not documented | Use an image-based multiple choice with labeled regions, or a Recorded Task on a prototype | Alchemer Question Types and Sprig Questions docs |
| Text Highlighter | Not documented | Split the passage into labeled phrases as multiple choice, then add an open text question | Alchemer Question Types and Sprig Questions docs |
| Grouping (open and closed card sort), Quick Sort | Not documented | Keep card sorting in a dedicated card-sort tool, or use a matrix with categories as columns | Alchemer Question Types and Sprig Questions docs |
| Cascading Dropdown | Not documented | Chain single-select questions with display logic and response piping | Alchemer Question Types and Sprig changelog |
| Signature | Not documented | Use Consent/Legal with name collection, and confirm with legal that it meets your requirement | Alchemer Question Types and Sprig AI File Upload docs |
| Semantic Differential | Partial | Use a matrix or rating scales with bipolar endpoint labels | Sprig Questions docs |
| Video Sentiment and Audio Sentiment | Partial | Use Video and Voice responses with AI theming, not available in HIPAA environments | Sprig Questions docs |
| Custom Group and Custom Table | Not documented | Use Multi-Question: Single Page, Surveys only | Sprig Questions docs |
| Conjoint and Max Diff | Partial | Enterprise plan only. Conjoint runs in link surveys, MaxDiff in standard-format Surveys | Sprig Questions docs |
| File Upload | Partial | Enterprise only, link Surveys and web In-Product Surveys, not mobile In-Product Surveys or video files | Sprig Questions docs |
| Lua Custom Script and JavaScript actions | Not documented | Rebuild with skip logic, display logic and piping, or move the calculation downstream | Alchemer Scripting docs |
| Webhook action pulling data mid-survey | Not documented | Pass the data in before the survey as user attributes or URL parameters | Alchemer Actions docs and Sprig changelog |
| Percent Branch (A/B split) | Partial | Randomize pages, then confirm the split in a test export | Alchemer Actions docs and Sprig changelog |
| Link-based and distributed logic quotas | Partial | Enterprise response-based quotas on single-select, rating scale or NPS screeners | Alchemer Quotas docs and Sprig Quotas docs |
| Login/Password and Payment actions | Not documented | Target authenticated users in-product or by email with user IDs, and keep payment outside the survey | Alchemer Actions docs |
| Historical responses | Not documented as importable | Archive in Alchemer's export formats before the term ends | Sprig Export docs |
| EU, Canada or Australia data center | No | Sprig hosts on AWS in the United States. See who should not migrate | Alchemer International docs and Sprig Security page |
| Snowflake push and pull | Not documented | Use CSV export, the Export API, webhooks or Segment Streams | Alchemer Snowflake docs and Sprig Data Destinations docs |
| SPSS .sav export and TURF report | Not documented | Export CSV, rebuild value labels from the codebook, and run TURF in your statistics package | Alchemer Exports and TURF docs and Sprig Export docs |

Why Survey Flow Breaks Before Question Types

The question types are generally the easiest category to plan for, because you can see them on the page. Survey flow constructs are commonly harder.

A Lua script that recodes an answer before a branch doesn’t show up in a question inventory, and it’s where hidden behavior lives.

Don’t audit questions alone. Open every action on every page of every survey you plan to move. Alchemer’s own action list includes Webhook, URL Redirect, Percent Branch, Login/Password, Payment, Custom Script and JavaScript, and each one is a place hidden behavior lives. A Login/Password page, for example, usually becomes an in-product survey shown only to signed-in users, or an email survey tied to user IDs.

The operational rows matter for a different reason. Residency and warehouse connectors aren’t survey features, but they’re often contractual or architectural commitments someone else in your company made.

Decision rule: if any "Not documented" row sits on a survey’s critical path, rebuild that survey last, after the simpler ones have proven the process.

Who Should Not Migrate From Alchemer

Some teams shouldn’t migrate from Alchemer to Sprig right now, and the guide would be doing them a disservice to pretend otherwise. If any of the conditions below describes a core program rather than an edge case, stop and resolve it before signing anything.

Teams with a data residency requirement outside the United States shouldn’t migrate. Alchemer runs separate data centers in the US, the EU (Frankfurt), Canada (Montreal) and Australia.

Sprig hosts its software on AWS facilities in the USA and publishes no regional hosting option. For a public-sector body in Canada or a European team under a residency clause, that’s disqualifying rather than inconvenient. Moving those programs would also move respondent data out of the jurisdiction your privacy notices describe, which is a legal change before it’s a research one.

Teams whose instruments depend on scripting shouldn’t migrate without a rebuild budget. Alchemer documents Lua custom scripting for Full Access licenses and select Enterprise plans, plus JavaScript actions.

If your survey calculates eligibility, scores a quiz or rewrites answers in a script, that logic has to be redesigned rather than copied.

Teams that pull live data into a survey mid-response shouldn’t migrate yet. Alchemer’s Webhook action and Snowflake integration can look up a record and return it to the survey while the respondent is on the page.

Sprig documents no mid-response lookup. Its documented routes load the data before the survey, as user attributes sent through the API, a CSV upload or data sources such as Census and RudderStack.

Teams whose core method is a specialist question type should pause. Card sorting, image heatmaps, continuous sum allocation and text highlighting are genuine Alchemer capabilities with no documented replacement.

Teams that deliver SPSS files to an external analyst every wave should plan the conversion work first. An agency contract that specifies .sav deliverables is a commitment Sprig’s CSV export doesn’t meet on its own, so either renegotiate the deliverable or budget the labeling work for every wave. CSV is the documented export, so somebody has to own value labels.

Teams in the middle of a tracker wave should wait for the wave to close. Moving an instrument while a wave is fielding splits one measurement period across two platforms, and no bridge study can separate that cleanly afterwards. Start the migration between waves, with the next wave planned as the bridge.

Teams that rely on Enterprise-gated Sprig features without an Enterprise plan should resolve packaging first. MaxDiff, conjoint, rank order, file upload, response-based quotas, single sign-on and the AI File Upload builder are all documented as Enterprise capabilities.

A migration plan built on those features, signed against a different plan, stalls when the first gated feature is missing.

Decision rule: if your answer to any of these is "that’s our main program," keep that program on Alchemer and migrate the rest.

The Pre-Migration Audit

A pre-migration audit is an inventory of every Alchemer survey, its status, its dependencies and its owner, finished before anything is exported. It’s the step teams most commonly shorten, and it’s the one that decides whether the rest of the plan is accurate.

Work through this checklist in order:

  1. List every survey in the Alchemer account, including those owned by people who’ve left the company
  2. Mark which surveys are still fielding, which are scheduled to reopen and which are closed for good
  3. Record every share link, embed and email campaign still pointing at a live survey
  4. Open every page and list each action, script, quota and piped value
  5. Flag every question type that appears in the does-not-port table
  6. Identify each downstream consumer: dashboards, Snowflake tables, CRM fields, scheduled exports
  7. Name the person who owns the Alchemer contract and the clause that sets your end-of-term date
  8. Note the data center your Alchemer account runs in
  9. List each survey’s languages and its translation source files
  10. Assign a migration owner and an approver per survey

Items two, six and seven are the ones nobody checks. A survey that "closed last year" sometimes reopens quarterly from a scheduled campaign. A Snowflake table fed by a response action has consumers who’ve never heard of Alchemer. And the end-of-term date sits in a contract that procurement holds, not the research team.

Rather than auditing in a spreadsheet you’ll throw away, build the audit as the migration tracker itself, with one row per survey and columns for every later phase.

Sorting the Alchemer Inventory

Sort the inventory into three groups: rebuild, archive only, and delete after export. Long-lived Alchemer accounts accumulate test surveys, duplicates made for a single translation and one-off studies that closed years ago, and those belong in the second and third groups.

Decision rule: if a survey has no named owner after the audit, don’t migrate it. Archive it and close it.

Exporting From Alchemer

Exporting from Alchemer means pulling two separate things before your access ends: the responses and the instruments.

Alchemer documents raw data exports to CSV and Excel, SPSS exports in the .sav format with variable names and value labels set up automatically, bulk PDF exports of individual responses, bulk downloads of uploaded files, and delivery to an FTP site.

Export responses in at least two formats. CSV is the format you’ll still be able to open in 10 years. SPSS .sav preserves value labels that a CSV loses.

Those labels matter when the codebook lives nowhere else. If any survey used file upload questions, run the bulk file export too, because those files aren’t in the raw data.

Exporting the Alchemer Questionnaires

Export the instruments separately. Alchemer lets you download a survey as a Word document or PDF, with an option to include the logic.

Turn that option on. The logic printout is the only human-readable record of your branching once the account is closed, and it’s the input for the rebuild.

Alchemer can schedule exports daily, weekly or monthly. For any survey still fielding during the migration window, set a weekly scheduled export so the archive stays current without someone remembering to run it.

Two cautions apply. Exported timestamps follow the account’s time zone setting, so record that setting with the archive. And piped questions often export differently from standard ones, so spot-check a piped column before you trust it.

Teams on Alchemer’s business platform can also pull responses through the API, which Alchemer limits to business platform accounts.

An API pull is useful when you have dozens of surveys to archive, but treat it as a supplement. The CSV and .sav files are the records a future analyst can open without writing code.

Decision rule: if you can’t open an export and reconcile its row count against Alchemer’s response count, it isn’t an archive yet. Re-run it before you move on.

The Historical Data Decision

Your historical Alchemer responses stay where you archive them, because Sprig documents no import of responses collected on another platform. That makes the archive decision permanent, and it’s the one item in this migration with a contractual clock on it.

Alchemer’s cancellation documentation sets the clock. You keep access until the end of your current subscription term.

Deleting the account is immediate and permanent, and "all your data, projects, contacts, and collected responses are deleted." Share links on a deleted or cancelled account return errors.

So the decision isn’t whether to move history into the new platform. It’s where history lives and who can find it. Three workable options:

  • Warehouse: load the CSV exports into the warehouse your analysts already query, keyed by survey and wave
  • Statistics archive: keep the .sav files with their codebook in a governed shared drive
  • Both: the warehouse for analysis, the .sav files as the record of what respondents actually saw

Archive every survey with responses, not only the ones you expect to need, because deleting the Alchemer account removes every collected response.

Write down the archive location in the migration tracker, next to each survey, so the next researcher can find it.

Apply your normal retention policy to the archive. Survey responses often include contact details or free text that names people, so the archive needs the same access controls and deletion schedule as any other customer data, not a shared folder that anyone can open.

Decision rule: if your Alchemer term ends in less than one full export-and-verify cycle, export first and plan later. Every other step can slip, but this one can’t.

Mapping Alchemer Question Types

Most Alchemer question types map to a documented Sprig type, and the ones that don’t are listed in the does-not-port table. The table below covers the common types, with the restriction named on every partial match.


| Alchemer question type | Sprig equivalent | Port status |
|:---:|:---:|:---:|
| Radio Buttons, Dropdown Menu | Multiple Choice Single-Select | Yes |
| Checkboxes | Multiple Choice Multi-Select | Yes |
| Radio Button Grid, Checkbox Grid | Matrix / Accordion | Partial: mobile always shows accordion |
| Textbox, Essay | Open Text | Yes |
| Email, Number, Date, Percent | Validated Text | Partial: no AI follow-ups or AI theming |
| Rating (Likert Scale), Star Rating Grid, Slider | Rating Scale or Matrix | Partial: slider presentation not documented |
| Net Promoter Score | NPS | Yes |
| Drag and Drop Ranking, Ranking Grid | Rank Order | Partial: Enterprise only, drag-and-drop not on Android |
| Image Select | Multiple Choice with images | Partial: Surveys only, no carry forward |
| Max Diff | MaxDiff | Partial: Enterprise only, standard-format Surveys |
| Conjoint (Choice-Based) | Conjoint | Partial: Enterprise only, link surveys |
| Video Feedback | Video and Voice | Partial: not in HIPAA environments |
| Contact Form | Open Text or Validated Text fields | Partial |
| File Upload | File Upload | Partial: Enterprise, link and web in-product only |

The partial matches carry restrictions worth stating plainly. Validated Text, which replaces Alchemer’s Email, Number, Date and Percent fields, doesn’t support AI follow-ups or AI theming. Rank Order is Enterprise only, and its drag-and-drop interaction isn’t available on Android. Image response options work in Surveys only and not with carry forward, and Sprig doesn’t document a slider presentation for rating questions.

Two patterns matter more than any single row. First, several Alchemer types collapse into one Sprig type, so a survey that mixed Radio Buttons and Dropdown Menus for style reasons ends up visually uniform. Second, many partial matches are plan-gated, which turns the mapping exercise into a packaging question.

Rather than mapping question by question, map by instrument. A tracker with one MaxDiff block has an Enterprise dependency the whole tracker inherits.

Grids show why the Partial label matters. An Alchemer Radio Button Grid with eight rows reads as one compact table on a laptop. In Sprig, the same matrix always displays as an accordion on mobile, one row at a time.

Respondents who see one row at a time often answer differently from those who see the whole grid, so a grid in a tracker belongs in the bridge study.

Decision rule: if a survey’s mapping includes a Partial row with a plan restriction, confirm the plan before rebuilding that survey.

Rebuilding Logic and Survey Flow

Rebuild logic from the Word or PDF logic printout, not from memory. Sprig supports skip logic, display logic, response piping, attribute piping, carry forward and randomization of options, questions and pages, which covers most of what an Alchemer survey does without scripts.

Translate each Alchemer construct deliberately:

  • Page and question logic: rebuild as skip logic or display logic
  • Piping: rebuild as response piping, or as attribute piping when the value came from a URL variable
  • Percent Branch: rebuild as page randomization, then check the split in a test export
  • Hidden values and URL variables: pass them as user attributes or URL parameters
  • Custom Script and JavaScript: redesign, because there’s no documented scripting layer

Scripts are typically where rebuilds slip. Rather than reproducing a script’s mechanics, write down what it decided and rebuild that decision. A script that set a segment flag from three answers often becomes a display condition on those three answers.

Skip logic options differ by question type. Multi-select skip logic, for example, supports four conditions, and when more than one is true the respondent goes to a randomly selected destination. Test any multi-select branch with overlapping answers.

A worked example makes the pattern concrete. Suppose an Alchemer onboarding survey ran a Lua script that set a variable to "power user" when a respondent chose daily usage and three or more features, then showed a page of advanced questions.

The rebuild needs no script: a display condition on the advanced page that checks both answers does the same job, and it’s visible to the next researcher.

Decision rule: if you can’t describe what a script decided in one sentence, don’t rebuild it until its owner can.

Rebuilding the Instrument in Sprig

The fastest documented route into Sprig for an existing Alchemer survey is the AI File Upload builder, which builds a study from a PDF or Word file of up to 25 MB. That’s why exporting the questionnaire as a Word document matters.

The builder imports these question types:

  • Multiple choice, single and multi-select
  • Rating scale and NPS
  • Rank order and matrix
  • Open text
  • Text/URL messages
  • Video and voice
  • AI Dynamic Question
  • Consent/Legal

It reads plain-text markers for required questions, skip logic, display logic and response randomization, and it groups questions onto a page when the file marks that page’s start and end lines. It doesn’t import MaxDiff questions or prototype links, which you add by hand. The builder is available on Enterprise plans.

The Alchemer logic printout generally won’t match the builder’s marker format exactly, so expect a cleanup pass on the file before upload rather than after. One instrument through the builder, reviewed line by line, teaches you the cleanup rules for the rest.

In Sprig: the Design Agent reviews a draft for broken or conflicting logic and unclear questions before launch. It doesn’t know what your Alchemer script used to do, so the logic check catches contradictions, not missing intent. Researchers remain responsible for comparing the rebuilt flow against the original printout.

Branding, translations and distribution are the remaining rebuild items. Rebuild branding once as a theme and apply it to every survey, rather than restyling each instrument by hand, because inconsistent styling across waves is one more rendering change a tracker frequently picks up.

Alchemer translates surveys into more than 200 languages. Sprig’s multi-language docs describe a translation file you download, fill in and upload, with only the Next and Finish buttons and thank-you text auto-translated into 10 languages. Budget translation work for each language before you promise a launch date.

Decision rule: if the rebuilt survey hasn’t been tested on every path in the logic printout, it isn’t rebuilt.

The Measurement Discontinuity

Changing survey platforms commonly changes the numbers, even when the questions are identical. A move from Alchemer changes the rendering of each question, the device experience, the invitation, often the distribution channel and sometimes the sampling frame, all at once.

The tracked metric moves, and the movement isn’t a change in customer sentiment. Reporting it as one publishes an artifact as a finding.

Selection Effects and Measurement Effects

Two different things move a tracked number when the platform changes. A selection effect changes who answers: an email survey sent from a new domain typically reaches a different slice of customers than an Alchemer link embedded in a help center did.

A measurement effect changes how the same people answer: a slider becomes a rating scale, a grid becomes an accordion on mobile, and responses shift.

Separating the two requires a comparable dataset collected alongside, not a judgment call afterwards. Once the old platform is switched off, the two effects are confounded permanently.

What the Mode-Effect Research Shows

The best-documented example comes from Pew Research Center. In 2014 it randomly assigned 3,003 members of its American Trends Panel to answer the same 60 questions either by phone or on the web. The mean difference between modes was 5.5 percentage points, and individual items differed by as much as 18 points, with the largest gaps on satisfaction and sensitive items.

Pew’s report is candid about the limit of that finding: for most items, there’s no way to determine which mode produced the more accurate answer.

That’s the honest caveat for any migration. A bridge study tells you the size of the shift, not which platform was right.

The House Effect

Even with the same questions and the same population, a different fielding organization can produce a different number. Tom W. Smith’s 1978 study in Public Opinion Quarterly compared identical questions asked by different survey organizations and found significant differences in 10 of 33 comparisons fielded within five months of each other.

Smith concluded house effects weren’t a large systemic problem, but that they do occur. A platform change is a house change in miniature.

How Large Organizations Handled a Transition

Two precedents show what careful practice looks like. The US Bureau of Labor Statistics redesigned the Current Population Survey in 1994 and ran a parallel survey of 12,000 households from July 1992 through December 1993 first.

The parallel data indicated the 1993 unemployment rate would have been 0.5 percentage point higher under the new method, a shift large enough to read as an economic event.

Pew Research Center’s own move from phone to online polling is the second. Pew assessed each question’s risk of a mode effect and chose one of three treatments: break the trend, connect it but flag the mode change with a footnote and a dotted line, or connect it with less emphasis once several years of online data showed a small effect.

Pew also runs a phone poll alongside an online one when feasible to measure the shift directly.

The Commercial Tension

The methodologically correct answer is to run both platforms concurrently for at least one measurement cycle. You’re migrating partly to stop paying for and operating two platforms.

Both statements are true, and no published source gives a general rule for how long an overlap should last.

What the precedents give you is a procedure: decide per metric whether to bridge, break or flag, and only pay for an overlap on the metrics someone actually reports as a trend.

The generic version of this problem is covered in the guide How to Switch Survey Platforms Without Breaking Your Trend Data. This section is the Alchemer-specific application.

What This Means for an Alchemer Tracker

For a typical Alchemer tracker, the exposure is concentrated in a few places. Sliders, star rating grids and image selects render differently in Sprig, grids become accordions on mobile, and a link survey moved in-product typically reaches a different population.

Each of those is a measurement or selection change, and each is a reason to bridge rather than assume continuity.

Decision rule: if a metric is reported to executives as a trend, it gets a bridge study or an explicit, footnoted break. It never gets silence.

Designing the Bridge Study

A bridge study runs the old and new instruments side by side on comparable samples so you can measure the shift a migration introduces. It’s the only way to tell a real change from a platform artifact, and it needs only a small spec.

Use this spec for each tracked metric:

  • What runs in parallel: the Alchemer instrument and the rebuilt instrument, in the same field window
  • What’s held constant: question wording, response scale, invitation timing, eligibility rules and the reporting period
  • How respondents are split: at random from one eligible pool, so selection effects cancel
  • What gets compared: the headline metric, its distribution, completion rate and item nonresponse
  • What licenses continuity: a difference small enough that you’d treat it as noise in any other wave, judged against your own historical wave-to-wave variation

The last line is deliberately not a fixed threshold. Your tracker’s normal variation is the right benchmark, and it’s already in the archive.

Rather than bridging every question, bridge the headline metrics and the items that typically move most with rendering changes: grids, sliders and anything with images.

Here’s how the spec works for a quarterly customer satisfaction tracker. In the bridge quarter, split the eligible customer list at random, send half the Alchemer survey and half the rebuilt survey on the same day, and compare the satisfaction score, its distribution and completion rates.

If the gap sits inside the tracker’s usual quarter-to-quarter movement, connect the series with a footnote. If it doesn’t, start a new series.

Decision rule: if the bridge shows a shift larger than your normal wave-to-wave movement, start a new series or connect it with a flagged break, the way Pew did.

Users, Roles, SSO and Provisioning

Single sign-on (SSO) carries over in principle, because both platforms use SAML 2.0, but provisioning works differently. Alchemer offers SAML SSO to its business platform customers and can create users just in time at first login. It doesn’t document SCIM.

Sprig supports SAML 2.0 SSO on Enterprise plans, with setup guides for Auth0, Google Workspace, KeyCloak, Microsoft Entra ID, Okta and OneLogin. Its changelog announced SCIM provisioning on October 23, 2026, and SSO has to be turned on first. Confirm SCIM availability on your plan before you design user lifecycle around it.

Roles generally don’t map one to one. List each Alchemer role and license type in use, then map people to Sprig’s roles by what they do, not by their old title.

Use the migration to clean up access. Alchemer accounts often carry users who left, shared logins for agencies and licenses assigned to people who only view reports.

Rather than recreating that list, invite people as they join a migration wave, so the new user base reflects who actually works on surveys.

Decision rule: if your identity team requires automated deprovisioning, confirm SCIM before the cutover date, not after.

Integrations and Downstream Data

Every downstream consumer of Alchemer data needs a new source before cutover, and the audit’s consumer list is your checklist. Alchemer documents integrations through actions and its Snowflake connector, which pushes response rows into Snowflake and pulls rows back into a live survey.

Sprig documents CSV export and an Export API. Its documented data destinations are Amplitude, Segment Streams, Slack, Mixpanel, Webhooks and Zapier.

It doesn’t document a Snowflake or BigQuery connector. A warehouse table that Alchemer filled directly has to be refilled through the Export API, a webhook or Segment.

Rebuild each pipe and point its consumers at the new table before the old one goes stale. Keep the old table read-only with a note naming the date it stopped updating.

Map each Alchemer response action to its nearest Sprig equivalent. A Salesforce or HubSpot push typically becomes a webhook or Zapier step. A Slack alert typically becomes the Slack destination.

A Google Spreadsheet action becomes a scheduled CSV export or a Zapier step. Test each one with a dummy response before the survey goes live.

Decision rule: if a dashboard still reads from an Alchemer-fed table on cutover day, cutover isn’t complete.

The Parallel Run

The parallel run is the operational overlap in which both platforms field live surveys while the new one proves itself.

It’s different from the bridge study, which is a measurement design. The parallel run asks whether the new setup works: invitations send, logic routes correctly, responses land in the right tables.

Sequence the migration plan by dependency, not by calendar:

  1. Archive: export and verify every survey, owned by the research operations lead
  2. Pilot: rebuild one low-risk survey with no tracked metric, owned by one researcher
  3. Pipes: rebuild integrations for the pilot survey, owned by the data team
  4. Wave one: rebuild surveys with no scripts and no does-not-port rows
  5. Bridge: run bridge studies for tracked metrics, owned by the measurement owner
  6. Wave two: rebuild scripted and complex surveys
  7. Cutover: close Alchemer surveys and switch links, owned by the program lead

Each phase starts only when the one it depends on has been approved. Staff the pilot with the people who will own the rebuild and the pipes, and bring the wider team in at wave one, when the cleanup rules and integration pattern are written down and repeatable.

The pilot exists to find your cleanup rules for the AI File Upload builder and your integration pattern before the important surveys depend on them.

No published source supports a standard duration for a parallel run, so don’t plan one from a rule of thumb. Plan it from your own survey cadence: the overlap should cover at least one full fielding cycle of each survey type you’re moving.

Decision rule: if the pilot survey needed more than one rebuild pass, add a second pilot before wave one.

Cutover and Decommissioning

Cutover is the day each Alchemer survey stops collecting and its replacement becomes the only live version. Do it survey by survey rather than account-wide, and do it well inside your contract term so the archive can be re-verified with access still open.

For each survey, follow the same order. Close the Alchemer survey. Replace every share link, embed and email campaign with the new distribution. Run one final export and reconcile it against the archive. Then mark the survey as migrated in the tracker.

Remember how Alchemer handles closed accounts. Its documentation says share links on a deleted or cancelled account return 404 errors, so any link you missed will fail in front of a respondent.

Search your website, help center, email templates and product for old Alchemer domains before the term ends.

Delete the Alchemer account only after the last export is verified and the contract owner has signed off. Deletion can’t be undone.

Tell internal stakeholders before cutover, not after. Customer success teams, support agents and product managers often share survey links by hand, and they’ll keep pasting the old link until someone gives them the new one.

Decision rule: if any live page still links to an Alchemer survey, that survey hasn’t been cut over.

Validating the Migration

Validating a migration means proving three things: every response is archived, every rebuilt instrument behaves like the original, and every downstream consumer reads from the new source. Use this checklist per survey:

  • Archived response count matches Alchemer’s response count
  • Archive opens in its intended tool, and value labels match the codebook
  • Every path in the logic printout has been tested in the rebuilt survey
  • Required questions, randomization and quotas behave as specified
  • Each translation renders, including right-to-left languages where you use them
  • Test responses appear in every downstream table and dashboard
  • Bridge study result is recorded, with the continuity decision written down
  • Old share links are replaced or retired
  • Survey owner has signed off

Validate each survey at its own cutover, while the Alchemer original is still open for side-by-side comparison. A defect found in wave one costs one rebuild. The same defect found after wave two costs every rebuild that copied it.

Keep the completed checklist with the archive. A year from now, someone will ask whether the numbers before and after the move are comparable, and the checklist plus the bridge result is the answer.

How to Test Every Logic Path

Test paths systematically rather than by clicking around. Number every branch in the logic printout, write one test persona per branch, and submit one response per persona to the rebuilt survey.

Then export those test responses and confirm each persona reached the pages and questions the printout says it should. Delete the test responses before launch, or mark them for exclusion from analysis.

Decision rule: if a survey fails any line on the checklist, it stays on Alchemer until the line passes.

Where Alchemer Wins

Alchemer is better than Sprig at several specific, checkable things, and a team that’s used it for years already knows them. Naming them here is part of planning the migration honestly, because each one is something your team will either redesign around or keep Alchemer for.

Alchemer’s Question-Type Breadth

Alchemer documents 43 question types. The specialist ones with no full equivalent in Sprig include:

  • Continuous Sum
  • Image Heatmap
  • Text Highlighter
  • Cascading Dropdown
  • Semantic Differential
  • Open and closed card sorts, plus Quick Sort
  • Signature
  • Video and Audio Sentiment

Sprig documents a smaller set. Every specialist type in the does-not-port table is a capability you’re giving up, not just a migration chore.

Alchemer’s Regional Data Residency

Alchemer runs data centers in the US, the EU, Canada and Australia, with separate accounts in each. Sprig hosts in the United States on AWS and publishes no regional option. For readers with a residency requirement, this decides the question.

Alchemer’s Scripting and Live Data Pulls

Alchemer supports Lua custom scripting and JavaScript actions, and its Webhook action and Snowflake integration can pull data into a survey mid-response. That lets an Alchemer survey compute, look up and branch in ways no documented Sprig feature reproduces.

Alchemer’s Analysis and Export Formats

Alchemer documents a TURF report on checkbox and image multi-select questions and a native SPSS .sav export with value labels. Sprig documents CSV export and doesn’t publish a TURF report, its MaxDiff estimation method, weighting or significance testing.

Alchemer’s Packaging and Reviews

Alchemer publishes per-user pricing for three plans and offers a seven-day trial of its Professional plan, which makes it easy to keep a small Alchemer seat for one specialist study.

Alchemer Survey holds a 4.4 out of 5 rating on G2 from 971 reviews, retrieved November 16, 2026.

Alchemer’s Quota Options

Alchemer documents overall quotas, segmented logic quotas, distributed logic quotas that spread responses evenly across many conditions, and link-based quotas that cap each share link.

Sprig documents response-based quotas on single-select, rating scale and NPS screeners, on Enterprise plans. A research team that balances samples across many cells or caps each distribution link has more control on Alchemer today.

Alchemer’s Survey Actions

Alchemer’s action library lets a survey do work while the respondent is still on the page: send an email, redirect with values, take a payment, post to Slack or write to Salesforce and HubSpot.

Many of those become post-response integrations after the move, which is generally fine. But a survey that depended on acting mid-response loses that behavior.

Decision rule: if one of these capabilities carries a program you can’t redesign, keep that program on Alchemer and say so in the migration plan.

Common Mistakes in an Alchemer Migration

The most common Alchemer migration mistakes are generally sequencing errors, not technical ones. They come from treating the move as a rebuild and forgetting the archive and the measurement transition.

  • Exporting late: waiting until the final month of the term, then finding a scheduled campaign that’s still collecting
  • Exporting one format: keeping only CSV and losing the SPSS value labels that were the only codebook
  • Skipping the logic printout: rebuilding branching from memory and missing a script’s side effect
  • Copying a script’s mechanics: reproducing how a script worked rather than what it decided
  • Ignoring plan gating: rebuilding a MaxDiff tracker before confirming the plan that supports it
  • Reporting the platform shift as a finding: showing executives a step change caused by rendering, not by customers
  • Leaving links behind: a help-center embed that returns 404 once the Alchemer account closes

Walk this list against your tracker at the end of the audit and again before each wave, while the Alchemer account is still open.

The last one is the most visible. Respondents don’t see your migration plan, but they do see a broken link.

Decision rule: if your plan has no owner for the archive, the bridge study and link retirement, it has at least three of these mistakes waiting.

How Sprig Supports the Migration

Sprig supports an Alchemer migration at the rebuild, fielding and analysis stages, and leaves the archive and the measurement decision with your team.

The AI File Upload builder turns an exported questionnaire into a draft study, and the Design Agent checks that draft for broken logic and unclear questions before launch.

For distribution, Sprig fields studies through email, shareable links, external panels and in-product surveys for web and mobile apps.

Teams moving an Alchemer link survey can keep it as a link survey, or move a customer satisfaction program in-product, which is a selection change the bridge study needs to account for.

The Field Agent can generate follow-up questions in real time based on responses, and it can be disabled per study.

Turn it off for any tracked question during a bridge study, because a follow-up that appears on one platform and not the other is a measurement difference.

The Synthesize Agent builds a report with themes, summaries and supporting quotes as responses arrive. Researchers remain responsible for validating those themes against the raw responses, especially in the first waves after migration.

Sprig’s limits apply here too. It doesn’t publish its MaxDiff estimation method, weighting approach or significance testing, so a team migrating advanced analysis from Alchemer’s SPSS workflow should keep its statistics package and treat the platform’s reports as a starting point.

Decision rule: if a study is part of a bridge, configure it to match the Alchemer instrument first and add agent features after the continuity decision.

Frequently Asked Questions

How Long Does It Take to Migrate From Alchemer to Sprig?

No published source sets a standard duration for an Alchemer to Sprig migration, so the honest answer depends on your inventory. The overlap has to cover at least one fielding cycle per survey type. An account with trackers, Lua scripts and Snowflake pipes generally takes longer, because each tracker needs a bridge study and each script needs a redesign.

Can I Import My Historical Alchemer Responses Into Sprig?

Sprig doesn’t document an import for responses collected on another platform, so plan to archive your Alchemer history rather than move it.

Export raw data as CSV and SPSS .sav files, export uploaded files in bulk, and download each questionnaire as a Word or PDF file with logic included. Store the archive where your analysts already work.

What Happens to My Alchemer Data When the Contract Ends?

Alchemer’s documentation says you keep access until the end of your current subscription term. It also says deleting the account permanently removes all data, projects, contacts and collected responses.

Share links on a cancelled or deleted account stop working. Export and verify everything before the term ends, and delete the account only after the contract owner approves.

Do Alchemer Custom Scripts Work in Sprig?

Alchemer’s Lua custom scripts and JavaScript actions don’t carry over, because Sprig documents no scripting layer. Rebuild what each script decided using skip logic, display logic, response piping and attribute piping.

Where a script computed a value, compute it before the survey and pass it in as a user attribute, or compute it downstream from the export.

What Are the Sprig Equivalents of Alchemer Question Types?

Most common Alchemer question types have a direct Sprig equivalent. Radio Buttons and Dropdown Menus become Multiple Choice Single-Select, Checkboxes become Multi-Select, Radio Button and Checkbox Grids become Matrix, Textbox and Essay become Open Text, and Net Promoter Score becomes NPS.

Email, Number, Date and Percent fields become Validated Text, without AI follow-ups or AI theming. Ranking becomes Rank Order, and Max Diff and Conjoint map to Sprig’s MaxDiff and Conjoint, all three on Enterprise plans only.

Do I Need Sprig’s Enterprise Plan to Migrate From Alchemer?

You often need Sprig’s Enterprise plan to migrate from Alchemer. Sprig documents MaxDiff, conjoint, rank order, file upload, response-based quotas, single sign-on and the AI File Upload builder as Enterprise capabilities, so an Alchemer instrument that uses any of them inherits that dependency.

Surveys built from multiple choice, rating scale, NPS, open text and skip or display logic map without a documented plan restriction. Confirm your plan before rebuilding a plan-gated survey.

Which Alchemer Question Types Have No Sprig Equivalent?

Continuous Sum, Image Heatmap, Text Highlighter, Cascading Dropdown, Signature, card sorting and Quick Sort have no documented Sprig equivalent.

Several others port partially: MaxDiff, conjoint, rank order and file upload are Enterprise-gated, and grids display as accordions on mobile. The does-not-port table names a replacement for each one.

Can I Keep My Data in the EU or Canada After Migrating?

No documented option keeps your data in the EU or Canada after an Alchemer migration. Sprig hosts on AWS in the United States and publishes no regional hosting option, while Alchemer runs data centers in the US, EU, Canada and Australia.

If a residency clause governs a program, keep that program on Alchemer or resolve the requirement before migrating.

Will My NPS or Satisfaction Trend Change After Migrating?

Your tracked numbers will often shift after an Alchemer migration, even with identical questions, because rendering, device experience and invitations change too.

Pew Research Center found a mean 5.5-point difference across 60 questions when only the interview mode changed. Run a bridge study, fielding the old and new surveys side by side on randomly split samples, on every metric you report as a trend, then connect, break or flag the series.

Does Sprig Support Quotas Like Alchemer?

Sprig supports response-based quotas on Enterprise plans, set on screener questions of the single-select, rating scale and NPS types. Alchemer offers overall, segmented, distributed logic and link-based quotas.

Map each Alchemer quota to a screener-based quota, and redesign any link-based or distributed quota that has no screener behind it.

Can I Move My Alchemer Users and SSO Setup?

You can reconnect your identity provider, but users and settings don’t transfer. Both platforms use SAML 2.0 for single sign-on.

Alchemer can create users just in time at login, while Sprig’s changelog announced SCIM provisioning on October 23, 2026, with SSO as a prerequisite. Confirm SCIM on your plan and remap roles by what people do.

How Do I Rebuild an Alchemer Survey Quickly?

Download the Alchemer survey as a Word document with logic included, clean it into the AI File Upload builder’s marker format, and upload it to build a draft study on an Enterprise plan.

The builder imports most common question types plus skip logic, display logic and randomization. Add MaxDiff questions and prototype links by hand, then test every path.

Should I Run Alchemer and Sprig at the Same Time?

Run both platforms at the same time for any survey that feeds a tracked metric, at least long enough to complete a bridge study. For one-off studies with no trend, there’s no measurement reason to overlap. The overlap costs money and operational effort, so limit it to the metrics someone actually reports as trends.

What Should I Export From Alchemer Before Cancelling?

Before cancelling Alchemer, export raw responses as CSV, the same responses as SPSS .sav files with value labels, uploaded files in bulk, individual responses as PDFs where you need a respondent-level record, and every questionnaire as a Word or PDF file with logic included.

Record the account’s time zone and data center with the archive, then reconcile each export’s row count.

Should I Migrate My Alchemer Snowflake Pipelines?

Snowflake pipelines have to be rebuilt rather than migrated, because Sprig doesn’t document a Snowflake or BigQuery connector. Refill warehouse tables through the Export API, webhooks or Segment Streams, then repoint dashboards.

Any survey that pulls Snowflake rows into a live response needs a redesign that syncs the data into Sprig as user attributes before fielding, for example through the Census integration, which syncs warehouse data keyed by user ID.

Back to top
Solutions
Experience measurementStrategic & foundational discoveryJourney & behavioral researchMarket & consumer insightsConcept & prototype testing
Agents
DesignFieldAnalyzeSynthesize
Deploy
PanelsEmailWeb apps and websitesMobile app
Pricing
Community
EventsBlogGuides
CustomersIntegrationsCompare
Company
About usCareersService agreementPrivacy policyData addendumSystem status
Socials
LinkedInX