Sometimes a vendor change cannot wait for the next study: a contract ends, a vendor is acquired, costs balloon or the system cannot handle an amendment. Here is how to do it without losing data integrity, and the alternatives worth considering first.
Free sandbox · No credit card · 21 CFR Part 11 aligned
Weeks
New data entered only in the new system from this date
Key points
Deciding
The reasons are usually commercial or practical rather than technical: a renewal quote far above the original contract, a vendor acquired and its product sunset, a CRO relationship ending and taking the database with it, or a system that cannot implement an amendment in a reasonable time or for a reasonable change-order fee. Each of these can make staying more expensive than moving.
If you are still choosing a platform, our Medidata Rave vs Veeva Vault EDC comparison lists the questions to ask enterprise vendors, and REDCap vs Castor covers the common academic choice. But a mid-study switch has costs that do not show up in the vendor comparison. Sites must learn a new system in the middle of recruitment. Monitoring plans, edit checks and data management procedures must be rebuilt and revalidated. And the study ends up with data in two systems, which has to be explained in the clinical study report and to any inspector.
Can the current study finish where it is? If most participants have completed and the remaining work is follow-up and cleaning, staying often costs less. Is there a natural break point, such as the end of Part A of a two-part study, a new cohort, an open-label extension or the next protocol? Starting the new phase in a new system gives a clean boundary. Our REDCap migration guide makes the same recommendation: use the new system for a new study or arm where possible.
| Switch mid-study | Next phase or study | |
|---|---|---|
| Data in one system | ||
| Site retraining mid-recruitment | ||
| Stops a runaway renewal cost now | ||
| Needed if vendor is shutting down | ||
| Inspection explanation required |
Step by step
Record the reason for the change, the risk assessment and the cutover plan in a change control document. Agree it with the sponsor, CRO and data management lead.
Rebuild the current protocol version in the new system, including edit checks and the schedule, and run user acceptance testing against the old system's specifications.
Choose a date after which all new data goes into the new system. Freeze and lock the legacy database for anything entered before it.
Export the complete legacy dataset, audit trail and metadata, archive them, and document how the two datasets are combined for analysis.
The legacy database
Regulators expect you to be able to reconstruct the study from its records, which means the legacy system's data is not just the clinical values. Before access ends, secure the full dataset in an open format, the audit trail showing who changed what and why, electronic signature records, query history, the form and edit check definitions that applied at each point in time, user access records, and the export and validation documentation.
Many contracts restrict or charge for bulk exports after termination, so negotiate the exit package before you give notice. Keep the archive for the full retention period your regulations require, and make sure someone can still open it in ten years.
Importing historical data into the new system looks tidy but raises hard questions: the new audit trail starts at import, not at original entry, and any mapping error becomes part of the clinical record. Most teams keep the legacy dataset as its own locked, archived source and merge the two at analysis using a documented mapping. Whichever you choose, write the rationale down.
Items
9
Secured
6
At risk
1
Rebuilding fast
The longest part of most transitions is rebuilding the study. In Capture, the AI Study Generator drafts visits, windows and forms from the protocol, and the AI form builder drafts questions from exported data dictionaries or CRF files, for your team to review. Everything can be tested with bulk test subjects before a single site switches.
11
visits
9
draft forms
2
diaries
Upload your protocol to a free sandbox and see how much of the study is drafted for you.
Before cutover
Reason, risk assessment, cutover date and responsibilities documented and signed off.
User acceptance testing against the current protocol version and edit check specification.
Data, audit trail, signatures, queries, metadata and documentation exported and archived.
Training completed and acknowledged before cutover; updated completion guidelines issued.
SDV scope and review procedures reflect the new system.
Confirm whether your procedures or authorities require notification of the change.
Yes, with a documented plan, a validated new build, a defined cutover date and a complete archive of the legacy data and audit trail. It carries risk, so consider switching at a natural break point first.
Not necessarily. Many teams archive the legacy dataset and merge it with new data at analysis using a documented mapping, which keeps the original audit trail intact.
It depends on study complexity and the number of sites. Rebuilding and validating the study usually takes the longest; AI-assisted builds can shorten that considerably.
The complete clinical dataset, audit trail, e-signature records, query history, form and edit check versions, user access history, data dictionary and validation documentation.
Not usually just because the data system changes, but check whether your consent form names the system or data processor, and follow your ethics committee's requirements.
Capture drafts studies from protocols and forms from exported files, and Enterprise plans include implementation assistance. For a mid-study switch, contact us to discuss your situation.
Keep exploring
How to migrate from REDCap
A specific migration path.
Protocol amendments without change orders
A common reason teams switch.
Computer system validation
Validating the new system.
Audit trail software
What a complete audit trail contains.
EDC procurement checklist
Choosing the next vendor.
Vendor security questionnaire
Due diligence before signing.
No setup fees, no change orders for amendments, and your data exportable any time.