LineagePress GEDCOM Import Guide

Quick Start

1. Create a Tree First

  • Go to LineagePress → Trees → Add New Tree.
  • Enter a Tree ID (alphanumeric, no spaces).
  • Enter a Tree Name.
  • Click Save.

2. Import Your GEDCOM

  • Go to LineagePress → Import.
  • Click “Choose File” and select your .ged file.
  • Select your destination tree.
  • Choose the desired import mode (see below for details).
  • Click “Next“.

3. Monitor Progress

  • Watch the progress bar.
  • The import runs automatically in chunks.
  • Do not close the browser window until complete.

4. Review Results

  • Check the import summary.
  • Review any errors or warnings.
  • View your newly imported tree data.

Import Modes

ModeBest ForBehavior Notes
Update Tree (Recommended)Regular updates, preserving manual edits.Fills empty fields only, keeps existing data intact.Safest option for ongoing maintenance.
Replace TreeStarting fresh, major corrections.Deletes ALL existing data first, then imports everything from scratch.⚠️ WARNING: Cannot be undone. Use for a clean slate.
Add OnlyMerging data, avoiding duplicates.Only adds new records, skips existing records completely.Never modifies existing data. Use for combining multiple GEDCOM files.

Event Handling

SettingStatusDescription
Import Custom Events CheckedImports specialized event types from your genealogy software.
UncheckedOnly imports standard GEDCOM events.
Import All Events Checked (Recommended)Imports all event data.
UncheckedSkips all event data.

Advanced Options

Media Handling

  • Do not import media: Skips all media references.
  • Import media links only: Imports references but not the actual files (Recommended).

Performance Settings

SettingOptionsEffect
Processing Chunk Size5,000 linesConservative (slower, more stable).
10,000 linesBalanced (Recommended).
15,000 linesMaximum performance (faster, requires good server).
Smart Import Optimization Enabled (Recommended)Automatically adjusts chunk sizes up to 25,000 lines based on server performance.
DisabledUses fixed chunk size only.

Import Speed & File Size Guidelines

⚠️ Important: These are conservative estimates based on average shared hosting (2GB RAM). Your actual times may be 2-3x faster on dedicated servers or VPS hosting.

File SizeRecordsIndividualsFamiliesImport Time (Est.)Recommended Settings
Small Imports (Fast)
100 KB100–20050–10020–4010–20 secondsDefault
1 MB1,000–1,500500–750200–3001–2 minutesDefault
Medium Imports (Moderate)
5 MB5,000–7,0002,500–3,5001,000–1,4005–8 minutesDefault
10 MB10,000–12,0005,000–6,0002,000–2,50010–15 minutesSmart Optimization
Large Imports (Slower)
20 MB20,000–25,00010,000–12,5004,000–5,00020–30 minutes15K Chunk + Smart
50 MB50,000–60,00025,000–30,00010,000–12,00050–75 minutes15K Chunk + Smart
Very Large Imports (Contact Support)
100 MB+100,000+50,000+20,000+2+ hoursContact support

Character Encoding & Special Characters

⚠️ Best Practice: Fix Encoding BEFORE Import

While LineagePress has a built-in character encoder, ensuring your GEDCOM file uses UTF-8 encoding before importing is the most reliable way to prevent potential issues with special characters.

Common Encoding Issues

  • Accented characters (é, ñ, ü) appear as “ or ?.
  • Non-English names or special symbols are corrupted.

How to Fix Encoding

OptionMethodDetails
1. Export as UTF-8 (Recommended)Use your genealogy software’s export options.Select “UTF-8” or “Unicode” when creating the GEDCOM file.
2. Convert with Text EditorUse a code editor like Notepad++ (Windows) or TextEdit (Mac).Open the file, go to the Encoding menu, and select “Convert to UTF-8.”
3. Verify EncodingOpen the GEDCOM file in a text editor and check the header:The header should be 1 CHAR UTF-8. If it says ANSEL, ANSI, or ASCII, it needs to be converted.

GEDCOM Version Support

LineagePress automatically handles the following conversions transparently:

  • GEDCOM 5.5 / 5.5.1: Automatically migrated to 7.0 format upon import.
  • GEDCOM 7.0: Direct import (fastest).

Troubleshooting

ProblemCause & Solution
Import Fails ImmediatelyCheck: File is valid .ged format, a Tree is selected, and encoding is UTF-8. Try: Smaller chunk size (5,000).
Import Stalls/FreezesCheck: Server timeout settings. Try: Disable Smart Optimization or reduce Chunk Size.
Missing DataCheck: Import mode (did you use Update Tree when you meant to use Replace Tree?). Review: Import warnings/errors.
Duplicate RecordsCause: Multiple imports were run using the “Add Only” mode. Solution: Use “Replace Tree” to wipe and start fresh.
Memory ErrorsTry: Smallest chunk size (5,000) or disable Smart Optimization. Contact: Hosting provider to increase PHP memory limit (recommended 256MB).

Best Practices

Before Import

  1. ✅ Backup your database.
  2. ✅ Convert GEDCOM to UTF-8 encoding (prevents character issues).
  3. ✅ Create a test tree first.
  4. ✅ Validate your GEDCOM file in your genealogy software.
  5. ✅ Verify GEDCOM header shows 1 CHAR UTF-8.

During Import

  1. Keep the browser window open.
  2. Do not navigate away or refresh the page.
  3. ✅ Monitor the progress bar.

After Import

  1. ✅ Review the import summary.
  2. ✅ Check for errors/warnings.
  3. ✅ Verify key records for accuracy.
  4. ✅ Run post-import utilities (if available).

Performance Tips

GoalRecommendations
For Large Files (> 20 MB)1. Enable Smart Import Optimization. 2. Use 15,000 chunk size. 3. Import during low-traffic hours. 4. Ensure adequate server resources.
For Slow Servers1. Use 5,000 chunk size. 2. Disable Smart Optimization. 3. Consider splitting large GEDCOMs.
For Maximum Speed1. Use GEDCOM 7.0 format (avoids migration). 2. Enable Smart Optimization. 3. Use 15,000 chunk size. 4. Ensure PHP memory limit 256MB.

Common Questions

QuestionAnswer
How long does import take?It varies: Small (< 1 MB): 10 seconds – 2 minutes. Medium (1–10 MB): 2–15 minutes. Large (10–50 MB): 20–75 minutes. See table above for benchmarks.
Can I import multiple GEDCOM files?Yes, use “Add Only” mode for subsequent imports to combine data and avoid duplicates.
Can I undo an import?No. Always backup first. Use “Replace Tree” to re-import if necessary.
What happens if import is interrupted?Partial data may be imported. Use “Replace Tree” to start fresh.
Why is my import slow?Check server resources, reduce chunk size, or disable Smart Optimization.
Do I need to convert GEDCOM 5.5 to 7.0 first?No, LineagePress automatically handles the migration.
My names with accents (é, ñ, ü) are showing as or ?This indicates an encoding issue. Convert your GEDCOM file to UTF-8 before importing.

Support

If you encounter issues:

  1. Check this guide and review error messages.
  2. Try importing with a smaller test file.
  3. Check server error logs for PHP or timeout issues.
  4. Contact support with the following details:
    • File size and GEDCOM version
    • Specific error messages encountered
    • Your server specifications (hosting type, PHP memory limit)
    • Import settings used (Chunk Size, Import Mode, Smart Optimization status)
Powered by LineagePress
Scroll to Top