Introduction
To migrate from Forsta to Sprig, confirm which Forsta product you run, audit what’s still fielding, export every study before your contract’s deletion clock runs out, rebuild instruments from the questionnaire rather than the script, and run a bridge study for every tracker. Some things won’t port: phone and in-person interviewing, loops, several specialist question types and non-US hosting. This guide names each one and the workaround.
Last updated November 2026.
What a Migration Actually Involves
A Forsta migration is five decisions and four projects. The decisions come first because each one changes the size of a project, and a team that starts rebuilding before deciding usually rebuilds the wrong things.
The Five Decisions
The five decisions are which studies move, which studies retire, where the response history lives, which trackers need a bridge study, and when the Forsta contract ends. Each decision has an owner. The last one is a legal date, and the other four are research calls that depend on it.
The Four Projects
Each project has its own owner, failure mode and deadline:
- The instrument rebuild, owned by whoever programs surveys today
- The data archive, owned by whoever owns the warehouse or the analysis files
- The measurement bridge, owned by the researcher who reports the tracked numbers
- The access and integration cutover, owned by IT and the systems owners downstream
Treating the four as one project is the most common way a migration slips. The rebuild looks like the whole job because it’s the visible part, so the archive starts late and the bridge study never starts at all.
Which Forsta You Run Changes the Work
Forsta isn’t one survey product. Its survey work runs on two platforms: Forsta Plus, the platform with Confirmit heritage that’s scripted in JScript .NET or JavaScript, and Decipher, the platform with FocusVision heritage that’s programmed in XML with Python. Some organizations run both, often because two research teams came from two acquisitions.
The difference matters for every chapter below. Forsta Plus programs commonly carry 3D Grids, script nodes and computer-assisted telephone interviewing (CATI). Decipher programs commonly carry dynamic question elements, Python exec blocks and loops. Identify which one each study lives in before you estimate anything.
What Does Not Port
Instruments, history and operations all port partially, and some parts don’t port at all. The table below is the full inventory, one row per item, each with what you do instead. Forsta capability names come from Forsta’s own help centers, and Sprig capability names come from docs.sprig.com, both checked on November 11, 2026.
The Does-Not-Port Inventory
| What you have in Forsta | Does it port | What you do instead | Source |
|:---:|:---:|:---:|:---:|
| 3D Grid (Forsta Plus) | Not documented | Split into one Matrix question per column dimension, or move the third dimension into separate pages | Forsta Plus Objects Overview, Sprig question types |
| Numeric List and constant-sum allocation | Not documented | Rebuild as Rank Order plus a separate weighting question, or move the study to MaxDiff | Forsta Plus Objects Overview, Sprig question types |
| Numeric entry | Partial | Use Validated Text and test that its validation covers your range and decimals | Sprig question types |
| Open Text List | Partial | Use several Open Text questions on one page with Multi-Question Single Page, Surveys only | Sprig question types |
| Date and Date Picker | Not documented | Ask month and year as Multiple Choice, or pass the date as an attribute | Decipher Dynamic Questions, Sprig question types |
| Geolocation | Not documented | Pass region as a user attribute or URL parameter before the survey loads | Forsta Plus Objects Overview, Sprig survey logic |
| Image Upload | Not documented | Use a Video and Voice question if a recording serves, or route uploads to a separate tool | Forsta Plus Objects Overview, Sprig question types |
| Card Sort and Rank Sort | Partial | Use Rank Order, Enterprise plans, In-Product Surveys and Surveys only | Decipher Dynamic Questions, Sprig question types |
| Slider, Slider Decimal and Slider Rating | Partial | Use Rating Scale and treat the change from continuous to discrete points as a measurement change | Decipher Dynamic Questions, Sprig question types |
| Image Map and Text Highlighter | Not documented | Ask about named regions as Multiple Choice, or keep the study on a specialist tool | Decipher Dynamic Questions, Sprig question types |
| Shopping Cart and Media Evaluator | Not documented | Keep these studies on a specialist tool or redesign them as monadic concept tests | Decipher Dynamic Questions, Sprig question types |
| DCM Conjoint | Partial | Use Sprig Conjoint on Enterprise plans and re-specify the design, since estimation output won’t match | Decipher Dynamic Questions, Sprig question types |
| Loops (Decipher loop tag, Forsta Plus loops) | Not documented | Duplicate the block once per item, or use subset randomization to show a random set of blocks | Decipher Loop Tag article, Sprig survey logic |
| Scripted logic in JScript, JavaScript or Python | Does not port | Rebuild as skip logic, display logic and piping, and move computed values into attributes | Forsta Scripting introduction, Sprig survey logic |
| Quotas on any variable | Partial | Use Sprig quotas, Enterprise only, built on screener questions | Sprig quotas documentation |
| Column masks in grids | Not documented | Split the grid or use display logic at the question level | Forsta Scripting introduction, Sprig survey logic |
| Hooks and server-to-server calls | Not documented | Compute the value before the survey and pass it as an attribute | Decipher XML Programming Guides, Sprig survey logic |
| Telephony object and CATI | Does not port | Keep phone fieldwork with a phone vendor, or move the study to self-completion and bridge it | Forsta Plus Objects Overview |
| CAPI offline fieldwork | Does not port | Keep in-person fieldwork with a CAPI vendor | Forsta CAPI introduction |
| Response history | Does not port | Archive SPSS, datamaps and CSV outside both platforms | Sprig export and CSV import documentation |
| Translations | Partial | Regenerate with AI Translations and have a native speaker review each language | Sprig AI Translations documentation |
| Regional hosting (Canada, Germany, Australia) | Does not port | No documented Sprig equivalent: Sprig hosts in the US | Forsta Cloud Schedule, Sprig security standards |
| User provisioning by SCIM | Partial | Create users by SSO or invitation, and use SCIM only for deprovisioning | Sprig SCIM documentation |
| Reportal dashboards | Partial | Rebuild key views as reports and CSV feeds into your BI tool | Forsta Plus overview, Sprig export documentation |
| Quantum, SAS and fixed-width exports | Does not port | Convert Sprig’s CSV in your data-processing tool | Sprig export documentation |
Question Types With No Documented Equivalent
The Forsta Plus types with no documented Sprig equivalent are 3D Grid, Numeric List, Date, Geolocation and Image Upload. The Decipher elements with none are Date Picker, Image Map, Text Highlighter, Shopping Cart and Media Evaluator.
“Not documented” isn’t the same as “not possible.” It means the capability doesn’t appear in Sprig’s published question-type list, so you plan the workaround and ask your Sprig contact to confirm before you depend on it.
Forsta’s own Decipher page claims more than 85 question types, while Decipher’s help center lists 24 dynamic elements. Whatever the exact count, the specialist end of that list has no counterpart in Sprig’s documented set of 15, and pretending otherwise would mislead a reader who uses them weekly.
Workarounds for the Specialist Types
Each specialist type has a workaround, even where no equivalent exists. Split a 3D Grid into one Matrix question per column dimension, and rebuild a Numeric List as Rank Order plus a weighting question or move the study to MaxDiff. Ask a date as month and year in Multiple Choice, or pass it as an attribute. Pass region as an attribute before the survey loads instead of using Geolocation.
For Image Upload, use a Video and Voice question if a recording serves, or route uploads to a separate tool. Image Map, Text Highlighter, Shopping Cart and Media Evaluator studies either stay on a specialist tool or get redesigned as monadic concept tests. Each workaround changes the instrument, so each one belongs in the bridge study if the question is tracked.
Survey Flow Constructs
Survey flow is where enterprise Forsta instruments break. A Decipher program with a loop over 12 brands, a Python exec block that computes a segment and a quota keyed to that segment doesn’t translate into three settings. It translates into a redesign, because Sprig documents no loops and no scripting.
Forsta Plus programs carry the same risk in a different language. Its scripting documentation lists conditions, question masks, column masks in 3D grids and loop filters. It also lists response piping, custom validation and general script nodes. Each one is a line of code in the source and a design decision in the destination.
Partial Ports and Why the Restriction Matters
A partial port is one where the capability exists but with a restriction that may not fit your study. Rank Order exists, but only on Enterprise plans and only in In-Product Surveys and Surveys. Display logic and response piping exist, but only on Enterprise plans. Quotas exist, but only on Enterprise plans and only on screener questions.
The restriction usually matters more than the mapping. A study that relied on a quota built from a scripted segment has no clean quota in the destination, even though "quotas" appears on both feature lists.
Operational Surface
Phone and in-person interviewing, regional hosting, user provisioning, dashboards and legacy export formats all sit outside the survey editor, so they don’t show up in a questionnaire review. Find their owners during the audit rather than during cutover.
Decision rule: If a study depends on any row marked “Does not port,” decide its fate before rebuilding anything else in that study. Rebuilding the parts that port first creates sunk cost that biases the decision.
Who Should Not Migrate
Some Forsta customers shouldn’t migrate to Sprig, and this section tells them directly. The conditions below are disqualifying rather than inconvenient, and each is checkable against published documentation.
Teams That Field by Phone or in Person
If your core trackers run by CATI or by computer-assisted personal interviewing (CAPI), don’t migrate them. Forsta Plus documents both, including offline CAPI on Windows, Android and iOS devices that sync after fieldwork. Sprig documents neither. Moving a phone tracker to a self-administered web survey changes the mode, and the mode change alone can move the numbers, as the measurement section shows.
Teams With a Residency Commitment Outside the US
If your data has to stay in Canada, Germany, Australia or anywhere outside the US, stop here. Forsta’s published Cloud Schedule names Canada-based, Germany-based and Australia-based cloud services. Sprig’s security page states that it uses AWS facilities in the USA, and it names no other region. A written residency commitment can’t be worked around by configuration.
Teams Whose Instruments Are Code
If your most important studies are scripted programs, with Python exec blocks, JScript validation or server-to-server hooks doing real work, the migration is a redesign rather than a rebuild. Some teams should still do it. But a team without the research time to redesign its flagship instruments should keep them on Forsta and move only the simpler studies.
Teams Whose Statisticians Sign Off on Platform Output
If a methodologist currently signs off on significance tests computed inside Forsta, plan where those tests will run before you migrate. Forsta documents a Z-test with an effective base for weighted data and six confidence levels. Sprig’s Analyze Agent page describes t-tests, ANOVA and crosstabs but carries preview and coming-soon labels, and Sprig documents no weighting method.
Teams Running Specialist Instruments Weekly
If shopping-cart simulations, media dial testing or image-map heatmaps are a weekly part of your program, those studies have no documented destination. Keep them on Forsta or a specialist tool, and decide whether running two platforms costs less than losing the instrument.
Teams With Less Time Than the Rebuild Needs
If the contract ends before your flagship trackers can be rebuilt, tested and bridged, don’t migrate them on that contract date. A rushed tracker migration produces the silent step change the measurement section warns about. Rather than racing the clock, negotiate a short extension for the trackers alone, or declare their break in advance and accept a new baseline.
Teams That Run an Owned Panel Community
If your program depends on an owned panel or community that you recruit, profile and manage inside Forsta Plus Professional Panels, the migration has a gap. Sprig documents research panels for reaching external participants and attribute-based targeting of your own users. It doesn’t document an owned-panel management module with profiling, incentives and community features, so plan where that community will live before moving the studies that sample from it.
Who Should Migrate Anyway
Most teams that run web, email and in-product studies, with logic that fits skip logic, display logic and screener quotas, can migrate cleanly. A partial migration is still a migration. Moving the studies that fit and keeping the rest on Forsta for a defined period is a defensible plan.
Decision rule: If two or more of these conditions apply to your flagship studies, a partial migration is likely the right plan. Move the simpler studies, keep the flagship ones where they are, and revisit when either platform’s documentation changes.
The Pre-Migration Audit
The pre-migration audit is an inventory of every Forsta study, its owner, its consumers and its deadline, done before anyone rebuilds anything. It typically takes longer than teams expect, because Forsta instances accumulate years of studies that nobody has closed.
What to Inventory
Inventory studies, not projects. For each study, record the Forsta product it runs in, whether it’s still fielding, its mode and its question types. Then record its logic, quotas, languages, downstream consumers and the person who would notice if it stopped. A study with no one who would notice is a retirement candidate, not a migration candidate.
The Audit Checklist
Work through the checklist in this order:
- List every study fielded since your oldest active tracker’s last methodology change, by Forsta product
- Mark which studies are still fielding and which are archived
- Name an owner for every fielding study, or mark it for retirement
- Record the mode of each study: web, CATI, CAPI or mixed
- Record every question type used, using the names in the inventory table
- Record every loop, script node, exec block and hook
- Record every quota and the variable it’s keyed to
- Record every language each study fields in
- List every downstream consumer: dashboards, data-processing scripts, warehouse tables and recurring decks
- Find the contract clause that sets when Forsta deletes your data
- Name the person who can give notice and the date notice is due
- Mark every tracker that reports a number to executives
The Two Items No One Checks
The two items nobody checks are downstream consumers and the contract clause. Downstream consumers matter because a Quantum or SPSS job that reads a Forsta export every month keeps running on the last file it received, so it reports stale numbers rather than failing. The contract clause matters because it sets the deadline for everything else, and it often sits with procurement rather than research.
What the Contract Says, if It Follows the Template
Forsta’s published Master SaaS Agreement says Forsta will permanently delete client materials no later than 60 business days after the term ends or the agreement terminates. The same agreement says self-service export through the platform is available during the term at no additional cost, while a request for Forsta to return data carries additional fees. Your own agreement may differ, so read it rather than relying on the template.
How to Find What Is Still Fielding
The fastest way to find what’s still fielding is to look at response activity, not study status. A study marked closed can still accept responses through an old link in an email footer or an app intercept. Pull completes by study for at least one full cycle of your slowest tracker, and treat any study with recent completes as active until its owner confirms otherwise.
Tracker Triage
Sort every active tracker into three groups. Group one reports a number to executives and needs a bridge study. Group two reports internally and needs a methods note and a declared break. Group three no longer drives a decision and can retire with an archive. Rather than treating every tracker as group one, ask each owner what decision the number informed in the last year.
One Trap Worth Naming
Studies programmed by an outside data-collection partner on your Forsta instance often have no internal owner and no internal questionnaire document. Find them early. Ask the partner for the source questionnaire and the latest datamap while the relationship and the contract are both still active.
Decision rule: If the audit finds a study with no owner and no downstream consumer, archive its data and retire it. Don’t rebuild it.
Exporting from Forsta
Export everything you might need before notice is given, in formats that don’t require Forsta to read. Rather than exporting only what you plan to analyze, export every study you might ever need to defend, because Forsta’s published agreement deletes client materials after the term ends, so a missing export can’t be recovered.
Forsta Plus Export Formats
Forsta Plus documents 10 export options in its export dialog. The spreadsheet and text options are Excel and delimited text, each with a variant that shows answer codes as labels. The research formats are Forsta Extended Triple-S XML, standard Triple-S XML, SPSS, Quantum, SAS and fixed width.
The dialog also filters by interview status, date range and expression, and it can export only records added or modified since the previous export.
For an archive, export SPSS for analysts and standard Triple-S XML for portability. Triple-S is an open interchange standard, so a Triple-S export remains readable by tools other than Forsta. Keep the Excel export with answer codes as values, since Forsta’s own documentation notes you can’t reimport the labels version.
Decipher Export Formats
Decipher’s data downloads include SPSS in fixed-width and tab-delimited layouts, plus fixed-width, tab, pipe and CSV data files. They also include datamaps in several layouts including a Triple-S datamap, SAS, Excel, and an open-end Excel export with one sheet per field. Decipher can also replace text piping with values in Excel exports, though only for some pipe syntaxes.
For an archive, export SPSS plus the plain datamap, and export open ends separately. The datamap is the part teams most often forget, and without it a fixed-width file is a block of numbers nobody can decode.
Export the Questionnaire Too
Export the programmed questionnaire as well as the data. The data tells you what respondents answered, but the questionnaire tells you what they were asked, in what order and under what conditions. Rather than relying on the script as the record, keep a rendered document of each instrument as respondents saw it, plus the original Word specification if your team wrote one.
Paradata and Metadata
Interview status, timestamps, device information, quota cell assignments and any computed variables are easy to lose. Include them in the export layout explicitly, because default layouts frequently omit system variables. Decipher documents default meta variables, and Forsta Plus filters by interview status, so check which fields each default includes before you rely on it.
Exporting at Scale
A Forsta instance with hundreds of studies needs a scripted export rather than a person clicking through each one. Forsta Plus documents incremental exports, and both platforms publish APIs. Assign the export to someone with API access and a list from the audit, and verify each file opens before the deadline rather than after it.
Open Ends and Verbatims
Open-ended responses need their own export check. Decipher documents a dedicated open-end Excel export with one sheet per field, and fixed-width layouts often truncate or separate long text. Export open ends in a format that keeps full text and the respondent identifier, so coded verbatims can be rejoined to the closed-ended data later.
Coded Data and Coding Frames
If your team coded open ends, export the coding frame along with the coded variables. Keep the frame as a document in the archive, with the date it was last revised and the coder or vendor who applied it.
Sample, Panel and Quota Records
Export the sample and panel records you’re allowed to keep: invitation lists, disposition codes, quota cell assignments and panel profile variables. These records explain who answered, which is half of what a later analyst needs to compare a Forsta wave with a Sprig wave. Check your data protection obligations before exporting any personal data you don’t need.
A Naming Convention for the Archive
Name every exported file with the Forsta product, study identifier, wave, export date and format. A consistent name lets a script verify that every study in the audit has its data file, datamap, questionnaire and methods note, which is faster and more reliable than checking by hand.
Decision rule: If an export hasn’t been opened and checked against its row count, treat it as missing. Re-export it while the contract is still active.
The Historical Data Decision
The historical data decision is where years of Forsta responses will live after cutover. Sprig documents no way to import historical survey responses, so the answer is never "inside Sprig."
What Sprig’s Documentation Shows
Sprig’s CSV import is documented for user attributes and for adding users to manual groups. Its Study API v2 creates draft studies, adds questions and launches them. Its export documentation covers CSV out. None of these documents a way to bring responses in, as of November 11, 2026.
Where the History Should Live
Rather than trying to force the history into a survey platform, put it where your analysts already work: a data warehouse, a BI layer or a governed file store. A warehouse table per tracker, with a source column marking Forsta rows, lets an analyst query both periods in one place once Sprig data starts flowing.
What the Archive Has to Contain
A usable archive holds four things for every study: the response data, the datamap or codebook, the rendered questionnaire and a short methods note. The methods note records the mode, field dates, sample source, quotas and weighting. Without it, the next analyst can read the numbers but can’t defend a comparison against them.
The Archive Is a Privacy Object
Archived responses still contain personal data in many programs, so the archive inherits your retention and deletion obligations. Decide who can read it, how long you keep it and how a deletion request reaches it. A Forsta export sitting on a shared drive is a compliance gap that the migration created.
Recoding History to Match the New Instrument
Where a rebuilt question changed its options or scale, recode the history rather than the new data. Keep the original Forsta variable untouched, and add a harmonized variable that maps old codes onto the new instrument’s codes. Analysts can then compare periods on the harmonized variable while the original stays available for audit.
Who Can Query the Archive
Decide who can query the archive before it’s built. Research analysts typically need read access to the harmonized tables, while raw files with personal data need tighter access. Rather than copying the archive to every team that asks, give them a governed view, so a deletion request only has to reach one place.
Weights Belong in the Archive
If your Forsta trackers were weighted, archive the weights, the targets and the weighting specification with the data. Sprig documents no weighting method, so any weighting of future Sprig waves will happen in your own analysis tools. Keeping the Forsta specification lets you apply the same targets to the new series, which removes one avoidable source of discontinuity.
Decision rule: If a tracker’s history will be compared to future results, it goes into the warehouse with its datamap and methods note. If it won’t be compared, archive it in cold storage and set a deletion date.
Mapping Question Types
Most common Forsta question types map to a documented Sprig type. The specialist ones don’t, and several map only partially because of plan or format restrictions. The table below maps each Forsta type to its nearest documented Sprig type.
The Question-Type Mapping Table
| Forsta type | Nearest Sprig type | Port | Restriction or note |
|:---:|:---:|:---:|:---:|
| Single, Button Select | Multiple Choice Single-Select | Yes | None documented |
| Multi | Multiple Choice Multi-Select | Yes | None documented |
| Grid, Multi Grid, Button Select Grid | Matrix / Accordion | Partial | Check that multi-select grids render as intended |
| Open Text | Open Text | Yes | None documented |
| Open Text List | Open Text on a multi-question page | Partial | Multi-Question Single Page is Surveys only |
| Numeric | Validated Text | Partial | Confirm numeric validation fits your range |
| Ranking, Rank Sort, Card Sort | Rank Order | Partial | Enterprise plans, In-Product Surveys and Surveys only |
| Star Rating, Button Rating, Rating Scale | Rating Scale | Yes | None documented |
| Slider family | Rating Scale | Partial | Continuous input becomes discrete points |
| Info | Text / URL Prompt | Yes | None documented |
| DCM Conjoint | Conjoint | Partial | Enterprise plans, and the format restriction conflicts in Sprig’s docs |
| Net Promoter Score item | NPS | Yes | None documented |
| Consent screen | Consent / Legal | Partial | In-Product Surveys and Surveys only |
| Media testimonial | Video and Voice | Partial | Not available in HIPAA-compliant environments |
Forsta types not listed here have no documented Sprig equivalent. They appear in the does-not-port inventory with a workaround. Plan and format restrictions in this table were verified against Sprig’s documentation on November 11, 2026, and this guide states no pricing for either platform.
The Restrictions That Catch Forsta Teams
Three restrictions catch Forsta teams most often. Rank Order needs an Enterprise plan. Multi-Question Single Page works only in Surveys, so a page of five open text fields in an in-product survey becomes five pages. And Sprig’s question-type documentation states the conjoint restriction two different ways, Standard Format in its summary table and link surveys only in its conjoint section, so confirm the format with Sprig before building.
Two Restrictions Outside the Plan Tier
Two restrictions have nothing to do with the plan. Consent / Legal questions work only in In-Product Surveys and Surveys, and Video and Voice questions aren’t available in HIPAA-compliant environments. A Forsta study that collected recorded testimonials under a HIPAA program has no documented Sprig equivalent for that question.
Net Promoter Score and Rating Scales
Net Promoter Score (NPS) maps cleanly as a question type, but the rendered scale can still differ. Check the number of points, the end labels, whether a midpoint label shows and whether the scale renders horizontally on mobile. Those are presentation changes, and presentation changes can move a tracked score.
Grids on Mobile
Grids generally render differently on mobile than on desktop in any platform, and a Forsta grid and a Sprig Matrix may not stack the same way on a phone. If a large share of your respondents answer on mobile, preview each rebuilt grid on a phone and compare it with the Forsta rendering. A grid that becomes a sequence of single questions on mobile is a presentation change worth bridging.
Required Questions and Answer Validation
Forsta programs frequently enforce answers through script, with custom error messages. Sprig marks questions required or optional, and Validated Text covers text validation. Check every forced-response question, since a question that was required in Forsta and optional in Sprig will lower its base size and can shift its distribution.
Decision rule: If a tracked question maps as "Partial," include it in the bridge study even if the change looks cosmetic. The bridge study is how you find out whether it was.
Rebuilding Logic and Survey Flow
Rebuilding logic is translating code into settings. Forsta programs express logic as script, and Sprig expresses it as skip logic, display logic, piping and randomization configured in the editor, so every scripted condition becomes a design decision.
What Sprig Documents for Logic
Sprig documents skip logic on all plans, configured at the bottom of each question, with one skip control per multi-question page and no redirects between questions on the same page. Display logic, response piping and attribute piping are Enterprise-only. Randomization is available on all plans at the survey, block, subset and response-option levels, and it respects skip logic, display logic and piping.
Translating a Condition
Translate each condition by asking what it decides rather than how it’s written. A Forsta Plus condition that skips a block when Q3 equals 2 becomes skip logic on Q3. A Decipher condition that shows a question only to a computed segment becomes display logic on an attribute, with the segment computed before the survey and passed in.
Computed Values Move Upstream
Python exec blocks and JScript script nodes frequently compute a value mid-survey: a segment, a score or a quota cell. Sprig documents no scripting, so the computation moves upstream.
Compute the value in your own systems, store it as a user attribute, and use attribute piping or display logic on it. For values that depend on earlier answers in the same survey, redesign the flow so a screener question collects the input directly.
Loops Become Duplicated Blocks
A loop over brands, products or locations becomes one block per item, since Sprig documents no loop construct. For a loop over many items where each respondent sees a random few, use subset randomization on a parent block. Rather than rebuilding a 20-item loop by hand, decide first whether every respondent needs every item.
Quotas Need a Screener
Sprig quotas are Enterprise-only and are built on screener questions answered in the survey: Multiple Choice single-select, Rating Scale and NPS. Only completed responses count toward a quota, and a quota’s criteria can’t change once the survey is active. A Forsta quota keyed to a sample variable or a scripted segment needs a screener question that captures the same split.
Validation and Masks
Custom validation written in script has no documented equivalent beyond Validated Text. Column masks in 3D grids have no documented equivalent either. Split the grid, or move the masking decision to question-level display logic.
Piping Syntax Doesn’t Carry Over
Forsta Plus pipes text through script in form elements, and Decipher pipes through its own pipe syntax. Neither syntax means anything to Sprig. Sprig documents response piping and attribute piping on Enterprise plans, with fallback text for missing attribute values, and it can’t pipe from consent, video and voice, Text / URL prompt or recorded-task questions. Rebuild every pipe and test it with a missing value.
Randomization Behaves Differently
Forsta randomization is commonly scripted, with custom rules for which items stay anchored. Sprig documents randomization of questions and blocks with items pinned in place, subsets of a block, and response options. Write each Forsta randomization rule in plain language first, then rebuild it from that description rather than from the code.
Decision rule: If a condition can’t be expressed as skip logic, display logic, piping, randomization or a screener-based quota, it needs a redesign. Flag it during the audit, not during the rebuild.
Rebuilding the Instrument in Sprig
Rebuild each instrument from its questionnaire document rather than its script. A Forsta script contains rendering code, validation and logic tangled together, while a questionnaire document contains the research design, which is the part you want in the destination.
Start From the Questionnaire
Most Forsta trackers began as a Word questionnaire that a programmer scripted. That document, updated to match the live version, is the best input to the rebuild. Where the original is lost, render the live survey to a document from a test link and annotate the logic by hand.
The AI File Upload Builder
Sprig’s AI File Upload Builder, available on Enterprise plans, turns a .pdf or .docx questionnaire of up to 25 MB into a draft study. It recognizes Multiple Choice, Rating Scale, NPS, Rank Order and Matrix questions, as well as Open Text, Text / URL, voice and consent questions. It also reads directives for required questions, randomization, skip logic and display logic written into the document.
Format the document the way the builder expects before uploading. Number every question, end each one with a question mark, mark question types in brackets and wrap multi-question pages in page start and end tags. The builder doesn’t import MaxDiff questions or prototype links, so add those by hand afterward. Researchers remain responsible for checking every imported question, type and logic directive against the source questionnaire.
What the Builder Won’t Decide
The builder drafts, but it doesn’t decide. It won’t know that a Forsta 3D Grid should become three Matrix questions rather than one, or that a scripted segment should become an attribute. Make those calls in the questionnaire document before upload, so the draft reflects the redesign rather than the original code.
How Sprig fits here. The Design Agent can also draft a study from a pasted question list or a plain-language objective, and it flags unclear questions and conflicting logic. It doesn’t verify that a rebuilt question is equivalent to its Forsta original, and researchers remain responsible for checking every question and logic path against the source before launch.
The API and MCP Route
Teams that rebuild dozens of instruments can script the work. Sprig’s Study API v2 creates draft studies of the Survey and In-Product Survey kinds, adds questions within each kind’s supported set, and launches a study by setting its status. Sprig’s Model Context Protocol (MCP) server also supports study creation from AI clients such as Claude and ChatGPT, with a human approving every study before it goes live.
Translations
Sprig’s AI Translations generates translations for every selected language in one step, covering questions, descriptions, choices and button labels, and lets you edit each field beside the original. Forsta translations don’t carry over, and regenerating replaces manual edits, so translate only after the source-language instrument is final. Then have a native speaker review each language of every tracked question.
The Order That Works
Rebuild in this order: the questionnaire document, the draft, the logic, the translations, then a full test of every path. Testing every path matters more than usual, because skip logic that looked identical in the document can route differently once page groupings change.
Pilot With One Tracker
Rebuild one active tracker end to end before rebuilding the rest. The pilot shows how long a real rebuild takes in your hands, which restrictions bite, and how the bridge study works in practice. Use that measured time, not a guess, to plan the remaining rebuilds.
Decision rule: If a rebuilt instrument hasn’t been tested path by path against the Forsta original, it isn’t ready for a bridge study.
The Measurement Discontinuity
Changing survey platforms changes how questions are administered, rendered and sampled, all at once. The tracked number moves, and the movement isn’t a change in what customers think. A team that migrates a tracker mid-year and reports the resulting step change to an executive team has published an artifact as a finding.
Two Effects, Not One
A platform migration produces two separate effects. Measurement effects come from how the question is asked: mode, layout, scale rendering, page breaks and device. Selection effects come from who answers: a different invitation channel, a different sample source or a different panel reaches different people.
Separating the two requires comparable data collected at the same time. A judgment call after the fact can’t separate them, because both effects show up as the same moved number.
How Large the Mode Effect Can Be
Pew Research Center measured the mode effect directly in 2015. It randomly assigned 3,003 members of its American Trends Panel to a phone interview or a web survey and asked 60 questions in both. The mean difference was 5.5 percentage points, and the largest gaps were on satisfaction items: phone respondents were 18 percentage points more likely to say they were very satisfied with family life.
Pew also said that for most of those differences there was no way to determine whether the phone or the web answer was more accurate. That caveat is the important one for a migration. A moved number isn’t a corrected number, and it isn’t an error either. It’s a different measurement.
The Items That Move Most Are the Ones Teams Track
The items that moved most in Pew’s study were satisfaction, favorability and sensitive self-reports. Those are close cousins of the satisfaction, likelihood-to-recommend and brand-favorability items that many customer and brand trackers report. A Forsta Plus CATI tracker moving to a self-administered survey makes the same kind of change, from interviewer to self-completion, that Pew tested.
House Effects Say the Same Thing About Vendors
Changing the organization that fields a survey also moves results. In 2016 Pew fielded an identical 56-item questionnaire through nine online samples from eight vendors and found results varied with the vendor, concluding that "Vendor choice matters." A migration that also changes your sample source carries this effect on top of the mode effect.
Two Precedents, Handled Differently
Large survey programs have handled measurement transitions in two different ways. The University of Michigan’s Surveys of Consumers blended the change in gradually. It ran experimental web collection monthly from 2017, shifted the official sample from 25% web in April 2024 to 50% in May and 75% in June, and moved fully to web in July 2024.
Even with seven years of parallel data, Michigan found some items behaved very differently by mode. Its index of consumer sentiment correlated at 0.97 between modes, but nominal income expectations correlated at only 0.14. Michigan advised a more conservative reading of month-to-month changes during the transition.
The Centers for Disease Control and Prevention took the opposite route with its Behavioral Risk Factor Surveillance System in 2011. It added cell phone respondents and new weighting methods in one step, then told users that the new data “cannot be accurately compared to previous findings line by line.” CDC declared a break in the series rather than bridging it.
What the Precedents Teach
The precedents teach that there’s a choice, and that both answers are legitimate when they’re stated. You either bridge the series with overlapping data and report the adjustment, or you declare a break and start a new series. The indefensible option is the common one: switching platforms silently and reporting the next number as a change.
Is There a Standard Overlap Length?
No general rule for overlap length exists in the methodology literature, and this guide won’t invent one. Michigan’s overlap ran for years, and BRFSS used none. The bridge study design below hands you a procedure and a decision rule rather than a calendar figure.
The Commercial Tension, Named
The methodologically correct answer is to run both platforms at the same time on the same population. You’re migrating partly to stop running both platforms. That tension is real, and a guide that recommends overlap without acknowledging its cost will be ignored. The next two sections size the overlap to the trackers that need it rather than to the whole program.
Rendering and Device Effects Inside the Web Mode
A migration from web to web still changes measurement. Page breaks, the number of questions per screen, scale orientation, button styles and mobile stacking all differ between platforms. No study cited here measures their size inside a single mode, but tracked satisfaction items sit close to thresholds that stakeholders watch, so small shifts still get reported as news.
What to Tell Stakeholders Before the Numbers Move
Tell the people who read the tracker before cutover, not after the first odd number. Explain that the platform change may move the series, that a bridge study will measure how much, and that the methods note will record the decision. Rather than defending a surprise, you’re reporting a planned check.
Why Adjusting Afterward Isn’t Enough
Teams sometimes plan to explain a step change after it appears. That rarely works. Without overlapping data, nobody can say how much of the change came from the platform and how much from the customers, so any explanation offered afterward is a guess presented as an answer. The bridge study exists to collect the evidence while it can still be collected.
Decision rule: If a tracker reports a number to executives, it needs either a bridge study or a declared break, decided before cutover and written into the methods note.
Designing the Bridge Study
To keep a tracker comparable after switching survey platforms, run a bridge study: a short period in which the same tracker runs on the old and the new platform at the same time, on comparable samples, so you can measure how much the platform change alone moves the number. If you can’t run one, declare a break in the series rather than switching silently.
What to Hold Constant
Hold constant everything you’re not testing. On the instrument side, that’s question wording, response options, scale points and labels, and question order. On the fielding side, it’s the population definition, the field window and the incentive. Every difference you allow becomes a candidate explanation for any gap you find.
What Will Vary Anyway
The rendering, the page layout and often the invitation channel will vary, because that’s what a platform change is. Record each difference in the bridge-study log so the methods note can name it.
The Frame Problem
The frame problem is the one most migrations can’t design away. If Forsta reached customers by phone and Sprig reaches them by email or in-product, the two samples come from different frames, and some of the gap is selection rather than measurement. Randomizing one population between the two platforms is the cleanest design. Where that isn’t possible, compare demographic and account profiles of both samples and report the difference.
The Bridge Study Specification
| Element | Specification |
|:---:|:---:|
| Scope | Every tracked question that reports to executives, plus every "Partial" mapping |
| Design | One population, randomly split between Forsta and Sprig where possible |
| Held constant | Wording, options, scale points, order, population, field window, incentive |
| Logged differences | Rendering, page breaks, device mix, invitation channel, sample source |
| Comparison | Difference in each tracked estimate, with its confidence interval |
| Decision | Continuous, adjusted or broken, per question, recorded in the methods note |
Sizing the Bridge
Size the bridge to detect the smallest shift your stakeholders would act on, not to a round number. If leadership reacts to a three-point move in a satisfaction score, each arm needs enough completes for a difference of three points to be distinguishable from noise. Run the power calculation with your own baseline rates rather than borrowing a sample size from another program.
The Decision Rule for the Series
For each tracked question, the bridge result leads to one of three outcomes. If the difference is within the noise you sized for, declare the series continuous. If the difference is consistent and stable, report the series as adjusted, with the adjustment stated. If the difference is large or unstable, declare a break and start a new baseline.
Reporting the Bridge Result
Report the bridge result in one table per tracker: each tracked estimate on Forsta, the same estimate on Sprig, the difference, its confidence interval and the decision. Add one paragraph naming the logged differences that most plausibly explain any gap. That table and paragraph go into the methods note and travel with every future chart of the series.
Decision rule: If you can’t run a bridge study for a tracker, declare a break for it. A silent switch is the only option that can’t be defended.
Users, Roles, SSO and Provisioning
Sprig documents single sign-on with Auth0, Google Workspace, KeyCloak, Microsoft Entra ID, Okta and OneLogin, plus roles and permissions. Its SCIM support is narrower than many Forsta administrators will expect, so plan provisioning before cutover.
What Sprig Documents for Provisioning
Sprig’s SCIM documentation states that SCIM is Enterprise-only and handles deprovisioning: when the identity provider marks a user inactive, Sprig soft-deletes that dashboard user. Sprig doesn’t create users through SCIM, and import, groups, name updates and password sync aren’t supported. A user needs an existing account with the same email before SCIM can act on it.
What That Means in Practice
A Forsta administrator who provisions users automatically from the identity provider will need a different joiner process. Rather than relying on SCIM for joiners, use SSO plus invitations or domain-based team discovery, which Sprig documents, and keep SCIM for leavers. Give the joiner process a named owner, since it’s no longer automatic.
Audit and Access Logging
Sprig’s audit log is Enterprise-only and records membership and role changes, invitations and approved join requests. Sprig’s security page states that access to its applications is logged and audited, with logs kept for at least one year. Confirm with your security team that this covers what your current Forsta audit evidence covers.
Compliance, as Documented
Sprig’s security page lists SOC 2 Type II, HIPAA, GDPR and CCPA, and states that Sprig uses AWS facilities in the USA. Hosting outside the US isn’t documented, which is why the residency condition appears under who shouldn’t migrate.
Mapping Forsta Roles to Sprig Roles
List every Forsta role in use and what each one can do, then map each onto Sprig’s documented roles and permissions. Export Forsta’s role list and the permissions for each role before you map them. Rather than recreating every role, start from what each group of users needs to do in the new platform.
Workspaces and Team Structure
Sprig’s audit log records members added to or removed from the organization or a workspace, which reflects an organization-and-workspace structure. Decide how your research teams map onto workspaces before inviting anyone, since moving studies and people later is harder than placing them correctly once.
Leavers on Both Platforms
During the parallel run, a leaver has accounts on two platforms. Make sure your offboarding process removes access to both, and keep Forsta access reviews running until the contract ends. A dormant Forsta account with export rights is a data exposure for as long as the platform holds your data.
Decision rule: If your Forsta setup provisions users by SCIM, design and test the replacement joiner process before cutover rather than on cutover day.
Integrations and Downstream Data
Downstream data is the part of a Forsta migration that breaks without anyone noticing. Inventory the consumers of your Forsta data, not the integrations on its settings page, because a consumer is anything that reads the data and acts on it.
Inventory the Consumers
Consumers include Reportal dashboards, Quantum or SPSS tab jobs, warehouse loads, CRM Connect for Salesforce syncs, recurring decks and any scheduled export someone set up years ago. For each one, record what it reads, how often, who owns it and what replaces it. A consumer with no replacement is a report that will quietly go stale.
What Sprig Documents for Data Out
Sprig documents CSV export of study data with response text, numeric values or both, optionally including AI themes, user attributes and bot-detection scores. Exports arrive by email with a link that expires after one week, and each export supports up to 950,000 rows. Sprig also documents webhooks and Segment as data destinations.
What Sprig Doesn’t Document
Sprig’s documentation index has no pages for Snowflake, BigQuery, Redshift, S3 or Salesforce connectors, and no Quantum, SAS, SPSS or fixed-width export. A team whose data-processing house expects SPSS needs a conversion step that turns Sprig’s CSV into the format the tab job reads. Build and test that step before cutover.
Delivery Channels Need Their Own Check
Sprig documents distribution by email, shareable links, in-product surveys on web apps and websites, native mobile apps and research panels. Each channel has its own setup.
Email needs a sending domain, in-product surveys need the SDK installed, and mobile surveys need the app team, so a channel change is also a project with an owner.
Sample Sources and Panels
If Forsta studies sampled from a panel vendor through a link, the vendor’s redirects and completion codes need to be rebuilt for Sprig. If they sampled from your own customer lists, those lists need to reach Sprig as email recipients or as user attributes. Sprig also documents its own research panels for external participants, which changes the sample source and belongs in the bridge study log.
Testing the Conversion Step
Test the CSV conversion step with a real Sprig export before cutover. Check variable names, value codes, missing-value handling, multi-select layouts and open-end encoding against what each tab job expects. A conversion step that works on a test file with 10 rows can still fail on a full wave with long verbatims and non-Latin scripts.
Decision rule: If a downstream consumer has no named replacement, the migration isn’t ready to cut over, however finished the instruments are.
The Parallel Run
The parallel run is the period when both platforms are live for real fieldwork, not only for the bridge study. Keep it as short as the bridge studies and the consumer cutover allow, and no shorter.
What the Parallel Run Costs
The parallel run costs two licenses, two sets of operational work and two sets of data to reconcile. That cost is why teams skip it. But skipping the parallel run moves the cost into the tracked series, where it shows up as an unexplained step change a year later.
How to Make It Affordable
Make the parallel run affordable by narrowing it rather than skipping it. Run only the trackers that report to executives in parallel, and move one-off studies straight to Sprig. Field the bridge-study arms on the smallest sample that meets the sizing rule, and move ad hoc work to the new platform first so the Forsta workload shrinks while the parallel run continues.
Sequencing Against the Contract
Work backward from the contract date. The bridge study needs a full field window on both platforms, the final Forsta export needs time to be checked, and the deletion clause starts at the end of the term. Start the bridge for your slowest tracker early enough that its last Forsta wave closes well before notice takes effect.
The Sequenced Migration Plan
| Phase | Work | Owner | Depends on |
|:---:|:---:|:---:|:---:|
| 1. Audit | Inventory studies, consumers, contract clause | Research operations | Nothing |
| 2. Archive | Export, verify and store history with datamaps | Data owner | Phase 1 study list |
| 3. Rebuild | Redesign and rebuild instruments, test every path | Survey programmer | Phase 1 decisions |
| 4. Bridge | Run trackers on both platforms and compare | Tracker owner | Phase 3 tested instruments |
| 5. Consumers | Replace dashboards, tab jobs and loads | Systems owners | Phase 3 data shape |
| 6. Cutover | Stop Forsta fielding, final export, notice | Research operations | Phases 2, 4 and 5 |
| 7. Validate | Sign off fidelity, data and access | Research lead | Phase 6 |
The plan carries no durations because no source supports a general one. The dependencies are the plan: no phase starts before the phases it depends on are signed off.
Freeze Changes During the Parallel Run
Freeze questionnaire changes on both platforms while a tracker is in parallel. A wording fix applied on one side during the bridge makes the comparison meaningless. Collect proposed changes in a list and apply them to the Sprig instrument after the bridge decision is recorded.
Decision rule: If the bridge study for any executive tracker can’t finish before the contract date, either extend the Forsta term for that tracker or declare its break now.
Cutover and Decommissioning
Cutover is the date Forsta stops fielding. Decommissioning is everything after that date, until the contract ends and Forsta deletes your data. Treat them as two steps with a gap between them, and use the gap for verification.
The Cutover Sequence
Cut over in this order:
- Confirm every bridge study has closed and its decision is recorded
- Close fielding on each Forsta study and record the close date
- Run the final export for every study, including the questionnaire and metadata
- Open each final export and check its row count against Forsta’s own count
- Switch each downstream consumer to its replacement and confirm one full cycle
- Remove Forsta links from invitations, intercepts and apps
- Give contractual notice
What to Keep
Keep the final exports, datamaps, rendered questionnaires, methods notes and bridge-study results. Keep a list of every Forsta study and its fate: migrated, archived or retired. The list is what someone will need when an executive asks in two years why a number changed.
The Deletion Decision
Forsta’s published agreement deletes client materials within 60 business days after the term ends. Decide before that date whether anything else needs exporting, because after it there may be nothing left to export. Request written confirmation of deletion if your data protection obligations require it.
Respondent-Facing Links
Old Forsta survey links can sit in email templates, help-center articles, app intercepts, QR codes on printed material and partner websites. Search for the Forsta survey domain across your systems and replace or retire every link. A respondent who clicks a dead link after cutover becomes a lost response and, sometimes, a complaint.
Communicating the Change Internally
Tell every team that receives Forsta data what changes, when it changes and who to call. A short note with the cutover date, the new data location and the methods-note link answers the questions that would otherwise reach the research team after cutover.
Keeping One Forsta Login Until Deletion
Keep at least one administrator login active on Forsta until the term ends, even after fielding stops. Someone will need to check an export, answer an audit question or retrieve a study that the audit missed. Once the term ends and deletion begins, that option is gone.
Decision rule: If any final export hasn’t been opened and row-checked, don’t give notice yet.
Validating the Migration
Validation is the formal approval that the migration preserved what it was supposed to preserve. It has four parts: instrument fidelity, data integrity, the bridge result and access.
Instrument Fidelity
For each migrated instrument, compare the Sprig version against the Forsta questionnaire question by question. Check wording, options, order, logic paths, quotas and languages. Every difference should be one that the redesign decided on, not one that crept in.
Data Integrity
For each archived study, check that row counts match Forsta’s own counts and that a sample of records decodes correctly with its datamap. For each migrated tracker, check that the first Sprig wave produces the same variables your downstream consumers expect.
How Sprig fits here. The Synthesize Agent turns structured and open-ended responses into a report with themes that link back to the responses behind them, which helps reviewers spot an instrument that’s collecting something different from its Forsta original. Sprig’s Analyze Agent, shown as in preview, describes crosstabs, t-tests and ANOVA.
Neither replaces the question-by-question fidelity check, and researchers remain responsible for that approval.
The Bridge Result
Record the bridge decision for each tracked question as continuous, adjusted or broken, with the evidence. The methods note for each tracker carries the decision, so the next analyst doesn’t have to rediscover it.
The Access and Consumer Check
Confirm that every user who needs Sprig has it, that every leaver has been removed from both platforms, and that every downstream consumer completed a full cycle on Sprig data. Then sign off.
Final Approval
The research lead signs off when all four parts pass. Without that approval, the migration has no end date.
A Validation Checklist
Use this checklist for each migrated study:
- Wording, options and order match the approved redesign
- Every logic path routes as the Forsta original did, or as the redesign decided
- Quotas close at their targets on test data
- Every language has passed native-speaker review
- The first wave’s variables match what downstream consumers expect
- The archive for the Forsta history opens and decodes correctly
A study that passes all six is migrated. A study that fails any one goes back to the phase that owns it.
Validate Again After the Second Wave
Validate each tracker again after its second Sprig wave. The first wave proves the instrument works. The second shows whether the series is stable on the new platform, which is what your stakeholders will rely on.
Decision rule: If any of the four parts fails, the migration isn’t complete, whatever the contract date says.
Where Forsta Wins
Forsta does several things better than Sprig, and naming them is part of planning a migration rather than a concession of the decision. Each item below is checkable against Forsta’s own documentation.
Phone and In-Person Fieldwork
Forsta Plus documents CATI for managing telephone interviews and CAPI for face-to-face fieldwork, with the CAPI app running offline on Windows, Android and iOS devices. Sprig documents neither. For any program that reaches people who won’t answer a web survey, Forsta wins.
Code-Level Survey Programming
Forsta lets programmers write the survey. Forsta Plus programs use JScript .NET or JavaScript for conditions, masks, loop filters, piping and validation. Decipher programs use XML with Python exec blocks and virtual questions. Both platforms let a programmer write survey logic as code, which covers flows that a settings-based editor can’t express. Sprig documents configuration rather than code.
Specialist Instrument Breadth
Decipher’s help center documents dynamic elements including Card Sort, Image Map, Text Highlighter, Shopping Cart, Media Evaluator and DCM Conjoint, and Forsta Plus documents 3D Grid, Numeric List and Geolocation. These are the same items that appear in the does-not-port inventory above. Studies that use them stay on Forsta, move to a specialist tool or get redesigned.
Documented Statistical Testing
Forsta documents its significance testing. Forsta Visualizations names a Z-test for two independent samples and describes an effective base for weighted data, and Studio offers six confidence levels from 80% to 99.8%. A platform that names its test can be defended in a room with a methodologist. Sprig documents no weighting method, and its Analyze Agent, which describes t-tests and ANOVA, is shown as in preview.
Regional Hosting
Forsta’s published Cloud Schedule names Canada-based, Germany-based and Australia-based cloud services, with the location set in each order form. Sprig hosts in the US. For a buyer with a residency requirement, Forsta wins this dimension.
Integrated Panels and Translation Modules
Forsta Plus lists Professional Panels for managing owned panels and a Translator module, and Forsta’s Decipher page claims support for more than 80 languages. Sprig documents research panels for reaching external participants and AI Translations, but not an owned-panel management module.
A Mature Data-Processing Ecosystem
Forsta fits into traditional market research data processing. Forsta Plus exports SPSS, SAS, Quantum, Triple-S XML and fixed-width files, and Decipher exports SPSS layouts, datamaps and a Triple-S datamap. Tab houses and data-processing teams have built workflows on those formats for years. Sprig exports CSV, so a team with a deep data-processing pipeline gives up native format support and needs a conversion step.
Control Over Rendering
Forsta programmers control rendering closely, from custom layouts to Decipher’s styling configuration for dynamic questions. A team that matched a tracker’s look to a legacy paper or phone instrument can preserve that match in Forsta. Sprig documents editor settings rather than layout code, which is simpler to run but gives a programmer less control over how each question appears.
Common Mistakes
The common mistakes in a Forsta migration are predictable, and most come from treating it as a rebuild rather than four projects. Each one below names the prevention.
Rebuilding From the Script
Teams often hand a Decipher XML file or a Forsta Plus export to whoever rebuilds the survey and ask for a copy. The result reproduces the code’s quirks and misses the design intent. Rebuild from the questionnaire document, with redesign decisions written in, rather than from the script.
Exporting Data Without the Datamap
A fixed-width or SPSS file without its datamap is unreadable a year later. Export the datamap, the rendered questionnaire and the methods note alongside every data file.
Reading the Contract Late
The deletion clause sets the deadline for everything, and it commonly sits with procurement. Find it in the first week of the audit. A team that reads it during cutover usually discovers it has less time than it planned.
Treating "Partial" as "Yes"
A question type that maps as "Partial" carries a restriction: a plan tier, a survey format or a rendering change. Treating it as a clean port is how a tracked score moves without explanation. Put every "Partial" tracked question into the bridge study.
Skipping the Bridge Study
Skipping the bridge to save the cost of a parallel run moves that cost into the series. Michigan’s 2024 transition shows how differently items can behave across modes even after years of preparation. If you can’t bridge a tracker, declare a break instead.
Forgetting the Tab Jobs
Quantum, SPSS and Excel jobs that read Forsta exports keep running on the last file they received, so they report stale numbers rather than failing. List them in the audit and switch each one to Sprig’s CSV through a tested conversion step.
Assuming SCIM Covers Joiners
Sprig’s SCIM handles deprovisioning only. A team that assumes new users will appear automatically finds out when the first new researcher can’t log in. Design the joiner process before cutover.
Moving Phone Trackers to the Web Silently
Moving a CATI tracker to a web survey changes the mode, and Pew measured mode gaps of up to 18 percentage points on satisfaction items. Either keep the tracker on the phone with a phone vendor or bridge it and report the change.
Rebuilding Everything Before Testing Anything
Rebuilding every instrument before testing the first one multiplies any systematic error across the whole program. Pilot one tracker, fix what it reveals, then rebuild the rest.
Losing the Methods History
The methods history, meaning mode changes, questionnaire revisions and weighting changes over the life of a tracker, usually lives in someone’s memory. Write it down during the audit. Once that person moves on, the history of the series becomes impossible to explain.
Decision rule: If your plan doesn’t name an owner for the archive, the bridge, the consumers and the contract date, it has one of these mistakes in it.
How Sprig Supports the Migration
Sprig supports the rebuild, the fielding and the analysis after cutover. It doesn’t support the archive, which lives outside both platforms, and it doesn’t replace the bridge-study judgment, which stays with your researchers.
Rebuild
The Design Agent and the AI File Upload Builder draft studies from your questionnaire documents, and Sprig’s Study API v2 and MCP server let teams script the rebuild of many instruments. Researchers review every draft and approve every study before launch.
Fielding
Sprig distributes by email, links, in-product surveys on web apps and websites, native mobile apps and research panels. The Field Agent asks contextual follow-ups based on each response, and researchers can enable or disable AI follow-ups.
Follow-ups change what each respondent is asked, so researchers remain responsible for turning them off on tracked questions in a bridge study and for reviewing them before launch. Sprig quotas, on Enterprise plans, control fielding on screener questions.
Analysis
The Synthesize Agent builds reports from structured and open-ended responses, and customers use those reports as a running record of what each study found. The Analyze Agent, shown as in preview, describes crosstabs, t-tests, ANOVA and correlation, and researchers remain responsible for checking any test it reports against their own analysis.
Sprig doesn’t store or analyze research it didn’t collect, such as your archived Forsta history, so that history stays in your warehouse.
Where Sprig Doesn’t Help
Sprig doesn’t import Forsta responses, run phone or in-person fieldwork, host data outside the US, or document a weighting method. Plan for each of those outside Sprig, as the sections above describe.
Where to Start
Start with a single active tracker that runs on the web, uses common question types and has a clear owner. Rebuild it from its questionnaire, field it alongside Forsta as a bridge study and review the result with its stakeholders. That pilot shows, with your own data, which parts of the plan hold and which need more time.
Decision rule: If the reason you’re migrating is a capability Sprig documents, rebuild one active tracker as a pilot and run its bridge study before giving notice on anything.
Frequently Asked Questions
Can I Import My Forsta Survey Responses Into Sprig?
No, Sprig documents no way to import historical survey responses, as of November 11, 2026. Its CSV import covers user attributes and adding users to manual groups, and its Study API v2 creates studies and questions rather than responses. Keep Forsta history in a warehouse, BI layer or governed archive, with its datamap and a methods note, and query it beside new Sprig data.
Can Sprig Read a Decipher XML or Forsta Plus Survey File?
No, Sprig documents no import of Decipher XML or Forsta Plus survey definitions. The practical route is the questionnaire document: Sprig’s AI File Upload Builder turns a formatted .pdf or .docx questionnaire into a draft study on Enterprise plans. Rebuild from that document, then test every logic path against the Forsta original.
What Doesn’t Transfer From Forsta to Sprig?
From Forsta to Sprig, phone and in-person interviewing, loops, scripted logic, regional hosting outside the US and response history don’t transfer. Several question types have no documented Sprig equivalent. They include 3D Grid, Numeric List, Date and Geolocation, as well as Image Upload, Image Map, Shopping Cart and Media Evaluator. Others port partially, with plan or format restrictions, including Rank Order, conjoint, quotas and sliders.
How Long Does a Forsta Migration Take?
No published source supports a general duration, so this guide doesn’t give one. The length depends on the number of active studies, how many are scripted programs, how many trackers need bridge studies and when the contract ends. Build the plan from the dependencies in the sequenced migration plan, then work backward from the contract date.
Will My Satisfaction or NPS Score Change When I Migrate?
It may, even if the customers haven’t changed. Changing platforms changes mode, rendering and often the sample, and Pew’s 2015 experiment found a mean mode gap of 5.5 percentage points across 60 questions, with the largest gaps on satisfaction items. Run a bridge study for every tracked score, or declare a break.
How Long Should I Run Forsta and Sprig in Parallel?
No general rule for overlap length exists in the methodology literature. Michigan’s Surveys of Consumers ran experimental web collection for years before a four-month blend, while CDC’s BRFSS declared a break with no overlap. Run each executive tracker in parallel long enough to complete a bridge study sized to the smallest change your stakeholders act on.
When Does Forsta Delete My Data After the Contract Ends?
Forsta’s published Master SaaS Agreement says Forsta permanently deletes client materials no later than 60 business days after the term ends. The same agreement says self-service export is available at no additional cost during the term, while Forsta-performed data returns carry additional fees. Your own agreement may differ, so read it and export before notice.
Does Sprig Support SSO and SCIM?
Yes, Sprig documents single sign-on with Auth0, Google Workspace, KeyCloak, Microsoft Entra ID, Okta and OneLogin. Its SCIM support is Enterprise-only and covers deprovisioning: Sprig doesn’t create users through SCIM, and groups aren’t supported. Plan a separate joiner process using SSO and invitations.
Can Sprig Replace Forsta for Phone Surveys?
No, Sprig documents no CATI or CAPI. Keep phone and in-person trackers with a vendor that runs those modes, or move them to self-completion with a bridge study and a declared break if the gap is large. Pew’s 2015 experiment shows why the move from phone to web changes results.
Does the Qualtrics Acquisition Change What Happens to Forsta?
Qualtrics completed its acquisition of Press Ganey Forsta in May 2026, and as of November 11, 2026 it hadn’t published a roadmap for Forsta’s survey products. Forsta’s Decipher page is still live under Forsta branding. Plan your migration on your contract dates rather than on expected product changes, since none had been announced as of that date.
Will Sprig Help With the Migration Work?
Sprig’s enterprise page describes multi-channel support from a dedicated Sprig Specialist, from onboarding to survey creation to analysis. It doesn’t describe a dedicated migration service. Before you give Forsta notice, ask your Sprig contact in writing what help covers instrument rebuilds, bridge-study design and the parallel run, and who on their side owns each one.
Should We Migrate at All?
Not if you depend on phone or in-person fieldwork, need hosting outside the US, run code-level instruments you can’t redesign, or need platform-computed significance testing with documented weighting. In those cases, keep the affected studies on Forsta and move only the simpler ones. For everyone else, start with one tracker and its bridge study.
Does Sprig Support Quotas Like Forsta?
Partly. Sprig documents quotas on Enterprise plans, built on screener questions answered in the survey, with Multiple Choice single-select, Rating Scale and NPS as supported screener types. Only completed responses count. A Forsta quota keyed to a sample variable, a computed segment or a loop iteration needs a screener question that captures the same split.
What Export Format Should I Use to Archive Forsta Data?
Export SPSS with its datamap for analysts, and standard Triple-S XML from Forsta Plus or the Triple-S datamap from Decipher for portability. Export open ends separately with respondent identifiers, and keep the rendered questionnaire and a methods note beside each file. Open every file and check its row count before giving notice.
Can Sprig Run Conjoint and MaxDiff Studies From Forsta?
Partly. Sprig documents Conjoint and MaxDiff as question types on Enterprise plans, MaxDiff in Surveys in Standard Format, with Sprig’s conjoint format restriction stated two ways in its documentation. The designs need re-specifying in Sprig, and estimation output won’t match Forsta’s DCM Conjoint, so treat the results as a new series.
Can I Keep Using My Forsta Panel Vendor With Sprig?
Yes, if the vendor sends respondents to a survey link and can redirect them to the completion URL of the new survey. Sprig documents shareable link surveys, so the vendor’s entry links, redirects and completion codes need rebuilding. Confirm that handling with Sprig before you contract the vendor.
Keep the same vendor through the bridge study where possible, since changing the sample source at the same time as the platform adds a house effect to the mode effect.
Who Should Own a Forsta Migration?
A research operations lead should own the migration as a whole, with named owners for each of the four projects: the survey programmer for the rebuild, the data owner for the archive, the tracker owner for each bridge study and the systems owners for downstream consumers. The person who can give contractual notice needs to be named in the first week.