How to Move Genealogy Research From Folders and Spreadsheets Into One Workspace
Migrate scattered genealogy files and spreadsheets safely, preserving sources and confidence while creating useful links between them.
Moving genealogy research into one workspace is a data-cleaning project, not a copy-and-paste sprint. The safe approach is to inventory what you have, choose a small representative branch, map old fields to the new structure, and keep the original collection untouched until the migration has been checked.
Define what “one workspace” means
One workspace does not have to mean one physical file. It means one reliable system of record in which people, relationships, events, sources, media, notes, maps, and research questions can be found and connected.
Decide which tool will be authoritative for each kind of information. A family history workspace might hold structured people and source links while preservation masters remain in managed storage. The workspace should still show where each file lives and what it supports.
Inventory before moving anything
List every location containing research: computer folders, external drives, cloud accounts, email attachments, spreadsheets, online trees, genealogy software, notebooks, and physical boxes. Record format, approximate size, owner, date range, duplicates, privacy level, and whether a backup exists.
Do not merge yet. The inventory exposes surprises such as two differently edited copies of a tree, a spreadsheet with source references missing from the main database, or photographs whose filenames have been shortened by a cloud export.
Make a read-only safety copy
Create a dated snapshot of the starting collection. Export native genealogy databases and GEDCOM copies, download spreadsheets in their original format and CSV, and copy associated media. Keep the snapshot separate from the working migration.
Write a short migration note identifying the source locations and date. If something later appears missing, you can return to a known baseline rather than guessing which copy was original.
Choose a pilot family
Select one small but representative branch: perhaps 20 people with certificates, census records, photographs, notes, and at least one uncertain relationship. Avoid starting with the easiest three names, because that will not test source citations, duplicates, conflicting dates, or media links.
Use the pilot to settle conventions for names, dates, place hierarchy, unknown values, source references, file links, and privacy. Document those decisions in a migration guide before scaling up.
Map spreadsheet columns to proper entities
A spreadsheet often combines several concepts in one row. Split them deliberately:
- a person’s name becomes a person record, retaining alternative spellings;
- birth, marriage, residence, and death become separate dated events;
- place text becomes a consistent place entry, preserving the wording used by the source;
- a URL or archive reference becomes a source citation;
- free-text comments become notes, not automatically facts;
- “father?” or coloured cells become an explicit uncertain relationship or research question.
Create a mapping table: old column, new destination, transformation rule, and example. This prevents different batches being interpreted differently.
Clean without erasing evidence
Standardise presentation while retaining original values. If a register says “Kirk Braddan” and a modern map says “Braddan,” keep the source transcription and use the standard place entry for searching. If a date is “about 1880,” do not convert it to 1 January 1880 simply to satisfy a date field.
Handle each of these explicitly:
- married and birth surnames;
- initials and aliases;
- calendar changes and partial dates;
- historic jurisdictions;
- uncertain parentage;
- same-name people;
- conflicting facts from different records.
Import in controlled batches
Where the destination supports GEDCOM or CSV import, test with a copy of the workspace. Review the import report and count people, families, events, notes, sources, and media before and after. App-specific data may not survive GEDCOM, so inspect examples rather than trusting the total person count.
Import one branch or source collection at a time. Label the batch in a migration log and resolve duplicates before the next batch. A giant import makes it difficult to identify which source created an error.
Reconnect files and citations
For every imported fact, ask “What is the evidence, and can I open it?” Repair broken media paths, link records to the people and events they support, and add citations that contain the repository, collection, reference, page or image, URL, and access date as appropriate.
Avoid attaching one census page only to the head of household. Link or cite it for each relevant person and event, while retaining the household context.
Turn loose notes into useful work
Classify notes as transcription, analysis, hypothesis, correspondence, story draft, or task. Convert unresolved comments into explicit questions. Add negative searches to a research log. Keep old notes until you have confirmed that their meaning has been represented; “tidying” can otherwise destroy valuable reasoning.
Validate the pilot
Compare the pilot workspace against the original:
- Are all people and relationships present?
- Do dates retain uncertainty and precision?
- Can every cited media file be opened?
- Are sources distinguishable from repositories and individual citations?
- Did private living-person data remain restricted?
- Can a useful report, timeline, or GEDCOM be exported?
- Does another family member understand the result?
Correct the migration guide, reset the pilot if necessary, and repeat until the process is dependable.
Scale up and close the old system carefully
Migrate the remaining collection in logged batches. Reconcile counts and sample records after each one. When complete, keep the original snapshot as a read-only archive and mark old working folders clearly so research does not continue in two places.
The migration is finished when the new workspace is not merely fuller, but trustworthy: evidence opens, uncertainty survives, searches are not duplicated, and a relative can follow the reasoning without access to your old filing habits.