Every year, thousands of researchers move between universities, labs, and research institutions. A 2022 study published in Quantitative Science Studies found that academic mobility is not only common but accelerating — and nearly 50% of scientists leave or change their academic home within a decade of their first publication. Yet for all the energy that goes into securing the next position, surprisingly little attention is paid to one of the most stressful parts of the transition: transferring your research data, references, and project materials without losing years of carefully organized work.
If you have ever stared at a folder of 2,000 PDFs, a half-finished manuscript, and a shared reference library that technically belongs to your old department, you already know the problem. Research data transfer between institutions is not just a logistics headache — it is a career risk. Mishandled transitions lead to lost citations, broken collaboration chains, duplicated effort, and months of rebuilding what you already had.
This guide walks you through exactly how to transfer your research when changing institutions — from legal considerations and data ownership to practical workflows for moving references, project files, and collaborative workspaces intact.
What happens to your research when you leave an institution?
When a researcher changes institutions, not everything moves automatically. Understanding what you own, what stays behind, and what lives in a gray area is the essential first step in any research data transfer.
Research data ownership typically depends on three factors: who funded the work, what your employment contract says, and what your institution's intellectual property policy dictates. In most cases, research data generated under a grant or institutional funding belongs to the institution, not the individual researcher. The University of Minnesota's policy on transferring research data, for example, explicitly states that data transfers require formal agreements between the departing and receiving institutions.
Here is what generally does and does not transfer with you:
Moves with you:
Your personal notes, annotations, and reading logs
Publications you have authored (published versions)
Your own analytical code and scripts (if not funded by the institution)
Knowledge, expertise, and methodological know-how
Stays behind or requires formal transfer:
Raw datasets generated under institutional grants or IRB protocols
Shared reference libraries hosted on institutional accounts
Lab notebooks and experimental records (physical or digital)
Access to institutional repository subscriptions and databases
Gray area:
Annotated PDFs and personal reference collections built using institutional subscriptions
Collaborative project files in shared drives
Draft manuscripts with co-authors still at the old institution
The key takeaway is that you cannot assume anything transfers automatically. Start by reading your institution's IP and data retention policies, and flag anything that requires a formal data transfer agreement before you leave.
How to create a research transfer checklist before you move
The single biggest mistake researchers make when changing institutions is waiting until the last week to figure out what needs to move. By then, access to shared drives may already be revoked, email accounts deactivated, and critical files scattered across half a dozen platforms.
Start your transfer planning at least two to three months before your departure date. Here is a practical checklist:
1. Audit every project you are involved in
List every active, paused, or nearly complete project. For each one, document:
Current stage (data collection, analysis, drafting, under review, published)
Your specific role and contributions
Where the data, files, and references live
Who else is involved and their institutional affiliation
Any deadlines tied to grants, conferences, or journal submissions
2. Classify projects by transfer priority
Not every project deserves equal effort during a transition. Sort them into categories:
Must transfer — Projects close to publication or central to your ongoing research agenda
Should transfer — Active collaborations where your continued involvement is expected
Can hand off — Projects where someone at the old institution can take over your role
Close out — Stalled or abandoned projects that need clean documentation, not continued work
3. Identify what needs formal agreements
If your research involves human subjects data, patient records, proprietary datasets, or grant-funded materials, you will likely need a data transfer agreement (DTA) or material transfer agreement (MTA). Contact your institution's Office of Research or sponsored programs office early — these agreements can take weeks or even months to finalize.
4. Back up everything you are legally allowed to keep
Before your institutional access expires, make personal backups of:
Your authored manuscript drafts and figures
Your personal reference library exports (BibTeX, RIS, or CSV files)
Code repositories and analysis scripts you wrote
Meeting notes, project plans, and your own written protocols
5. Notify collaborators and co-authors
Send a clear email to every PI and collaborator you work with. Outline your timeline, your continued availability (or lack of it), and propose a plan for each shared project. This is not optional — it is professional, and it protects both your reputation and your authorship.
How to export and organize your reference library for a move
For many researchers, the reference library is the single most valuable digital asset they have built over years of work. Losing it — or losing the annotations, tags, and organizational structure within it — can set a literature review back by months.
Here is how to move your references cleanly:
Export from your current reference manager
Most reference managers — Zotero, Mendeley, Paperpile, ReadCube Papers, and EndNote — allow you to export your full library in standard formats like BibTeX (.bib), RIS (.ris), or CSV. Always export in at least two formats for redundancy.
When exporting, make sure to include:
All metadata fields (authors, titles, journals, DOIs, abstracts)
Your tags, folders, and collection structures
Notes and annotations attached to individual references
Attached PDFs (if your license and institutional policy allow it)
Preserve your organizational structure
A flat export of 3,000 references with no folder hierarchy is almost useless. Before exporting, take time to:
Clean up duplicate entries
Verify that your folder or collection structure reflects your actual projects and topics
Add missing tags or keywords that will help you re-sort references at your new institution
Re-import into your new system
If your new institution uses a different reference manager, or if you are switching tools during the transition, plan the re-import carefully. Test with a small subset of references first to make sure metadata, tags, and PDF attachments survive the conversion.
This is where a platform like ScholarDock, a research project and reference management platform, offers a significant advantage. Because ScholarDock keeps your references, project files, and collaborative workspaces in a single cloud-based environment, your entire research library travels with you — no exports, no re-imports, no lost annotations. Your organizational structure, tags, connected projects, and shared collections stay intact regardless of which institution you are affiliated with.
How to transfer research project data between institutions
Beyond references, the bulk of a research transition involves moving project-level data: datasets, analysis files, protocols, and documentation. The approach depends on the type of data and the agreements governing it.
For non-sensitive research data
If your data is not subject to IRB restrictions, HIPAA, or institutional IP claims, transferring it is relatively straightforward:
Organize files into a clear folder structure before moving them. Use consistent naming conventions (e.g.,
ProjectName_DataType_Date) so that files are immediately identifiable at your new institution.Use secure cloud storage for the transfer. Institutional Google Drive or OneDrive accounts may be deactivated after you leave, so transfer files to a personal cloud account or your new institution's storage before your access expires.
Document everything. Create a README file for each project folder explaining what each file contains, how data was collected, what software is needed to open it, and any known issues. This helps both you and any collaborators who may need the files later.
For sensitive or regulated data
Clinical research data, human subjects data, and grant-funded datasets require more careful handling. According to Case Western Reserve University's research data guidelines, any transfer of sensitive data typically requires:
A signed data transfer agreement between institutions
De-identification of data where possible
Secure transfer methods (encrypted file transfer, not email attachments)
Documentation of chain of custody
Do not skip this step. Transferring restricted data without proper authorization is a compliance violation that can jeopardize your career and your former institution's standing with funding agencies.
For collaborative project materials
Shared documents, co-authored drafts, and team project boards often fall through the cracks during a transition. Before you leave:
Transfer ownership of shared Google Docs, Dropbox folders, or project management boards to a collaborator who is staying
Download your own copies of all documents you contributed to
Clarify with your team who will maintain shared resources going forward
How to maintain collaboration after changing institutions
One of the most underrated challenges of changing institutions is maintaining productive collaboration with your former research team. Studies on academic mobility consistently show that researchers who maintain strong cross-institutional networks produce more impactful work — but sustaining those connections requires deliberate effort.
Set clear expectations before you leave
Have an explicit conversation with each collaborator about:
Which projects you will continue to contribute to remotely
Your expected level of involvement (weekly check-ins, monthly updates, or on-call for specific tasks)
Authorship expectations for ongoing manuscripts
Communication channels (email, video calls, shared project platforms)
Document these agreements in writing. A simple follow-up email summarizing what was discussed is sufficient and protects everyone involved.
Use tools designed for cross-institutional research collaboration
One of the most common reasons remote collaborations fail is tool fragmentation. When your references live in one app, your project notes in another, your data in a third, and your communication in a fourth, things get lost.
Clinical research management software and general-purpose project tools often lack the specialized features research teams need — like connected reference libraries, structured knowledge bases, and citation-aware collaboration. This is exactly the gap that ScholarDock fills. With ScholarDock, you can share curated source collections, co-edit project notes, assign tasks across team members at different institutions, and keep every reference, annotation, and project artifact connected in a single workspace. When a collaborator at your old institution adds a new source to a shared collection, you see it instantly — no file syncing, no version conflicts, no lost context.
Protect your research continuity
The most damaging outcome of a poorly managed transition is not losing a few files — it is losing research continuity. When your knowledge is scattered across disconnected tools, old email threads, and expired institutional accounts, you spend months rebuilding context that should have traveled with you.
A portable, cloud-based research workspace ensures that your accumulated knowledge — every tagged reference, every project note, every connected finding — remains accessible and organized no matter where your career takes you.
Common mistakes when transferring research between institutions
Even experienced researchers stumble during institutional transitions. Here are the most frequent errors and how to avoid them:
1. Waiting until the last minute
Institutional IT departments typically deactivate accounts within days of your official departure. If you have not exported your data, references, and files before that cutoff, recovering them can be extremely difficult — sometimes impossible.
Fix: Start your data audit and export process at least eight weeks before your last day.
2. Assuming your reference manager is portable
Many researchers use institutional licenses for tools like EndNote or Mendeley. When you leave, you may lose access to premium features, cloud sync, or even your entire library if it was hosted on an institutional server.
Fix: Export your full reference library in open formats (BibTeX, RIS) before your access expires. Better yet, use a platform like ScholarDock where your library is tied to your personal account, not your institution.
3. Ignoring data ownership policies
Taking data you do not have the right to transfer can result in serious professional and legal consequences, including loss of funding eligibility and reputational damage.
Fix: Read your institution's data retention and IP policies. If in doubt, ask your Office of Research before copying anything.
4. Failing to document your research methodologies
Your future self — and your new colleagues — will thank you for clear documentation. Without it, even your own datasets become difficult to interpret six months later. Preserving your research methodologies, protocols, and analytical workflows in a structured, searchable format is just as important as preserving the data itself.
Fix: Create a methodology document for each active project. Include software versions, parameter choices, data sources, and any deviations from published protocols.
5. Losing track of collaborative authorship agreements
Verbal agreements about authorship made in the hallway rarely survive an institutional transition. When you are no longer physically present, it is easy for your contributions to be forgotten — or for expectations to shift.
Fix: Confirm authorship expectations in writing before you leave, and maintain regular communication with co-authors.
A practical timeline for transferring your research
To bring everything together, here is a week-by-week framework for a smooth research transition:
8–10 weeks before departure:
Audit all projects and classify by transfer priority
Read institutional data and IP policies
Begin conversations with PIs and collaborators
6–8 weeks before departure:
Initiate data transfer agreements for restricted data
Export reference library in multiple formats
Begin organizing and documenting project files
4–6 weeks before departure:
Back up all personal research materials to personal or new institutional storage
Transfer ownership of shared documents and project boards
Confirm authorship agreements in writing
2–4 weeks before departure:
Finalize handoff documents for projects you are leaving behind
Test that all exported references and data import correctly at your new institution
Set up communication channels with ongoing collaborators
Final week:
Verify all critical files are accessible from your new institution
Send a final summary email to each collaborator with status updates and next steps
Deactivate or clean up old institutional accounts
Your research should move with your career
Changing institutions should be an opportunity, not a setback. The researchers who transition smoothly are not the ones who work harder during the move — they are the ones who had their research organized and portable from the start.
If your research team is tired of scattered PDFs, disconnected notes, and the anxiety of losing years of work every time someone changes labs, ScholarDock brings your entire research workflow — sources, projects, references, and collaborators — into one connected workspace that travels with your career. No more exporting, re-importing, or rebuilding. Just continuous, organized research from one institution to the next.