Migration guideUpdated September 26, 2026

How to migrate from REDCap to Capture.Study

You cannot import a REDCap project directly. Here is the practical path: export your data dictionary, let AI draft your new forms from it, and merge historical data during analysis rather than mid-study.

  • AI drafts forms from your REDCap export
  • Built-in 21 CFR Part 11-aligned controls
  • Free sandbox to test first

Free sandbox · No credit card · 21 CFR Part 11 aligned

Build this form with AI

Question form

CRF or ePRO

Lab table

Analytes, units, ranges

Vital signs form: BP, pulse, temperature, respiratory rate, weight
Upload CSV, XLSX, PDF or DOCX
14 questionsReview before applying
  • 1. Systolic blood pressure

    Required · Number · mmHg · 0 dp

    Number
  • 2. Diastolic blood pressure

    Required · Number · mmHg · 0 dp

    Number
  • 3. Pulse rate

    Required · Number · beats/min

    Number
  • 4. Body temperature

    Required · Number · °C · 1 dp

    Number
  • 5. Position during measurement

    Required · Sitting, Supine, Standing

    Single choice
  • + 9 more questions
Back Apply to form

1-3 hrs

typical time to rebuild a REDCap instrument

4

file types the AI reads to draft a form: CSV, XLSX, PDF, DOCX

0

direct REDCap project imports (rebuild is the recommended path)

Field-level

audit trail from your very first entry

The migration path

Four steps to move a REDCap study

Switching mid-study is risky for any EDC. This path is for a new study, or for testing Capture.Study before your next one.

  1. 1

    Export your REDCap data dictionary

    Download the CSV data dictionary from your REDCap project. It lists every field, type and choice set you will need to recreate.

  2. 2

    Let AI draft the new forms

    Upload the exported dictionary, or describe the form, and the AI proposes questions and lab tables for you to review before anything is saved.

  3. 3

    Rebuild skip logic and validation

    Recreate branching in the visual builder and add edit checks. Simple REDCap branching logic maps directly; very complex nested expressions may need simplifying.

  4. 4

    Test in the free sandbox, then go live

    Walk through the participant and site flow with sample data before a single real participant is enrolled.

The slow part, sped up

Rebuilding forms by hand is what makes migration slow. AI drafting fixes that

Most REDCap migrations stall on rebuilding instruments field by field. Upload your exported data dictionary or a copy of the instrument, and the AI drafts the questions, choices and lab tables so you start from a structured draft instead of a blank form.

  • Reads CSV, XLSX, PDF or DOCX.
  • Flags anything it cannot confidently match instead of guessing.
  • You review and approve every field before it is used.
See the CRF builder in depth
Build this form with AI · Lab table
central_lab_ranges.xlsx48 KB
2 tables24 rows1 unrecognised analyte

Haematology

RowCodeUnitRangeStratum
HaemoglobinHGBg/dL13.0-17.0Male 18-65 y
HaemoglobinHGBg/dL12.0-15.5Female 18-65 y
PlateletsPLAT10^9/L150-400All
ALTALTU/L7-56All
Site QC flagSITEQC--All

Before you switch

What to check before migrating a study

Map your branching logic

Simple REDCap conditional logic maps directly to skip logic; list any nested or calculated conditions that will need simplifying.

Decide what to do with historical data

Export REDCap data to CSV and merge it with new Capture.Study exports during analysis, since direct import is not supported today.

Plan for re-consent if switching mid-study

Changing platforms mid-study is not recommended; use Capture.Study for a new study or a future arm instead.

Confirm your compliance requirements

Capture.Study provides a field-level audit trail, OTP-verified e-signatures and role-based access; check this covers your specific regulatory needs.

Upload a REDCap instrument and see the draft

Try it in a free sandbox with sample data. Nothing is saved until you approve it.

Start your migration free

What changes

REDCap workflow vs Capture.Study workflow

Building a form
Write or edit data dictionary syntax
AI drafts it from a file or description; you review
Multi-site setup
Configure Data Access Groups
Add a site and get a QR code automatically
Consent
MyCap module, separate app
Built into the same platform and audit trail
Data changes
Production mode locks, dev mode to edit
Draft and approved states, field-level audit trail

FAQ

Questions teams ask before they switch

Something not covered here? Ask us directly.

Can I import my REDCap project directly into Capture.Study?

Not automatically. Export your REDCap data dictionary, then use it to draft your new forms with AI assistance in Capture.Study rather than rebuilding entirely from scratch.

What happens to my existing REDCap data?

Export it to CSV from REDCap. Most teams merge historical REDCap data with new Capture.Study data during analysis rather than importing it into the new system.

Should I switch platforms in the middle of an active study?

We do not recommend it. Switching mid-study risks data integrity and may require re-consenting participants. Use Capture.Study for a new study or a future arm instead.

How long does rebuilding a REDCap instrument usually take?

AI drafting produces a first version in minutes. Reviewing and refining it typically takes one to three hours depending on the instrument's size and how much branching logic it has.

Does Capture.Study support the same branching logic as REDCap?

Simple conditional show and hide logic maps directly. Very complex nested REDCap branching expressions may need to be simplified to fit the visual skip-logic builder.

Can I test the migration before committing?

Yes. The free sandbox includes every feature with sample data, no credit card and no time limit, so you can rebuild an instrument and compare it against your REDCap project first.

Start your migration in a free sandbox

Upload a REDCap instrument and see it drafted in minutes. No credit card, no sales call.