Gramps - User contributions [en]

User:ErickLedger

2026-03-24T00:25:24Z

ErickLedger: lack of time.

Eric
* Husband
* Father
* Grandfather

Occasionally edit the [[User manual]] and general wiki when time allows.

Thank you to the whole Gramps [[Team|team]] and all the volunteers who have made this great genealogy program and continue to improve and support it.

[[Category:User|E]]

User talk:ErickLedger

2025-11-12T21:24:41Z

ErickLedger:

Remember to use template {{man version} (})

Add a witness

2025-11-12T08:53:48Z

ErickLedger: /* Alternative: don't create a person */

{{languages|Add a witness}}

How to add a witness to an event.

[[File:Highlight-witness-role-dropdown-event-reference.editor51.png|right|thumb|450px|Highlighted - "Witness" role in dropdown from Event Reference Editor and highlighted {{man button|Share an existing event}} button on Event tab of Edit Person.]]

== Create the witness as person ==
We strongly suggest to add the witness related to the persons in your family tree. So go to the {{man label|People category view}}, and add them. In many cases, the only information you have of that the person is his name, and a date on which he was certainly alive.

== Create the event ==
Start by creating the event that will have a '''''Witness''''' '''[[Gramps_Glossary#role|Role]]''' in addition to the default Roles. The Witness will hold a secondary ([[Gramps_Glossary#sharing|shared]]) role for the event but the primary Roles for the event should be defined first.

(By default, a ''Marriage'' event is added in the Family Editor and has a ''Family'' default role, meaning that both spouses of that family hold primary roles in the event. Meanwhile, the record about the filing of a ''Will'' event is added in the Person Editor for the ''testator'' and holds a ''Primary'' role by default.)

{{man note|Event Roles are easy to change|Events shared via drag'n'drop from the Clipboard will default to ''Unknown''. Those shared from the Object Selector will have a ''Primary'' or ''Family'' role. The Role can be changed from the default at the top of the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]}}.}}

{{-}}

== Add all people to the marriage event ==
Now, share this same event with the witness if this person is in the family tree. However, assign that person a "witness" role in the event.

You can do this by selecting the witness from the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People category view]]}},

[[File:PeopleTreeView-GroupedPeople-example-with-context-menu-60.png|right|thumb|450px| People Category - Tree View - Grouped People]]

{{-}}
then in the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Edit_Person_dialog|person editor]]}} select the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Edit_Person_tab_pages|Events]]}} tabs, and select {{icon|share}}{{man button|Share an existing event}}.

[[File:EditPerson-Events-tab-example-50.png|right|thumb|450px| "Events" tab from "Edit Person" - dialog - example]]

{{-}}
From the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Select_Event_selector|Select Event selector]]}} chose the event you just created,

[[File:SelectEvent-selector-dialog-example-60.png|thumb|right|450px|Select Event - selector - example]]
{{-}}
and in the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]}} set the {{man label|Role}} to ''Witness'' from the dropdown list.

[[File:EventReferenceEditor-dialog-default-52.png|right|thumb|450px| Event Reference Editor - dialog - default]]
{{-}}
The event is now a shared event.
{{-}}

== Alternative: don't create a person ==
Some people are averse to adding people to their family tree that they only have a name of. First, allow us to point out why you should nevertheless make a person:
* Gramps supports this
* You might encounter the same person again in your research. Having them in the person view increases the likely-hood of you recognizing it is the same person as the one that appears as witness.
* The ''[[Gramps_6.0_Wiki_Manual_-_Tools#Find_Possible_Duplicate_People|Find Possible Duplicate People]]'' tool has more information to work with.

If you nevertheless want to record the witness, without creating a person, use the attribute tab of the event instead. You can add to the event in the attribute tab, the attribute of type ''witness'', and with as value the name.

Alternatively, you can just record this information in a note attached to the event.

== See also ==
*[[Add a child]]
*[[Add a spouse]]
*[[Add a godfather-godmother]]
*[[Adding existing people to Family]]

[[Category:How do I...]]

Add a witness

2025-11-12T08:51:54Z

ErickLedger: /* Alternative: don't create a person */

{{languages|Add a witness}}

How to add a witness to an event.

[[File:Highlight-witness-role-dropdown-event-reference.editor51.png|right|thumb|450px|Highlighted - "Witness" role in dropdown from Event Reference Editor and highlighted {{man button|Share an existing event}} button on Event tab of Edit Person.]]

== Create the witness as person ==
We strongly suggest to add the witness related to the persons in your family tree. So go to the {{man label|People category view}}, and add them. In many cases, the only information you have of that the person is his name, and a date on which he was certainly alive.

== Create the event ==
Start by creating the event that will have a '''''Witness''''' '''[[Gramps_Glossary#role|Role]]''' in addition to the default Roles. The Witness will hold a secondary ([[Gramps_Glossary#sharing|shared]]) role for the event but the primary Roles for the event should be defined first.

(By default, a ''Marriage'' event is added in the Family Editor and has a ''Family'' default role, meaning that both spouses of that family hold primary roles in the event. Meanwhile, the record about the filing of a ''Will'' event is added in the Person Editor for the ''testator'' and holds a ''Primary'' role by default.)

{{man note|Event Roles are easy to change|Events shared via drag'n'drop from the Clipboard will default to ''Unknown''. Those shared from the Object Selector will have a ''Primary'' or ''Family'' role. The Role can be changed from the default at the top of the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]}}.}}

{{-}}

== Add all people to the marriage event ==
Now, share this same event with the witness if this person is in the family tree. However, assign that person a "witness" role in the event.

You can do this by selecting the witness from the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Categories#People_Category|People category view]]}},

[[File:PeopleTreeView-GroupedPeople-example-with-context-menu-60.png|right|thumb|450px| People Category - Tree View - Grouped People]]

{{-}}
then in the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Edit_Person_dialog|person editor]]}} select the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Edit_Person_tab_pages|Events]]}} tabs, and select {{icon|share}}{{man button|Share an existing event}}.

[[File:EditPerson-Events-tab-example-50.png|right|thumb|450px| "Events" tab from "Edit Person" - dialog - example]]

{{-}}
From the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Select_Event_selector|Select Event selector]]}} chose the event you just created,

[[File:SelectEvent-selector-dialog-example-60.png|thumb|right|450px|Select Event - selector - example]]
{{-}}
and in the {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Event_Reference_Editor_dialog|Event Reference Editor]]}} set the {{man label|Role}} to ''Witness'' from the dropdown list.

[[File:EventReferenceEditor-dialog-default-52.png|right|thumb|450px| Event Reference Editor - dialog - default]]
{{-}}
The event is now a shared event.
{{-}}

== Alternative: don't create a person ==
Some people are averse to adding people to their family tree that they only have a name of. First, allow us to point out why you should nevertheless make a person:
* Gramps supports this
* You might encounter the same person again in your research. Having them in the person view increases the likely-hood of you recognizing it is the same person as the one that appears as witness.
* The ''Find Duplicates'' tool has more information to work with.

If you nevertheless want to record the witness, without creating a person, use the attribute tab of the event instead. You can add to the event in the attribute tab, the attribute of type ''witness'', and with as value the name.

Alternatively, you can just record this information in a note attached to the event.

== See also ==
*[[Add a child]]
*[[Add a spouse]]
*[[Add a godfather-godmother]]
*[[Adding existing people to Family]]

[[Category:How do I...]]

Addon:Life Line Chart View

2025-11-11T03:54:53Z

ErickLedger: /* On main Gramps Toolbar */

{{languages|Addon:Life Line Chart View}}
{{Third-party addon}}
[[File:LifeLineChartViewScreenshot1-51.png|450px|thumb|right|Life Line Chart View - addon - Visualizing an ancestors tree (Gramps 5.1.x version)]]
[[File:LifeLineChartViewScreenshot2-51.png|450px|thumb|right|Life Line Chart View - addon - Visualizing a descendant tree with photos (Gramps 5.1.x version)]]
[[File:LifeLineChartViewScreenshot3-51.png|450px|thumb|right|Life Line Chart View - addon - Visualizing a larger ancestor tree (Gramps 5.1.x version)]]
[[File:LifeLineChartViewScreenshot4-51.png|450px|thumb|right|Life Line Chart View - addon - Visualizing a ancestor tree with photos (Gramps 5.1.x version)]]
[[File:LifeLineChartViewScreenshot6-51.png|450px|thumb|right|Life Line Chart View - addon - Visualizing a descendant tree in cactus shape (Gramps 5.1.x version)]]

'''Life Line Chart Views''' are two interactive {{icon|ance}} [[Gramps Glossary#charts view|{{man label|Charts}}]] category view addons which shows individuals as lines in an either an ancestor or descendant chart. The length and position of the line depends on the actual life span and the marriages. The pedigree/ancestor collapse is handled. Labels for birth / names, death, and marriages can be added.

The active person is the starting point on both charts. Birth/christening/baptism, death/burial, and marriage dates need to be available to properly draw this chart. If they are incomplete reasonable guess values are chosen if possible. If not, then these individuals are not shown.

== Usage ==

If the addon was loaded successfully and the [[Addon:Life_Line_Chart_View#Prerequisites|prerequisites]] have been installed two new chart icons will appear [[File:LifeLineChartView-default-toolbar-icons-60.png|240px]] in the {{icon|ance}} {{man label|Charts}} category view tool bar.
* [[#Life_Line_Ancestor_Chart_View|Life Line Ancestor Chart View]] (left icon)
* [[#Life_Line_Descendant_Chart_View|Life Line Descendant Chart View]] (right icon)

In general the Life Line Chart Views can be:

* '''Configured independently''' using the [[Addon:Life_Line_Chart_View#Configure_Options|Configure the active view]] dialog.

* You may zoom (if the chart is focused) with
** {{man key press|Ctrl|+}} and {{man key press|Ctrl|-}}
** {{man key press|Ctrl|mouse wheel}}
** the GUI control buttons (+, -, fit to view, reset to 1)

* Scrolling is possible (if the chart is focused) with
** {{man key press|mouse wheel}}, {{man key press|shift|mouse wheel}}
** {{man key press|Ctrl|left mouse button}} (grabbing)

* Context menu enables
** Opening the edit dialog
** Change active person
** Show / hide persons and their ancestors / descendants
** Showing siblings in the ancestor chart

* You may lock {{man key press|Ctrl}} with the GUI control button "M"
* You may also use the filter to fade out individuals
* A tooltip shows the name, gramps id, birth and death date of the person.

* Photos of the persons can be displayed along the line. Their position is either based on the date that is set in the media object, or displayed in the order of appearance in the family tree.
* Overview map on the bottom left.
* The chart diagram can be exported as an SVG file using the {{man button|Save the Life Line Chart View}} button.
* Layout optimization algorithms.
* Dark theme.
* Handling of [https://en.wikipedia.org/wiki/Pedigree_collapse pedigree collapse].

{{-}}
===Life Line Chart View Toolbars===
The Life Line Chart Views toolbars are identical in options and usage:
==== Control Toolbars ====
The Life Line Chart Views have a two small toolbars as well as the decade grid and overview map of its own with the following options:

[[File:LifeLineChart-View-addon-top-toolbar-overview-60.png]]

;'''Top Life Line Chart View toolbar''':{{man button|Hand (grabber)}}, {{man button|'''+''' (Zoom in)}}, {{man button|'''-''' (Zoom out)}}, {{man button|'''1''' (Zoom to Original)}}, {{man button|'''☐''' (Zoom to best fit)}}, {{man button|Rebuild data cache}}, {{man button|'''-><-''' (Revert the placement and person selection)}}, {{man button|[Person/data/id and cursor position readout]}}, {{man button|'''?''' (Help)}}.

;'''Zoom sidebar''':Vertical Slider, ranging from 0.01x to 10.00x. On the left side.

;'''Timeline sidebar''':Decade grid. On the right side.

;'''Overview map''':(aka mini map). On the bottom left of the chart.

{{-}}

==== On main Gramps Toolbar ====
On the main Gramps Toolbar you also have:
* {{man button|'''⤓'''(Save the Life Line Chart View)}} button that allows you to save the currently displayed Chart into a SVG (*.svg) format file for later printing.
* [[File:Gramps-config.png|34px]] [[#Configure_Options|Configure the active view]] with options shown in that section.

=== Life Line Ancestor Chart View ===
Shows individuals as lines in an ancestor chart.

{{stub}}
{{-}}

=== Life Line Descendant Chart View ===
Shows individuals as lines in an descendant chart.
{{stub}}
{{-}}

=== Configure Options ===

[[File:LifeLineChartView-addon-Configure-dialogs-51.png|450px|thumb|right|Life Line Chart View - addon - Configure dialog (Gramps 5.1.x version)]]

The Configure the active view dialog shows two tabs of option that you can '''configure independently''' for the charts:
* [[#General_Layout|General Layout]]
* [[#Label_Configuration|Label Configuration]]

==== General Layout ====

* number of generations.
* relative line width.
* vertical and horizontal chart size.
* warping of the whole chart (normal grid, sine, triangle).
* show or hide pedigree collapse.
* unique line color or coloring based on surname.
* line fading represents the uncertainty of dates or the age.
* show or hide labels for birth, death, marriages.
* line weighting (only descendant diagram).
* general chart layout "parents enclose children" or "cactus" (only descendant diagram).
* optimizations (only ancestor diagram):
** flip family to reduce the cross chart connection lengths.
** horizontal chart compression.
* softness of the family shape.
* vertical flipping of the whole chart.
* show photos of the person on the line.
* size of the photos.

To return to defaults use the {{man button|Reset all settings}} button.

==== Label Configuration ====
* marriage label font size and name.
* birth and death label.
** position.
** rotation.
** alignment.
** word wrapping.
** font name and size.

To return to defaults use the {{man button|Reset all settings}} button.

== Prerequisites ==

This addon requires the following two Python modules be installed:

* life_line_chart
* svgwrite

===Semi-automatic download ===
Gramps 5.1 supported semi-automatic download '''If the requirements for this addon have not already been installed you will be prompted to download them semi-automatically by selecting the {{man button|Download module}} button for each.'''

The addon is based on the Python module [https://pypi.org/project/life-line-chart life_line_chart], this Python module is required.

[[File:LifeLineChartView-life line chart.png]]

To enable SVG file export, the module ([https://pypi.org/project/svgwrite svgwrite]) is required (which has a minimum requirement of Python 3.6).

[[File:LifeLineChartView-svgwrite.png]]

{{man warn|For Gramps 5.2 and older|To enable SVG file export use the minimum requirement of Python 3.6 for svgwrite [[#Prerequisites|prerequisite]]}}

== Issues ==
* Unable to be installed on Gramps 6.x Windows AIO due to pip issue win (Workaround use gpr file from Gramps 5.1 and modify the version number to 6.0 you will be offered the option buttons to semi-automatically install the modules as shown in prerequisites section) 
* "smooth scrolling" is supported since GTK 3.24 ([https://docs.gtk.org/gtk3/class.EventControllerScroll.html GTK documentation]), the Gramps 6.0.x Windows AIO uses version 3.24.+ .

For current issues see the related tag [https://gramps-project.org/bugs/tag_view_page.php?tag_id=372 LifeLineChartView] on the bugtracker.


[[Category:Views]]
[[Category:Addons]]
[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Prerequisites|L]]

Gramps 6.0 Wiki Manual - Error and Warning Reference

2025-11-03T08:36:57Z

ErickLedger: /* Warning button */ Copy {{man button|💡 Warning}} here also

{{man index|Gramps 6.0 Wiki Manual - User Directory|Gramps 6.0 Wiki Manual - Further References|6.0}}
{{languages|Gramps 6.0 Wiki Manual - Error and Warning Reference}}
{{#vardefine:chapter|E}}
{{#vardefine:figure|0}}
This section explains what to do when something unexpected happens.

== When something goes wrong ==

Sometimes something goes wrong, either because you have asked to do something that Gramps doesn't know how to do, or because something has happened that the developers of Gramps did not anticipate, or because there is a mistake in the coding of Gramps.

{{man warn| Not all errors and warnings are obvious |Sometimes all the errors do not appear on the screen. If something unexpected happens, you may need to dig a little deeper to see all the error messages in the [[Gramps_6.0_Wiki_Manual_-_Error_and_Warning_Reference#Seeing_all_the_error_messages|Gramps.log file]].}}

== Alerts ==

An alert is a dialog that appears when Gramps needs to give you an important message about an error condition or warn you about potentially hazardous situations or consequences.

Most alerts are self explanatory, and the same type of alerts that you might get with any application. These are not discussed further here.

However, some alerts require more complicated actions, so they are described below.
{{-}}
=== Abort changes?===
[[File:Abort-changes-dialog-60.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Abort changes?" dialog]]

The {{man label|Abort changes?}} dialog is shown when you select menu {{man menu|[[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#Saving_changes_to_your_Family_Tree|Family Trees ->Abandon Changes and Quit.]]}} you can use the {{man button|Cancel}} button to continue your editing session or {{man button|Abort changes}} button to return the family tree to the state it was before you started the editing session.

{{-}}

=== Are you sure you want to upgrade this Family Tree?===

[[File:AreYouSureYouWantToUpgradeThisFamilyTree-dialog-DbUpgradeRequiredError-example-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Are you sure you want to upgrade this Family Tree?" dialog - Db Upgrade Required - example]]

[[File:AreYouSureYouWantToUpgradeThisFamilyTree-dialog-BsddbUnsupported-example-52.png|350px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Are you sure you want to upgrade this Family Tree?" dialog - BSDDB conversion - example]]

[[File:AreYouSureYouWantToUpgradeThisFamilyTree-dialog-BsddbUpgradeRequiredError-example-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Are you sure you want to upgrade this Family Tree?" dialog - BSDDB Upgrade Required Error - example]]

[[File:AreYouSureYouWantToDowngradeThisFamilyTree-dialog-BsddbDowngradeRequiredError-example-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Are you sure you want to downgrade this Family Tree?" dialog - BSDDB Downgrade Required Error - example]]

[[File:AreYouSureYouWantToUpgradeThisFamilyTree-dialog-PythonUpgradeRequiredError-example-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Are you sure you want to upgrade this Family Tree?" dialog - Python Upgrade Required Error - example]]

These dialogs appear for the listed reasons:
* "Db Upgrade Required" - If you try to open a Db(Sqlite3) Family Tree created with a previous older version of Gramps with a newer version of Gramps.
* "BSDDB Upgrade Required Error" - superseded [[Gramps_Glossary#bsddb|BSDDB]] database Family must be converted to a current Database engine (typically SQLite) for Gramps.
* "BSDDB Upgrade Required Error" - If you try to open a BSDDB Family Tree created with a previous older version of Gramps with a newer version of Gramps.
* "BSDDB Downgrade Required Error" - If you try to open a BSDDB Family Tree created with a previous older version of BSDDB with a newer version of BSDDB.
* "Python Upgrade Required Error" - If you try to open a BSDDB Family Tree created with a previous older version of Gramps using Python 2 with a newer version of Gramps that uses Python 3.

For each of these reasons you may follow the same general advice; if you still have the older version of Gramps available, then you should:
* {{man button|Cancel}} this dialog, and exit Gramps
* Open the Family Tree with the previous version of Gramps (Reinstall the old version of Gramps),
* Export your family tree in [[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#Gramps_XML_.28family_tree.29_export|Gramps XML (family tree) export]] format or [[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#Gramps_XML_Package_.28family_tree_and_media.29_export|Gramps XML Package (family tree and media)]] format,
* Exit the old version of Gramps and Start the new version of Gramps,
* Open the Family Tree in the new version of Gramps and click the {{man button|I have made a backup, please upgrade my Family Tree}} button in this dialog
{{-}}

=== Error parsing arguments ===

[[File:ErrorParsingArguments-dialog-DatabaseIsLocked-example-50.png|thumb|right|346px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}}Error parsing arguments - dialog - Database is locked example]]
The Family Tree database is locked while in use by another user or because Gramps exited abnormally during previous use.

See [[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#Unlocking_a_Family_Tree|Unlocking a Family Tree]]
{{-}}

=== Database is locked. cannot open it! ===
The Family Tree database is locked while in use by another user or because Gramps exited abnormally during previous use.

See [[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#Unlocking_a_Family_Tree|Unlocking a Family Tree]]
{{-}}

=== Cannot open database ===

[[File:Cannot_open_database-40.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Dialogue showing DB Environment Error]]

[[File:DbVersionError-40.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Dialogue showing DB Version Error]]

As explained in the dialogue, the Family Tree was probably created with an old version of the Berkeley database program. This is not quite the same thing as an old version of the Gramps program, because the version of the Gramps program and the version of the Berkeley database are independent. However, the effect is somewhat the same. As suggested in the dialogue, if you have the old version of Gramps and its support software, then you should:
* cancel this dialogue,
* open the Family Tree with the previous version of Gramps,
* export your family tree in Gramps XML database export format or Gramps package export format (see [[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#Export_into_Gramps_formats|Export into Gramps formats]]),
* start the new version of Gramps,
* open the 'Manage Family Tree' dialogue,
* click on {{man button|new}} and create a new Family Tree,
* load the new Family Tree
* Import the Gramps XML or Gramps package.

Alternatively, it may be possible to use the recovery tools. See 'obtain the bsddb recovery tools' under [[Recover corrupted family tree]]
{{-}}

== Low level database corruption detected ==
[[File:LowLevelDatabaseCorruptionDetected-dialog-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Low level database corruption detected" dialog - example]]

This dialogue appears when a problem is detected with the underlying database that supports Family Trees.
* close the dialogue,
* click on the Family Tree Manager,
* select the Family Tree you were trying to open,
* the {{man button|Repair}} button should be available; click on it,
* once the Family Tree has been repaired it should be possible to open it in the normal way.

If this does not work, try 'obtain the bsddb recovery tools' under [[Recover corrupted family tree]]
{{-}}

=== Error detected in database ===
[[File:RunDatabaseRepair-40.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Dialogue showing Run Database Repair]]

Carry out suggested action.
{{-}}

== Warnings ==

If Gramps detects a minor error, or wishes to notify you about an occurrence within the program, then Gramps may display a {{man button|💡 Warning}} button on the status bar, as shown below. This button is only displayed for 180 seconds, so if you see it you should immediately click on it if you want to see the messages.
===Warning button ===
[[File:Status-bar-warning-button-60.png|650px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Gramps Main Window showing Warning button on the Status bar]]
The {{man button|💡 Warning}} button (light bulb icon)
{{-}}

=== Gramps Warnings dialog ===
[[File:Gramps-warnings-dialog-example-60.png|650px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Gramps Main Window showing Warning message and context menu]]

If you click the {{man button|💡 Warning}} button, then a {{man label|Gramps Warnings}} dialog box appears showing the last 20 messages received.

You may use the context menu to copy the details to a text file.

See [[Logging_system|More details about the Logging system]]
{{-}}

Some of the warnings that may appear are described below:

=== Locale warnings ===

Sometimes there is a problem with the language you have chosen.

If you have installed Gramps using your platform's standard installation method (Package manager/AIO installer/Application package) and are using your platform's built-in mechanism (System Setting/Control Panel/System Preferences) to choose the language/sort order/formats you are running in, then these errors should not occur, and may mean there is a problem in Gramps.

However, if you have set the language/sort order/formats manually by setting the 'environment' see [[Gramps_6.0_Wiki_Manual_-_Settings#Language| languages]], particularly if you are running Gramps from the command line, then there may be a problem with what you have typed in. The message (only part of which is shown below) should help you to understand where the error is.

* "Date parser for '%s' not available, using default"
* "Date displayer for '%s' not available, using default"
* "Family relationship translator not available for language '%s'. Using 'english' instead."
* 'Unable to determine your Locale, using English'
* "Localization library libintl not on %PATH%, localization will be incomplete"
* "No translations for %s were found, setting localization to U.S. English"
* "Unable to create collator: %s"
* "No language provided, using US English"
* "No usable languages found in list, using US English"
* "None of the requested languages (%s) were available, using %s instead"

=== Module not loaded warnings ===

The Gramps application contains many different 'modules'. Some of these modules are required for Gramps to run at all; some are 'strongly recommend', and some are optional.

If you have installed Gramps using your platform's standard installation method (Package manager/AIO installer/Application package) then the builder of that package will have decided which modules are present. He must include all the required modules, because otherwise Gramps will not run, but he can choose which of the recommended and optional packages he includes. Consult the documentation for your package to determine which modules are included.

If you try to do something that needs a module that is not included, then you will get a warning like the ones below (only the first part of the message is included). What you can do about it depends on your platform:

'''Linux'''
You should be able to install the package using your distribution's standard Package Manager or the GUI interface to the Package Manager. However, in some cases you will need to build the module from source.

'''MS Windows and macOS'''
The MS Windows AIO installer and the macOS Application bundle come with certain modules built in. It is not possible for the normal user to add further modules. Therefore, if you find a module that you particularly feel should be included you should post on the Gramps [[Contact#Official|Forum]] (probably the Development section) explaining why you feel its omission is a mistake.

* "WARNING: PIL module not loaded. "
* "ICU not loaded because %s. Localization will be impaired. "
* "OsmGpsMap module not loaded. "
* "GExiv2 module not loaded. "
* "Webkit module not loaded. "
* "PIL (Python Imaging Library) not loaded. "
* "GtkSpell not loaded. "



====Show plugin status dialog on plugin load error====

Allows showing dialog following the [[Gramps_Glossary#plugin|Plugin]] Registration process as Gramps starts. The dialog reports plugins that cause an error during registration. This allows users to find and resolve plugin problems.

The dialog can be suppressed from {{man label|Show plugin status dialog on plugin load error.}} option in the {{man label|[[Gramps_6.0_Wiki_Manual_-_Settings#Warnings|Warnings]]}} tab of the {{man menu|Edit -> Preferences}} dialog.

The error conditions that would trigger the plugin error status dialog are primarily handled in the `load_plugin` function of the `PluginManager` class. Here are the main error conditions:

1. Plugin Registration File Errors:
* Missing or invalid gramps_target_version ([https://github.com/gramps-project/gramps/blob/maintenance/gramps52/gramps/gen/plug/_manager.py#L1050-L1056 gen/plug/_manager])
* Incorrect plugin version format ([https://github.com/gramps-project/gramps/blob/maintenance/gramps52/gramps/gen/plug/_manager.py#L1058-L1062 gen/plug/_manager])
* Missing required attributes for the specific plugin type ([https://github.com/gramps-project/gramps/blob/maintenance/gramps52/gramps/gen/plug/_manager.py#L1064-L1068 gen/plug/_manager])
2. Module Import Errors:
* The plugin's main Python file cannot be imported ([https://github.com/gramps-project/gramps/blob/maintenance/gramps52/gramps/gen/plug/_manager.py#L1070-L1074 gen/plug/_manager])
3. Plugin Initialization Errors:
* Exceptions raised during the plugin's initialization process ([https://github.com/gramps-project/gramps/blob/maintenance/gramps52/gramps/gen/plug/_manager.py#L1076-L1080 gen/plug/_manager.py])
4. Version Incompatibility:
* The plugin's gramps_target_version does not match the running Gramps version ([https://github.com/gramps-project/gramps/blob/maintenance/gramps52/gramps/gen/plug/_manager.py#L1082-L1086 gen/plug/_manager])
5. Duplicate Plugin IDs:
* Multiple plugins with the same ID are detected ([https://github.com/gramps-project/gramps/blob/maintenance/gramps52/gramps/gen/plug/_manager.py#L1088-L1092 gen/plug/_manager])
6. Invalid Plugin Type:
* [[Addons_development#Create_a_Gramps_Plugin_Registration_file|PTYPE]] specified is not recognized ([https://github.com/gramps-project/gramps/blob/maintenance/gramps52/gramps/gen/plug/_manager.py#L1094-L1098 gen/plug/_manager] and [https://github.com/gramps-project/gramps/blob/maintenance/gramps52/gramps/gui/viewmanager.py#L615-L618 gui/viewmanager])

=== Configuration warnings ===

{{stub}}

Sometimes it is worth just deleting the old configuration files.

* "Importing old key file 'keys.ini'..." (The <code>.gramps/keys.ini</code> file was deprecated in Gramps 3.2, now <code>.gramps/gramps{{Stable_branch}}/gramps.ini</code> )
* "Done importing old key file 'keys.ini'"
* "Can't find filter %s in the defined custom filters"
* "Number of arguments does not match number of " +
* "Value '%(val)s' not found for option '%(opt)s'"
* "Unable to open recent file %s because %s",
* "WARNING: ignoring old key '%s'"
* "WARNING: ignoring key with wrong type "
* "Failed to parse doc options"
* "Skipped a line in the addon listing: "
* "Failed to load gramplets from %s because %s"

===Other warnings ===
{{stub}}
{{-}}

====Place cycle detected dialog====
[[File:PlaceCycleDetected-warning-dialog-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Place cycle detected" warning dialog]]

"Place cycle detected" warning dialog indicated that "The place you are adding is already enclosed by " "this place"

See also:
* [[Gramps_6.0_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Enclosed_By|Enclosed By]]
{{stub}}
{{-}}

====Missing Media dialog====
If a media file is not found during export, you will see the same Missing Media dialog.

{{stub}}

====Could not open file: <file path and file name>====

[[File:Could-not-open-file-file-path-and-file-name-warning-dialog-example-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Could not open file: <file path and file name>" - (Warning window)]]

In the [[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#Import_Family_Tree_dialog|Import_Family_Tree_dialog]] if you select the '''All files''' option and then select an unsupported file import type you will be shown the '''Could not open file: <file path and file name>''' warning dialog.

The message show mentions:
<hr>
File type "xxx" is unknown by Gramps.

Valid types are: Gramps database, Gramps XML, Gramps package, GEDCOM, and others.

{{man button|Close}}

{{stub}}
{{-}}

====Cannot save person====
[[File:CannotSavePerson-dialog-51.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Cannot save person (Warning window)]]
Attempting to save a person without any data from the Person editor displays this warning popup. You need at least one letter for the first name.

'''Cannot save person''' 
No data exist for this person. Please enter data or cancel the edit. 
Close
{{stub}}
{{-}}

====Cannot merge <object>====
[[File:CannotMerge-object-warning-dialog-example-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Cannot merge person (Warning dialog) - example]]
Attempting to merge anything other than two(2) of one type of record displays this warning popup dialog.

For example:

'''Cannot merge people''' 
Exactly two people must be selected to perform a merge. A second person can be selected by holding down the control key while clicking on the desired person.

Close

{{-}}

See:
* [[Gramps_6.0_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging records]]

====Duplicate Family warning dialog====

{{man warn| {{man label|Duplicate Family}} Warning |If you create a new family and select parents that are already in an existing family, Gramps will issue the {{man label|Duplicate Family}} warning message. If you proceed by saving the new family, you will have a duplicate family.}}

[[File:DuplicateFamily-warning-dialog-50.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Duplicate Family - warning dialog]]

{{-}}

====Suppress warning when adding parents to a child====
Can be enabled from {{man label|Suppress warning when adding parents to a child.}} option in the [[Gramps_6.0_Wiki_Manual_-_Settings#Warnings|Preferences > Warnings]] dialog.

{{-}}
=====Adding parents to a person dialog=====
[[File:AddingParetsToA-Person-warning-dialog-51.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Adding parents to a person" warning dialog]]

{{stub}}
{{-}}

====Suppress warning when cancelling with changed data====

Can be disabled from {{man label|[ ]Suppress warning when cancelling with changed data.}} option in the {{man menu|[[Gramps_6.0_Wiki_Manual_-_Settings#Warnings|Edit > Preferences > Warnings]]}} dialog.

Used by the {{man label|[[Gramps_6.0_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_1#Edit_Person_dialog|Edit Person]]}} dialog.
{{stub}}

====Save Changes? dialog====
[[File:SaveChanges-alert-dialog-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "Save Changes?" - alert dialog]]

If any data in any tabs in the Edit Person dialog were modified, an {{man label|[[Gramps_6.0_Wiki_Manual_-_Error_and_Warning_Reference#Suppress_warning_when_cancelling_with_changed_data|Save Changes?]]}} alert window will appear, prompting you to choose from the following options:
*{{man button|Close without saving}} - changes.
*{{man button|'''Cancel'''}} (default) - the initial cancel request.
*{{man button|Save}} - the changes.
as well as a checkbox to indicate {{man label|[ ] ''Do not ask again''}} that can be disabled from the {{man label|[ ] Suppress warning when cancelling with changed data.}} option in the {{man menu|[[Gramps_6.0_Wiki_Manual_-_Settings#Warnings|Preferences > Warnings]]}} dialog.

{{-}}

====Suppress warning about missing researcher when exporting to GEDCOM====
[[File:xxx.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} xxx]]

Can be disabled from {{man label|Suppress warning about missing researcher when exporting to GEDCOM.}} option in the [[Gramps_6.0_Wiki_Manual_-_Settings#Warnings|Preferences > Warnings]] dialog.

{{stub}}
{{-}}

====Delete confirmation dialog====
[[File:Delete-confirmation-dialog-Undo-History-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Delete confirmation dialog for the "Undo History" dialog]]
Are you sure you want to clear the [[Gramps_6.0_Wiki_Manual_-_Navigation#Undo_History_dialog|Undo history]]? Select {{man button|Clear}} to confirm or {{man button|Cancel}} to exit.
{{-}}

====Undo history warning====
[[File:UndoHistoryWarning-Tool-dialog-52.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Tool "Undo history warning" dialog - default]]

The {{man label|[[Gramps_6.0_Wiki_Manual_-_Error_and_Warning_Reference#Undo_history_warning|Undo history warning]]}} dialog will be shown and you can either {{man button|Stop}} or {{man button|Proceed with the tool/import}}. It is recommended that you stop and backup your database; so that you can revert the process of running the tool (or import) if required.
{{-}}
[[File:UndoHistoryWarning-Import-dialog-52.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Import "Undo history warning" dialog - default]]
{{man warn|Undo history warning|Proceeding with this {{man label|process}} will erase the undo history for this session. In particular, you will not be able to revert the changes made by this tool or any changes made prior to it.

If you think you may want to revert running this process, please stop here and backup your database.}}
{{-}}

====No selected book item====
[[File:No-selected-book-item-warning-52.png|450px|right|thumb|''No selected book item'' - warning]]

You will see {{man label|No selected book item}} warning dialog when the [[Gramps_6.0_Wiki_Manual_-_Reports_-_part_3#Books|Books]] Report when you have not selected the item first in the '''Current book''' section of the '''Manage Books''' dialog.
{{-}}

====Person <____> is not in the Database====
[[File:xxx-52.png|250px|right|thumb|Person <____> is not in the Database}} warning dialog]]

{{man label|Person ____ is not in the Database}} warning dialog will be shown if the Center Person is Private or Living when the filtering options on the Report Options (2) tab settings for do not allow Private or Living Persons are used.

{{stub}}
{{-}}

====Autobackup...====
[[File:Autobackup.notification.on.exit-52.png|450px|right|thumb|"Autobackup..." notification on exit warning dialog]]
The {{man label|Autobackup...}} '''Please wait for backup to complete.''' notification on exit dialog is shown when exiting Gramps to indicate an Automatic Backup is in progress.

See also:
* {{man menu|Edit ➡ Preferences...}} {{man label|[[Gramps_6.0_Wiki_Manual_-_Settings#Family_Tree|Family Tree]]}} tab's [[Gramps_6.0_Wiki_Manual_-_Settings#Backup_Management|Backup Management]] section for the {{man label|[ ]Backup on exit}} and {{man label|Autobackup:}} options.

* [https://github.com/gramps-project/gramps/pull/1416 Backup: Add a popup to show the gramps state #1416]
{{-}}
====Could Not Set a Bookmark====
[[File:Could-Not-Set-a-Bookmark-warning-60.png|450px|right|thumb|"Could Not Set a Bookmark" warning dialog]]
A [[Gramps_6.0_Wiki_Manual_-_Navigation#Bookmark_Navigation|bookmark]] could not be set because nothing was selected.
{{-}}

====Opening the '<xxxxxxx>' database====
[[File:Opening-the-xxxxxxx-database-warning-60.png|450px|right|thumb|"Opening the '<xxxxxxx>' database" warning dialog]]
You may see the "Opening the '<xxxxxxx>' database" warning dialog when attempting to [[Gramps_6.0_Wiki_Manual_-_Manage_Family_Trees#Family_Trees_.28manager.29_window|convert]] the ''Database Type'' from BSDDB to SQLite .

An attempt to convert the database failed. Perhaps it needs updating.
{{-}}

== Errors ==

More serious problems cause an {{man label|Error Report}} dialog to be shown which will describe the actions you should take.

{{-}}
=== Error Report ===
[[File:ErrorReport-dialog-collapsed-ErrorDetail-default-50.png|400px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Error Report Assistant - dialog - collapsed "Error Detail" - default]]

The {{man label|Error Report}} dialog appears whenever something has happened in the Gramps application that the programmers did not expect.

Have a read of the [[How to create a good bug report]] article. If you believe you know how the Gramps developers might reproduce the bug or not, then select the {{man button|Report}} button to start the {{man label|[[Gramps_6.0_Wiki_Manual_-_Error_and_Warning_Reference#Error_Reporting_Assistant_dialog|Error Reporting Assistant]]}} dialog, and you can then follow the instructions.
{{-}}
[[File:ErrorReport-dialog-expanded-ErrorDetail-50.png|400px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Error Report Assistant - dialog - expanded "Error Detail" - default]]
{{-}}

=== Error Reporting Assistant dialog ===

Allows you an opportunity to compile a report about an error and then submit it manually to the Gramps bug reporting system (This requires you to have a registered account on the Gramps bug reporting system and then login into your bug tracker account.)
* [[Using the bug tracker]]

The Error Reporting Assistant is also known as the Bug Reporting Assistant.
{{-}}
====Report a bug page====

[[File:ErrorReportingAssistant-ReportABug-page-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Report a bug (page) - Error Reporting Assistant]]

This is the Bug Reporting Assistant. It helps to make a bug report to the Gramps developers that will be as detailed as possible.

The assistant asks a few questions and gathers some information about the error that just occurred and the operating environment.

At the end of the assistant process, you will be asked to file a bug report through the [https://gramps-project.org/bugs/my_view_page.php Gramps bug tracking] system.

The assistant will copy the bug report to the Operating System clipboard. This allows you to paste it into the form on the [https://gramps-project.org/bugs/my_view_page.php Gramps bug tracking] and review exactly what information you want to include.
{{-}}

====Error Details page====

[[File:ErrorReportingAssistant-ErrorDetails-page-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Error Details (page) - Error Reporting Assistant (Showing example error)]]

If you can see that there is any personal information included in the error please remove it.

This is the detailed Gramps error information, don't worry if you do not understand it. You will have the opportunity to add further detail about the error in the following pages of the assistant.
{{-}}

==== System Information page ====

[[File:ErrorReportingAssistant-SystemInformation-page-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} System Information (page) - Error Report Assistant]]

This is the information about your system that will help the developers to fix the bug.
{{-}}

==== Further Information page====

[[File:ErrorReportingAssistant-FurtherInformation-page-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Further Information (page) - Error Reporting Assistant]]

Please provide as much information as you can about what you were doing when the error occurred.

This is your opportunity to describe what you were doing when the error occurred.
{{-}}

====Bug Report Summary page ====

[[File:ErrorReportingAssistant-BugReportSummary-page-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Bug Report Summary (page) - Error Reporting Assistant]]

This is the completed bug report. The next page of the assistant will help you to file a bug on the Gramps bug tracking system website.
{{-}}

====Send Bug Report page====

[[File:ErrorReportingAssistant-SendBugReport-page-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Send Bug Report (page) - Error Reporting Assistant]]

Use the two buttons below to first copy the bug report to the clipboard and then open a webbrowser to file a bug report at
https://gramps-project.org/bugs/login_select_proj_page.php?ref=bug_report_page.php

* {{man label|Send Bug Report}} - This is the final step. Use the buttons on this page to start a web browser and file a bug report on the Gramps bug tracking system (This assumes you already have an user account on the bug tracker, if not signup for one first and then login into your bug tracker account.)
** {{man button|File bug report}} - Use this button to start a web browser and file a bug report on the Gramps bug tracking system.
** {{man button|Copy to clipboard}} - Use this button to copy the bug report onto the clipboard. Then go to the bug tracking website by using the button below, paste the report and click submit report

{{-}}

====Complete page ====

[[File:ErrorReportingAssistant-Complete-page-50.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Complete (page) - Error Reporting Assistant]]

Gramps is an Open Source project. Its success depends on its users. User feedback is important. Thank you for taking the time to submit a bug report.
{{-}}

=== Other Errors ===
==== Report could not be created ====

[[File:xxxx.png|450px|thumb|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Report could not be created dialog]]

The {{man label|Report could not be created}} dialog can occur for various reasons, eg: one reason is that the custom paper size you have chosen for the report is too large for PDF format that is being used.

{{man tip|PDF size limits|Each Adobe PDF Version format specification has a maximum page size limit, for:
* PDF Version 1.4 (Acrobat 5.0) and PDF Version 1.5 (Acrobat 6.0) the maximum PDF page size is 200" x 200" inches (508cm x 508cm)
* PDF Version 1.6 (Acrobat 7.0) and newer the theoretical PDF page size is 15,000,000" x 15,000,000" inches (38,100,000cm x 38,100,000cm) but in reality most programs do not properly support any sizes above 200" x 200" inches (508cm x 508cm).

See [https://en.wikipedia.org/wiki/PDF PDF] From Wikipedia.
}}


== Seeing all the error messages ==

Sometimes, not all the information needed to understand what has gone wrong will appear on the screen. For example, if you start Gramps with an invalid language setting (and some missing components) then the message that appears in the {{man label|[[Gramps_6.0_Wiki_Manual_-_Error_and_Warning_Reference#Warnings|Warnings]]}} dialog is:

[[File:Warning_message_GExiv2-40.png|800px|thumb|left|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Dialogue showing limited warnings]]
{{-}}
However, the full set of warning messages is:
(process:10929): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
2013-03-13 18:49:04.376: WARNING: __init__.py: line 69: Date parser for 'xx_XX.UTF-8' not available, using default
2013-03-13 18:49:04.547: WARNING: __init__.py: line 85: Date displayer for 'xx_XX.UTF-8' not available, using default
2013-03-13 18:49:05.949: WARNING: spell.py: line 74: Spelling checker is not installed
2013-03-13 18:49:16.023: WARNING: gramplet.gpr.py: line 400: WARNING: GExiv2 module not loaded. Image metadata functionality will not be available.

Sometimes Gramps just doesn't start and nothing appears on the screen, or Gramps suddenly quits so you don't see anything on the screen. In all these cases you may need to do something special to see all the errors.

=== Linux ===

You can start Gramps from the Command Line, as described in the note [[Gramps_6.0_Wiki_Manual_-_Getting_started#Linux| here]]. You will then see all the diagnostic information on the terminal.

=== MS Windows ===

You can start Gramps from the Command Line, as described in the note [[Gramps_6.0_Wiki_Manual_-_Getting_started#MS_Windows| here]]. You will then see all the diagnostic information on the terminal.

=== macOS ===

Starting Gramps through the CLI on macOS is covered [[Gramps_6.0_Wiki_Manual_-_Command_Line#macOS|here]].

==== Console application ====
You can also look at log messages from Gramps using Apples {{man label|[https://support.apple.com/en-us/guide/console/welcome/mac Console application]}}. The Console application is located in your Mac's Utilities folder, which is found in the Applications folder. (A shortcut on recent versions of macOS is to press Command and the space bar to start a Spotlight search. In the resulting pop up window, enter the first few characters of the word "Console" and then select the Console application.)

For example, one of the early alpha releases of Gramps just would not start and displayed nothing on the screen. However by opening the Console application, and typing Gramps in the filter at the top right hand corner some diagnostic information appeared. (Actually we typed "gramps[" because there were some other messages that were not relevant, but it wouldn't matter if they were included as well).
[[File:Console_output-40.png|1000px|thumb|left|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Console output]]
{{-}}
By shift clicking to select all the relevant messages and copying them we get:
01/03/2013 00:08:02 [0x0-0x88088].org.gramps-project.gramps[1867] 2939: ERROR: importer.py: line 51: Could not find any typelib for Gtk
01/03/2013 00:08:05 [0x0-0x88088].org.gramps-project.gramps[1867] Gtk typelib not installed. Install Gnome Introspection, and pygobject version 3.3.2 or later.
01/03/2013 00:08:05 [0x0-0x88088].org.gramps-project.gramps[1867] Gramps will terminate now.

In this particular case, this was enough to help the developer discover the problem.

{{-}}
{{man index|Gramps 6.0 Wiki Manual - User Directory|Gramps 6.0 Wiki Manual - Further References|6.0}}
{{languages|Gramps 6.0 Wiki Manual - Error and Warning Reference}}
{{grampsmanualcopyright}}

[[Category:Documentation]]
[[Category:Troubleshooting]]

Addon:Extract Place Data from a Place Title

2025-10-31T08:08:04Z

ErickLedger: /* See also */

{{languages|Addon:Extract Place Data from a Place Title}}
{{Third-party addon}}

{{man warn|Previously Part of [[Gramps_4.2_Wiki_Manual_-_Tools#Extract_Place_Data_from_a_Place_Title|Gramps 4.2.x]] and earlier|And now no longer part of Gramps you can download this tool from the third party addons}}
[[File:ExtractPlaceDataFromAPlaceTitle-ExtractPlaceData-result-window-example-51.png|right|thumb|450px|{{man label|Extract Place Data}} result dialog example for the {{man label|Extract Place Data from a Place Title tool}}]]

The {{man label|Extract Place Data from a Place Title}} tool attempts to extract city, state/province and zip code information from a place title.

The tools operates on places where all fields in the main location are empty.

==Usage==

You can access this tool via the menu {{man menu|Tools->Family Tree Processing->Extract Place Data from a Place Title...}}

The '''Undo history warning''' will be shown and you can either {{man button|Stop}} or {{man button|Proceed with the tool}}.

Once the report finishes the {{man label|Extract Place data}} dialog results window will show a preview list of Places with the possible data that can be extracted from the place title. Un-select the places you don't wish the tool to convert and select the {{man button|Accept changes and close}} button to apply the changes.

You can use the mouse or keyboard to select multiple rows at once, by using the {{man button|CTRL}} or {{man button|SHIFT}} keys with the mouse click, or with the space key. {{man button|CTRL + A}} will select all rows.

The {{man button|Toggle selection}} button will toggle the selection of all selected rows to match the top row.

You can sort the columns with a click of the column header.

Apart from the <code>Place title</code> column you can also manually edit the other column values if necessary by clicking on them.

{{-}}

;Notes
The description must match the following categories:

<code>New York, NY 10000</code>

Only available for :
* USA
* Canada
* Sweden
** Stockholm (A)
* France
** Paris, IDF 75000, FRA or Paris, ILE DE FRANCE 75000, FRA
{{-}}
==See also==
* [[Places in Gramps]]
* [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Place_Editor_dialog]]
* Title area at the top of the {{man label|Place Editor dialog}} displays the description of the place to be used in reports. Gramps will construct this for you. See [[Gramps_{{Version manual}}_Wiki_Manual_-_Settings#Display_Options|{{man menu|Preferences > Display > Enable automatic place title generation}}]]

[[Category:Addons]]
[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Tools]]

Addon:Extract Place Data from a Place Title

2025-10-31T08:07:35Z

ErickLedger: /* See also */ fix link

{{languages|Addon:Extract Place Data from a Place Title}}
{{Third-party addon}}

{{man warn|Previously Part of [[Gramps_4.2_Wiki_Manual_-_Tools#Extract_Place_Data_from_a_Place_Title|Gramps 4.2.x]] and earlier|And now no longer part of Gramps you can download this tool from the third party addons}}
[[File:ExtractPlaceDataFromAPlaceTitle-ExtractPlaceData-result-window-example-51.png|right|thumb|450px|{{man label|Extract Place Data}} result dialog example for the {{man label|Extract Place Data from a Place Title tool}}]]

The {{man label|Extract Place Data from a Place Title}} tool attempts to extract city, state/province and zip code information from a place title.

The tools operates on places where all fields in the main location are empty.

==Usage==

You can access this tool via the menu {{man menu|Tools->Family Tree Processing->Extract Place Data from a Place Title...}}

The '''Undo history warning''' will be shown and you can either {{man button|Stop}} or {{man button|Proceed with the tool}}.

Once the report finishes the {{man label|Extract Place data}} dialog results window will show a preview list of Places with the possible data that can be extracted from the place title. Un-select the places you don't wish the tool to convert and select the {{man button|Accept changes and close}} button to apply the changes.

You can use the mouse or keyboard to select multiple rows at once, by using the {{man button|CTRL}} or {{man button|SHIFT}} keys with the mouse click, or with the space key. {{man button|CTRL + A}} will select all rows.

The {{man button|Toggle selection}} button will toggle the selection of all selected rows to match the top row.

You can sort the columns with a click of the column header.

Apart from the <code>Place title</code> column you can also manually edit the other column values if necessary by clicking on them.

{{-}}

;Notes
The description must match the following categories:

<code>New York, NY 10000</code>

Only available for :
* USA
* Canada
* Sweden
** Stockholm (A)
* France
** Paris, IDF 75000, FRA or Paris, ILE DE FRANCE 75000, FRA
{{-}}
==See also==
* [[Places in Gramps]]
* [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Place_Editor_dialog]]
* Title area at the top of the {{man label|Place Editor dialog}} displays the description of the place to be used in reports. Gramps will construct this for you. See [[Gramps_{{Version manual}}_Wiki_Manual_-_Settings#Display_Options|Preferences > Display > Enable automatic place title generation]]

[[Category:Addons]]
[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Tools]]

Installing Gramps for Linux computers

2025-10-24T05:15:40Z

ErickLedger: /* Linux distributions */

{{languages|Installing Gramps for Linux computers}}

{{man warn|Before upgrading your distribution|Use your '''earlier version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees to the hardy and portable [[#1|XML format1]].}}

== Linux distributions ==
{{man note|These packages are built and supported by the [https://en.wikipedia.org/wiki/Linux_distribution distros (Linux distribution(s))].|If your Linux distribution is not listed you may possibly find it listed on [https://repology.org/metapackage/gramps/versions ''Repology''] Please report any problems with them to the package maintainer.}}
Most Linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| {{prettytable}}
!style="width: 85pt;" | Distribution
!GUI Package manager
!Current versions
!Notes
|-
|[[File:Debianopenlogo-32.png|link=https://packages.debian.org/search?keywords=gramps]]''' [[Debian]] '''
|Add/Remove Software
|
* Debian 11 ("bullseye"): Gramps 5.1.3 
* Debian 11 ("bullseye")([https://packages.debian.org/bullseye-backports/gramps backports]): Gramps 5.1.6
* Debian 12 ("bookworm")([https://packages.debian.org/source/bookworm-backports/gramps backports]): Gramps 5.1.6
* Debian 13 ("trixie")(stable): ([https://packages.debian.org/source/trixie/gramps Gramps 6.0.1])
* [http://packages.debian.org/sid/gramps sid (unstable testbed)]: Gramps 6.0.1
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[File:Ubuntu_32x32.png]] '''[https://ubuntu.com/ Ubuntu]'''
|Software Centre
|
* Focal (20.04 LTS): Gramps: 5.1.5
* Jammy (22.04): Gramps: 5.1.5
* Noble (24.04LTS): Gramps: 5.1.6
* Oracular (24.10): Gramps: 5.2.2
* Plucky (25.04): Gramps: 5.2.4
* Questing (Development: 25.10): Gramps: 6.0.1
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]/ (Also see: [https://launchpad.net/~rosco2/+archive/ubuntu/backports Backports])
|-
|[[File:Farm-Fresh linux mint.png]]''' [https://www.linuxmint.com/ Linux Mint]'''
|Software Manager
|
* 20.x(Gramps 5.1.2) 
* 21.x(Gramps 5.1.2) 
* 22.x(Gramps 5.1.2) 
|
* Use the "Software Manager" to install a recent version.
* Manually install the most current version of Gramps using the either of the following suggestions instructions [https://forums.linuxmint.com/viewtopic.php?p=2626875#p2626875 Flatpak newer versions] [https://forums.linuxmint.com/viewtopic.php?t=220159 older versions] from the ''Linux Mint Forums''
* [http://community.linuxmint.com/software/view/gramps Old versions available from Linuxmint]
|-
|[[File:Fedora_32x32.png]] '''[https://getfedora.org/ Fedora]'''
|Add/Remove Software (Gnome) or Software Management (KDE)
|
* <abbr title="Rawhide - Fedora development version">[https://docs.fedoraproject.org/en-US/releases/rawhide/ Rawhide]</abbr> (Gramps 6.0.4)
* Fedora 42 (Gramps 6.0.4)
* Fedora 41 (Gramps 5.2.4-1)
|[https://packages.fedoraproject.org/pkgs/gramps/gramps/ available versions] (packages.fedoraproject.org) [https://koji.fedoraproject.org/koji/packageinfo?packageID=1969 available versions] (koji Buildsystem)

|-
|'''[https://www.mageia.org/en/ Mageia]'''
||[https://wiki.mageia.org/en/Installing_and_removing_software drakrpm (or rpmdrake)]
|
* Mageia [https://madb.mageialinux-online.org/show?distribution=cauldron&architecture=x86_64&rpm=gramps&repo=&group=&page= Cauldron]: Gramps 6.0.3
* Mageia 8.0: Gramps 5.1.3
* Mageia 9.0: Gramps 5.1.6
|[http://mageia.madb.org/package/show/name/gramps Mageia App Db - gramps]
|-
|[[File:OpenSUSE-distribution-icon.png|32px]] '''[https://www.opensuse.org/ openSUSE]'''
|[https://en.opensuse.org/YaST_Software_Management YaST]
|
* openSUSE Tumbleweed: Gramps 6.0.3
* openSUSE Leap 16.0: Gramps 6.0.3
* openSUSE Leap 15.6: Gramps 6.0.1 
|[https://software.opensuse.org/package/gramps available versions] The most recent version can usually be installed from the 'openSUSE BuildService - GNOME:Apps' repository
|-
|[[File:Slackware-distribution-icon.jpg|32px]] '''[http://www.slackware.com/ Slackware]'''
|
|
* 15.0: Gramps 5.2.4 - [https://slackbuilds.org/repository/15.0/misc/gramps/?search=gramps slackbuilds.org]
|[https://pkgs.org/search/?q=gramps available versions]
|-
|[[File:archlinux-icon-crystal-32.svg]] '''[https://www.archlinux.org/ Arch Linux]'''
| [https://wiki.archlinux.org/index.php/pacman pacman]
|
* Gramps 6.0.1
|[https://archlinux.org/packages/extra/any/gramps/ available versions]
|-
|[[File:Gentoo-distribution-icon.png|32px]]'''[https://gentoo.org Gentoo Linux]'''
|
|
* Gramps 6.0.1
|[https://packages.gentoo.org/packages/app-misc/gramps available versions]
|}

{{-}}

== Debian package ==
For [[File:Debianopenlogo-32.png|link=Download#Debian-based]]'''[[Debian|Debian-based linux distributions]]''' (Which includes [[File:Ubuntu_32x32.png|link=Download#Debian-based]]''' Ubuntu ''') [{{github_url}}/releases/download/v{{Version Linux Debian}}/gramps_{{Version Linux Debian}}-1_all.ubuntu-24.10.deb Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved ({{man menu|change the filename to match the one you downloaded}}).

sudo dpkg -i gramps_{{Version Linux Debian}}-1_all.deb

If you have an error about having unmet dependencies run:

sudo apt-get -f install

to install the dependencies.

If you see an error about an incomplete GTK installation and missing language translations when starting Gramps, run

sudo apt install language-pack-gnome-en

to install the proper language pack. You may need to replace 'en' with your own language code, like 'nl' for Dutch.

=== Useful command lines ===
Before upgrading you can[https://sourceforge.net/p/gramps/mailman/message/35460486/]:

* Find out what version you are running, by using this:

dpkg-query -s gramps

that queries the package currently installed on your system and gives you info about it.

The line that begin with 'Depends:' contains a list of packages and their version numbers that your current installation depends on
you can compare the required Dependencies with the new version you downloaded with the following command:

dpkg-deb -I gramps_Version.Number.Of.NewDownload_all.deb

for example, you can get just the two Depends lines to compare using:

dpkg-query -s gramps | grep Depends:
dpkg-deb -I gramps_5.Version-Number_all.deb | grep Depends:

* If you are committed to an upgrade then make sure you have backed up you Family Trees to Gramps XML then run :

sudo dpkg -r gramps

this will remove the current gramps package (assuming its a python3 version older versions could be python-gramps )

* To stop Ubuntu updating gramps (to possibly an older version from Ubuntu!) you may need to run:

sudo apt-mark hold gramps

'''Upgrade is then complete.'''

== Flathub ==
Gramps {{Version Linux Flatpak}} is available as a Flatpak at [https://flathub.org/apps/search?q=gramps Flathub]. Flatpaks allow installing sandboxed versions of applications, which will work on any linux distribution.

'''Things to consider regarding the flatpak:'''

1. All flatpaks from Flathub are compiled at Github with their dependencies. If someone wants a dependency for an Addon not supported by the flatpak, then a repository or source install might be a better option. There is a list of dependencies included in the Gramps flatpak at https://github.com/gramps-project/flatpak . If you would like another dependency to be considered for addition to the flatpak, please submit an issue at https://github.com/gramps-project/flatpak/issues

2. Directory access to the Gramps flatpak at Flathub is limited by default to the user's home directory. However, another app named Flatseal can change the sandbox permissions. https://flathub.org/en/apps/com.github.tchx84.Flatseal

3. If you use Fedora, Fedora maintains its own Gramps flatpak in addition to the Gramps flatpak available at Flathub. The Fedora flatpak has a different list of dependencies. Here is the link to Fedora's Gramps flatpak https://koji.fedoraproject.org/koji/packageinfo?packageID=39415

4. Support for BSDDB3 got dropped in the Gramps 5.2 flatpak at Flathub. If you need to access a BSDDB3 database to convert it to Sqlite, there are a few options. The Fedora flatpak might include BSDDB3, and the archived 5.1.6 Gramps flatpak at the gramps-project github https://github.com/gramps-project/flatpak/releases/tag/v5.1.6-1 includes BSDDB3. However, the archived flatpak at the gramps-project link will eventually stop working because Flathub removes obsolete runtimes after a certain length of time. If neither flatpak option works, then a manual intall of BSDDB3 with a repository or source install of Gramps will be required.

'''Recommended steps to install the Gramps flatpak:'''

1. There are instructions for setting up and enabling Flathub for various distributions at https://flathub.org/setup

2. Use the blue install button at https://flathub.org/apps/details/org.gramps_project.Gramps if you set your software manager up to work with Flathub, or use the command below in a terminal:

flatpak install org.gramps_project.Gramps

== Snap from Canonical Snapcraft Store ==
The Gramps snap is a Linux app packages for desktop, cloud and IoT that can be installed from the Canonical Snap Store, the app store for Linux.

To install run:

<code>sudo snap install gramps</code>

It has been bundled with the same packages as our Flatpak:

* ICU
* PIL
* osm-gps-map
* GExiv2
* geocodelib
* goocanvas
* graphviz
* ghostscript
* networkx

These should allow some popular addons to work.

Dictionaries are not currently included. This would be possible, but the package size would obviously increase.

Let us know what you think. Comments from people who already use snaps would be especially welcome.

See also:
* [https://snapcraft.io/gramps snapcraft.io/gramps]
* [https://gramps.discourse.group/t/gramps-is-now-available-as-a-snap/7380 Gramps is now available as a Snap]
** [https://gramps.discourse.group/t/after-snap-install-help-request-on-facebook-group/7387 Snap Feedback]

== Build from source ==
For other distributions, [[File:Download_link.png|150px|link={{github_url}}/releases/v{{version}}]] the source and follow the instructions for [[Linux:Build from source]]

== Linux Live CD ==

{{man warn|Outdated version warning|Note this '''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} (an older version released 2010-11-17) and it is not recommended for general use}}

[[File:Download_link.png|150px|left|link=https://sourceforge.net/projects/gramps/files/gramps-cdrom/lgenealogy-6.1-desktop-i386.iso/download]]
'''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} pre-installed to trial, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn, [https://rufus.ie/en/ Rufus]..). [[Linux_Genealogy_CD#Download_the_CD|Download the CD]] (727 MB). The [[Linux Genealogy CD|Linux Genealogy CD is based on Ubuntu 10.10 (Maverick Meerkat)]]. If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install latest [http://www.ubuntulinux.org/ Ubuntu] and Gramps from the CD anytime you like.
{{-}}

== Online Demonstration ==
{{man warn|Buyer Beware|The following is a limited trial of a commercial cloud VM service (rollApp) that operates by subscription. The listing here is '''''not''''' an endorsement by the Gramps-project. Beware of giving third parties access to your genealogical data.}}

You can also try an online demonstration of version 5.2.3 of Gramps on rollApp (''"Cloud platform for native applications"'') categorized under '''[https://www.rollapp.com/apps/utilities Utilities]''' - ''[https://www.rollapp.com/apps/diagrams #diagrams]'':

* https://www.rollapp.com/app/gramps

Select '''Launch Online''' then '''Test Drive(Opening/saving files will not be available)'''

{{-}}

== Notes ==
Backup to '''Gramps XML''' format when updating. ''Although Gramps reads and writes '''GEDCOM 5.5.1''' format fluently (because it is the de facto format for genealogical data interchange), never depend on such a rudimentary format for archiving your research. GEDCOM cannot store all the intricacies found in Gramps data.'' Always backup with the more robust Gramps XML format.

[[File:Menubar-FamilyTrees-overview-FamilyTree-Loaded-example-60.png|thumb|right|450px|Menubar - {{man menu|"Family Trees > Make Backup..."}}]]

You will find a [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Backing_up_a_Family_Tree|{{Man menu|Make Backup...}}]] option in the {{Man menu|Family Trees}} menu of recent Gramps versions. Alternately, use [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|{{Man menu|Export...}}]] in the same menu but deselect the privacy and filtering options in the Exporter Assistant to avoid omission of any data.

See: [[How to make a backup]]

== See also ==
===Installing Gramps for Desktops===
Installation instructions specific to the different OSes are on the [[File:linux_32x32.png|link=Installing_Gramps_for_Linux_computers#Linux_distributions]], [[File:windows_32x32.png|link=Installing_Gramps_for_Windows_computers]],[[File:macos_200x200.png|32px|link=Installing_Gramps_for_macOS_computers]] and [[File:Bsd daemon.png|32px|link=BSD_platforms]] pages.

===GitHub Gramps for Desktops Releases===
:* [{{github_url}}/releases/v{{version}} {{version}} version]
:* [{{github_url}}/releases/ Archive of Gramps releases]
Wiki pages
* [[Previous releases of Gramps]]
* [[:Category:Versions|Versions on various platforms]]

===Installing Gramps Web for online collaboration===
[https://gramps-project.org/blog/web/ Gramps Web] is a frontend for a hosted instance of Gramps.
* [https://www.grampsweb.org/Deployment/ Docker]
* [https://www.grampsweb.org/LetsEncrypt/ Let's Encrypt und Docker Compose]

[[Category:Documentation]]

Installing Gramps for Linux computers

2025-10-24T05:15:22Z

ErickLedger: /* Linux distributions */

{{languages|Installing Gramps for Linux computers}}

{{man warn|Before upgrading your distribution|Use your '''earlier version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees to the hardy and portable [[#1|XML format1]].}}

== Linux distributions ==
{{man note|These packages are built and supported by the [https://en.wikipedia.org/wiki/Linux_distribution distros (Linux distribution(s))].|If your distribution is not listed you may possibly find it listed on [https://repology.org/metapackage/gramps/versions ''Repology''] Please report any problems with them to the package maintainer.}}
Most Linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| {{prettytable}}
!style="width: 85pt;" | Distribution
!GUI Package manager
!Current versions
!Notes
|-
|[[File:Debianopenlogo-32.png|link=https://packages.debian.org/search?keywords=gramps]]''' [[Debian]] '''
|Add/Remove Software
|
* Debian 11 ("bullseye"): Gramps 5.1.3 
* Debian 11 ("bullseye")([https://packages.debian.org/bullseye-backports/gramps backports]): Gramps 5.1.6
* Debian 12 ("bookworm")([https://packages.debian.org/source/bookworm-backports/gramps backports]): Gramps 5.1.6
* Debian 13 ("trixie")(stable): ([https://packages.debian.org/source/trixie/gramps Gramps 6.0.1])
* [http://packages.debian.org/sid/gramps sid (unstable testbed)]: Gramps 6.0.1
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[File:Ubuntu_32x32.png]] '''[https://ubuntu.com/ Ubuntu]'''
|Software Centre
|
* Focal (20.04 LTS): Gramps: 5.1.5
* Jammy (22.04): Gramps: 5.1.5
* Noble (24.04LTS): Gramps: 5.1.6
* Oracular (24.10): Gramps: 5.2.2
* Plucky (25.04): Gramps: 5.2.4
* Questing (Development: 25.10): Gramps: 6.0.1
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]/ (Also see: [https://launchpad.net/~rosco2/+archive/ubuntu/backports Backports])
|-
|[[File:Farm-Fresh linux mint.png]]''' [https://www.linuxmint.com/ Linux Mint]'''
|Software Manager
|
* 20.x(Gramps 5.1.2) 
* 21.x(Gramps 5.1.2) 
* 22.x(Gramps 5.1.2) 
|
* Use the "Software Manager" to install a recent version.
* Manually install the most current version of Gramps using the either of the following suggestions instructions [https://forums.linuxmint.com/viewtopic.php?p=2626875#p2626875 Flatpak newer versions] [https://forums.linuxmint.com/viewtopic.php?t=220159 older versions] from the ''Linux Mint Forums''
* [http://community.linuxmint.com/software/view/gramps Old versions available from Linuxmint]
|-
|[[File:Fedora_32x32.png]] '''[https://getfedora.org/ Fedora]'''
|Add/Remove Software (Gnome) or Software Management (KDE)
|
* <abbr title="Rawhide - Fedora development version">[https://docs.fedoraproject.org/en-US/releases/rawhide/ Rawhide]</abbr> (Gramps 6.0.4)
* Fedora 42 (Gramps 6.0.4)
* Fedora 41 (Gramps 5.2.4-1)
|[https://packages.fedoraproject.org/pkgs/gramps/gramps/ available versions] (packages.fedoraproject.org) [https://koji.fedoraproject.org/koji/packageinfo?packageID=1969 available versions] (koji Buildsystem)

|-
|'''[https://www.mageia.org/en/ Mageia]'''
||[https://wiki.mageia.org/en/Installing_and_removing_software drakrpm (or rpmdrake)]
|
* Mageia [https://madb.mageialinux-online.org/show?distribution=cauldron&architecture=x86_64&rpm=gramps&repo=&group=&page= Cauldron]: Gramps 6.0.3
* Mageia 8.0: Gramps 5.1.3
* Mageia 9.0: Gramps 5.1.6
|[http://mageia.madb.org/package/show/name/gramps Mageia App Db - gramps]
|-
|[[File:OpenSUSE-distribution-icon.png|32px]] '''[https://www.opensuse.org/ openSUSE]'''
|[https://en.opensuse.org/YaST_Software_Management YaST]
|
* openSUSE Tumbleweed: Gramps 6.0.3
* openSUSE Leap 16.0: Gramps 6.0.3
* openSUSE Leap 15.6: Gramps 6.0.1 
|[https://software.opensuse.org/package/gramps available versions] The most recent version can usually be installed from the 'openSUSE BuildService - GNOME:Apps' repository
|-
|[[File:Slackware-distribution-icon.jpg|32px]] '''[http://www.slackware.com/ Slackware]'''
|
|
* 15.0: Gramps 5.2.4 - [https://slackbuilds.org/repository/15.0/misc/gramps/?search=gramps slackbuilds.org]
|[https://pkgs.org/search/?q=gramps available versions]
|-
|[[File:archlinux-icon-crystal-32.svg]] '''[https://www.archlinux.org/ Arch Linux]'''
| [https://wiki.archlinux.org/index.php/pacman pacman]
|
* Gramps 6.0.1
|[https://archlinux.org/packages/extra/any/gramps/ available versions]
|-
|[[File:Gentoo-distribution-icon.png|32px]]'''[https://gentoo.org Gentoo Linux]'''
|
|
* Gramps 6.0.1
|[https://packages.gentoo.org/packages/app-misc/gramps available versions]
|}

{{-}}

== Debian package ==
For [[File:Debianopenlogo-32.png|link=Download#Debian-based]]'''[[Debian|Debian-based linux distributions]]''' (Which includes [[File:Ubuntu_32x32.png|link=Download#Debian-based]]''' Ubuntu ''') [{{github_url}}/releases/download/v{{Version Linux Debian}}/gramps_{{Version Linux Debian}}-1_all.ubuntu-24.10.deb Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved ({{man menu|change the filename to match the one you downloaded}}).

sudo dpkg -i gramps_{{Version Linux Debian}}-1_all.deb

If you have an error about having unmet dependencies run:

sudo apt-get -f install

to install the dependencies.

If you see an error about an incomplete GTK installation and missing language translations when starting Gramps, run

sudo apt install language-pack-gnome-en

to install the proper language pack. You may need to replace 'en' with your own language code, like 'nl' for Dutch.

=== Useful command lines ===
Before upgrading you can[https://sourceforge.net/p/gramps/mailman/message/35460486/]:

* Find out what version you are running, by using this:

dpkg-query -s gramps

that queries the package currently installed on your system and gives you info about it.

The line that begin with 'Depends:' contains a list of packages and their version numbers that your current installation depends on
you can compare the required Dependencies with the new version you downloaded with the following command:

dpkg-deb -I gramps_Version.Number.Of.NewDownload_all.deb

for example, you can get just the two Depends lines to compare using:

dpkg-query -s gramps | grep Depends:
dpkg-deb -I gramps_5.Version-Number_all.deb | grep Depends:

* If you are committed to an upgrade then make sure you have backed up you Family Trees to Gramps XML then run :

sudo dpkg -r gramps

this will remove the current gramps package (assuming its a python3 version older versions could be python-gramps )

* To stop Ubuntu updating gramps (to possibly an older version from Ubuntu!) you may need to run:

sudo apt-mark hold gramps

'''Upgrade is then complete.'''

== Flathub ==
Gramps {{Version Linux Flatpak}} is available as a Flatpak at [https://flathub.org/apps/search?q=gramps Flathub]. Flatpaks allow installing sandboxed versions of applications, which will work on any linux distribution.

'''Things to consider regarding the flatpak:'''

1. All flatpaks from Flathub are compiled at Github with their dependencies. If someone wants a dependency for an Addon not supported by the flatpak, then a repository or source install might be a better option. There is a list of dependencies included in the Gramps flatpak at https://github.com/gramps-project/flatpak . If you would like another dependency to be considered for addition to the flatpak, please submit an issue at https://github.com/gramps-project/flatpak/issues

2. Directory access to the Gramps flatpak at Flathub is limited by default to the user's home directory. However, another app named Flatseal can change the sandbox permissions. https://flathub.org/en/apps/com.github.tchx84.Flatseal

3. If you use Fedora, Fedora maintains its own Gramps flatpak in addition to the Gramps flatpak available at Flathub. The Fedora flatpak has a different list of dependencies. Here is the link to Fedora's Gramps flatpak https://koji.fedoraproject.org/koji/packageinfo?packageID=39415

4. Support for BSDDB3 got dropped in the Gramps 5.2 flatpak at Flathub. If you need to access a BSDDB3 database to convert it to Sqlite, there are a few options. The Fedora flatpak might include BSDDB3, and the archived 5.1.6 Gramps flatpak at the gramps-project github https://github.com/gramps-project/flatpak/releases/tag/v5.1.6-1 includes BSDDB3. However, the archived flatpak at the gramps-project link will eventually stop working because Flathub removes obsolete runtimes after a certain length of time. If neither flatpak option works, then a manual intall of BSDDB3 with a repository or source install of Gramps will be required.

'''Recommended steps to install the Gramps flatpak:'''

1. There are instructions for setting up and enabling Flathub for various distributions at https://flathub.org/setup

2. Use the blue install button at https://flathub.org/apps/details/org.gramps_project.Gramps if you set your software manager up to work with Flathub, or use the command below in a terminal:

flatpak install org.gramps_project.Gramps

== Snap from Canonical Snapcraft Store ==
The Gramps snap is a Linux app packages for desktop, cloud and IoT that can be installed from the Canonical Snap Store, the app store for Linux.

To install run:

<code>sudo snap install gramps</code>

It has been bundled with the same packages as our Flatpak:

* ICU
* PIL
* osm-gps-map
* GExiv2
* geocodelib
* goocanvas
* graphviz
* ghostscript
* networkx

These should allow some popular addons to work.

Dictionaries are not currently included. This would be possible, but the package size would obviously increase.

Let us know what you think. Comments from people who already use snaps would be especially welcome.

See also:
* [https://snapcraft.io/gramps snapcraft.io/gramps]
* [https://gramps.discourse.group/t/gramps-is-now-available-as-a-snap/7380 Gramps is now available as a Snap]
** [https://gramps.discourse.group/t/after-snap-install-help-request-on-facebook-group/7387 Snap Feedback]

== Build from source ==
For other distributions, [[File:Download_link.png|150px|link={{github_url}}/releases/v{{version}}]] the source and follow the instructions for [[Linux:Build from source]]

== Linux Live CD ==

{{man warn|Outdated version warning|Note this '''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} (an older version released 2010-11-17) and it is not recommended for general use}}

[[File:Download_link.png|150px|left|link=https://sourceforge.net/projects/gramps/files/gramps-cdrom/lgenealogy-6.1-desktop-i386.iso/download]]
'''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} pre-installed to trial, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn, [https://rufus.ie/en/ Rufus]..). [[Linux_Genealogy_CD#Download_the_CD|Download the CD]] (727 MB). The [[Linux Genealogy CD|Linux Genealogy CD is based on Ubuntu 10.10 (Maverick Meerkat)]]. If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install latest [http://www.ubuntulinux.org/ Ubuntu] and Gramps from the CD anytime you like.
{{-}}

== Online Demonstration ==
{{man warn|Buyer Beware|The following is a limited trial of a commercial cloud VM service (rollApp) that operates by subscription. The listing here is '''''not''''' an endorsement by the Gramps-project. Beware of giving third parties access to your genealogical data.}}

You can also try an online demonstration of version 5.2.3 of Gramps on rollApp (''"Cloud platform for native applications"'') categorized under '''[https://www.rollapp.com/apps/utilities Utilities]''' - ''[https://www.rollapp.com/apps/diagrams #diagrams]'':

* https://www.rollapp.com/app/gramps

Select '''Launch Online''' then '''Test Drive(Opening/saving files will not be available)'''

{{-}}

== Notes ==
Backup to '''Gramps XML''' format when updating. ''Although Gramps reads and writes '''GEDCOM 5.5.1''' format fluently (because it is the de facto format for genealogical data interchange), never depend on such a rudimentary format for archiving your research. GEDCOM cannot store all the intricacies found in Gramps data.'' Always backup with the more robust Gramps XML format.

[[File:Menubar-FamilyTrees-overview-FamilyTree-Loaded-example-60.png|thumb|right|450px|Menubar - {{man menu|"Family Trees > Make Backup..."}}]]

You will find a [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Backing_up_a_Family_Tree|{{Man menu|Make Backup...}}]] option in the {{Man menu|Family Trees}} menu of recent Gramps versions. Alternately, use [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|{{Man menu|Export...}}]] in the same menu but deselect the privacy and filtering options in the Exporter Assistant to avoid omission of any data.

See: [[How to make a backup]]

== See also ==
===Installing Gramps for Desktops===
Installation instructions specific to the different OSes are on the [[File:linux_32x32.png|link=Installing_Gramps_for_Linux_computers#Linux_distributions]], [[File:windows_32x32.png|link=Installing_Gramps_for_Windows_computers]],[[File:macos_200x200.png|32px|link=Installing_Gramps_for_macOS_computers]] and [[File:Bsd daemon.png|32px|link=BSD_platforms]] pages.

===GitHub Gramps for Desktops Releases===
:* [{{github_url}}/releases/v{{version}} {{version}} version]
:* [{{github_url}}/releases/ Archive of Gramps releases]
Wiki pages
* [[Previous releases of Gramps]]
* [[:Category:Versions|Versions on various platforms]]

===Installing Gramps Web for online collaboration===
[https://gramps-project.org/blog/web/ Gramps Web] is a frontend for a hosted instance of Gramps.
* [https://www.grampsweb.org/Deployment/ Docker]
* [https://www.grampsweb.org/LetsEncrypt/ Let's Encrypt und Docker Compose]

[[Category:Documentation]]

Installing Gramps for Linux computers

2025-10-24T05:14:11Z

ErickLedger:

{{languages|Installing Gramps for Linux computers}}

{{man warn|Before upgrading your distribution|Use your '''earlier version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees to the hardy and portable [[#1|XML format1]].}}

== Linux distributions ==
{{man note|These packages are built and supported by the [https://en.wikipedia.org/wiki/Linux_distribution distros].|If your distribution is not listed you may possibly find it listed on [https://repology.org/metapackage/gramps/versions ''Repology''] Please report any problems with them to the package maintainer.}}
Most Linux distributions come bundled with a version of Gramps, though it's not always the most recent version and it may not have been installed by default. Still it is recommended to use the Gramps version that comes with your distribution.

Below are ways to install Gramps on some of the more popular distributions:

{| {{prettytable}}
!style="width: 85pt;" | Distribution
!GUI Package manager
!Current versions
!Notes
|-
|[[File:Debianopenlogo-32.png|link=https://packages.debian.org/search?keywords=gramps]]''' [[Debian]] '''
|Add/Remove Software
|
* Debian 11 ("bullseye"): Gramps 5.1.3 
* Debian 11 ("bullseye")([https://packages.debian.org/bullseye-backports/gramps backports]): Gramps 5.1.6
* Debian 12 ("bookworm")([https://packages.debian.org/source/bookworm-backports/gramps backports]): Gramps 5.1.6
* Debian 13 ("trixie")(stable): ([https://packages.debian.org/source/trixie/gramps Gramps 6.0.1])
* [http://packages.debian.org/sid/gramps sid (unstable testbed)]: Gramps 6.0.1
|[http://packages.debian.org/search?keywords=gramps available versions]
|-
|[[File:Ubuntu_32x32.png]] '''[https://ubuntu.com/ Ubuntu]'''
|Software Centre
|
* Focal (20.04 LTS): Gramps: 5.1.5
* Jammy (22.04): Gramps: 5.1.5
* Noble (24.04LTS): Gramps: 5.1.6
* Oracular (24.10): Gramps: 5.2.2
* Plucky (25.04): Gramps: 5.2.4
* Questing (Development: 25.10): Gramps: 6.0.1
|[http://packages.ubuntu.com/search?keywords=gramps&searchon=names available versions]/ (Also see: [https://launchpad.net/~rosco2/+archive/ubuntu/backports Backports])
|-
|[[File:Farm-Fresh linux mint.png]]''' [https://www.linuxmint.com/ Linux Mint]'''
|Software Manager
|
* 20.x(Gramps 5.1.2) 
* 21.x(Gramps 5.1.2) 
* 22.x(Gramps 5.1.2) 
|
* Use the "Software Manager" to install a recent version.
* Manually install the most current version of Gramps using the either of the following suggestions instructions [https://forums.linuxmint.com/viewtopic.php?p=2626875#p2626875 Flatpak newer versions] [https://forums.linuxmint.com/viewtopic.php?t=220159 older versions] from the ''Linux Mint Forums''
* [http://community.linuxmint.com/software/view/gramps Old versions available from Linuxmint]
|-
|[[File:Fedora_32x32.png]] '''[https://getfedora.org/ Fedora]'''
|Add/Remove Software (Gnome) or Software Management (KDE)
|
* <abbr title="Rawhide - Fedora development version">[https://docs.fedoraproject.org/en-US/releases/rawhide/ Rawhide]</abbr> (Gramps 6.0.4)
* Fedora 42 (Gramps 6.0.4)
* Fedora 41 (Gramps 5.2.4-1)
|[https://packages.fedoraproject.org/pkgs/gramps/gramps/ available versions] (packages.fedoraproject.org) [https://koji.fedoraproject.org/koji/packageinfo?packageID=1969 available versions] (koji Buildsystem)

|-
|'''[https://www.mageia.org/en/ Mageia]'''
||[https://wiki.mageia.org/en/Installing_and_removing_software drakrpm (or rpmdrake)]
|
* Mageia [https://madb.mageialinux-online.org/show?distribution=cauldron&architecture=x86_64&rpm=gramps&repo=&group=&page= Cauldron]: Gramps 6.0.3
* Mageia 8.0: Gramps 5.1.3
* Mageia 9.0: Gramps 5.1.6
|[http://mageia.madb.org/package/show/name/gramps Mageia App Db - gramps]
|-
|[[File:OpenSUSE-distribution-icon.png|32px]] '''[https://www.opensuse.org/ openSUSE]'''
|[https://en.opensuse.org/YaST_Software_Management YaST]
|
* openSUSE Tumbleweed: Gramps 6.0.3
* openSUSE Leap 16.0: Gramps 6.0.3
* openSUSE Leap 15.6: Gramps 6.0.1 
|[https://software.opensuse.org/package/gramps available versions] The most recent version can usually be installed from the 'openSUSE BuildService - GNOME:Apps' repository
|-
|[[File:Slackware-distribution-icon.jpg|32px]] '''[http://www.slackware.com/ Slackware]'''
|
|
* 15.0: Gramps 5.2.4 - [https://slackbuilds.org/repository/15.0/misc/gramps/?search=gramps slackbuilds.org]
|[https://pkgs.org/search/?q=gramps available versions]
|-
|[[File:archlinux-icon-crystal-32.svg]] '''[https://www.archlinux.org/ Arch Linux]'''
| [https://wiki.archlinux.org/index.php/pacman pacman]
|
* Gramps 6.0.1
|[https://archlinux.org/packages/extra/any/gramps/ available versions]
|-
|[[File:Gentoo-distribution-icon.png|32px]]'''[https://gentoo.org Gentoo Linux]'''
|
|
* Gramps 6.0.1
|[https://packages.gentoo.org/packages/app-misc/gramps available versions]
|}

{{-}}

== Debian package ==
For [[File:Debianopenlogo-32.png|link=Download#Debian-based]]'''[[Debian|Debian-based linux distributions]]''' (Which includes [[File:Ubuntu_32x32.png|link=Download#Debian-based]]''' Ubuntu ''') [{{github_url}}/releases/download/v{{Version Linux Debian}}/gramps_{{Version Linux Debian}}-1_all.ubuntu-24.10.deb Download the .deb file]. Double-click on the downloaded .deb file or (for some distributions, e.g. Mint Debian) run the following command from the directory where the file was saved ({{man menu|change the filename to match the one you downloaded}}).

sudo dpkg -i gramps_{{Version Linux Debian}}-1_all.deb

If you have an error about having unmet dependencies run:

sudo apt-get -f install

to install the dependencies.

If you see an error about an incomplete GTK installation and missing language translations when starting Gramps, run

sudo apt install language-pack-gnome-en

to install the proper language pack. You may need to replace 'en' with your own language code, like 'nl' for Dutch.

=== Useful command lines ===
Before upgrading you can[https://sourceforge.net/p/gramps/mailman/message/35460486/]:

* Find out what version you are running, by using this:

dpkg-query -s gramps

that queries the package currently installed on your system and gives you info about it.

The line that begin with 'Depends:' contains a list of packages and their version numbers that your current installation depends on
you can compare the required Dependencies with the new version you downloaded with the following command:

dpkg-deb -I gramps_Version.Number.Of.NewDownload_all.deb

for example, you can get just the two Depends lines to compare using:

dpkg-query -s gramps | grep Depends:
dpkg-deb -I gramps_5.Version-Number_all.deb | grep Depends:

* If you are committed to an upgrade then make sure you have backed up you Family Trees to Gramps XML then run :

sudo dpkg -r gramps

this will remove the current gramps package (assuming its a python3 version older versions could be python-gramps )

* To stop Ubuntu updating gramps (to possibly an older version from Ubuntu!) you may need to run:

sudo apt-mark hold gramps

'''Upgrade is then complete.'''

== Flathub ==
Gramps {{Version Linux Flatpak}} is available as a Flatpak at [https://flathub.org/apps/search?q=gramps Flathub]. Flatpaks allow installing sandboxed versions of applications, which will work on any linux distribution.

'''Things to consider regarding the flatpak:'''

1. All flatpaks from Flathub are compiled at Github with their dependencies. If someone wants a dependency for an Addon not supported by the flatpak, then a repository or source install might be a better option. There is a list of dependencies included in the Gramps flatpak at https://github.com/gramps-project/flatpak . If you would like another dependency to be considered for addition to the flatpak, please submit an issue at https://github.com/gramps-project/flatpak/issues

2. Directory access to the Gramps flatpak at Flathub is limited by default to the user's home directory. However, another app named Flatseal can change the sandbox permissions. https://flathub.org/en/apps/com.github.tchx84.Flatseal

3. If you use Fedora, Fedora maintains its own Gramps flatpak in addition to the Gramps flatpak available at Flathub. The Fedora flatpak has a different list of dependencies. Here is the link to Fedora's Gramps flatpak https://koji.fedoraproject.org/koji/packageinfo?packageID=39415

4. Support for BSDDB3 got dropped in the Gramps 5.2 flatpak at Flathub. If you need to access a BSDDB3 database to convert it to Sqlite, there are a few options. The Fedora flatpak might include BSDDB3, and the archived 5.1.6 Gramps flatpak at the gramps-project github https://github.com/gramps-project/flatpak/releases/tag/v5.1.6-1 includes BSDDB3. However, the archived flatpak at the gramps-project link will eventually stop working because Flathub removes obsolete runtimes after a certain length of time. If neither flatpak option works, then a manual intall of BSDDB3 with a repository or source install of Gramps will be required.

'''Recommended steps to install the Gramps flatpak:'''

1. There are instructions for setting up and enabling Flathub for various distributions at https://flathub.org/setup

2. Use the blue install button at https://flathub.org/apps/details/org.gramps_project.Gramps if you set your software manager up to work with Flathub, or use the command below in a terminal:

flatpak install org.gramps_project.Gramps

== Snap from Canonical Snapcraft Store ==
The Gramps snap is a Linux app packages for desktop, cloud and IoT that can be installed from the Canonical Snap Store, the app store for Linux.

To install run:

<code>sudo snap install gramps</code>

It has been bundled with the same packages as our Flatpak:

* ICU
* PIL
* osm-gps-map
* GExiv2
* geocodelib
* goocanvas
* graphviz
* ghostscript
* networkx

These should allow some popular addons to work.

Dictionaries are not currently included. This would be possible, but the package size would obviously increase.

Let us know what you think. Comments from people who already use snaps would be especially welcome.

See also:
* [https://snapcraft.io/gramps snapcraft.io/gramps]
* [https://gramps.discourse.group/t/gramps-is-now-available-as-a-snap/7380 Gramps is now available as a Snap]
** [https://gramps.discourse.group/t/after-snap-install-help-request-on-facebook-group/7387 Snap Feedback]

== Build from source ==
For other distributions, [[File:Download_link.png|150px|link={{github_url}}/releases/v{{version}}]] the source and follow the instructions for [[Linux:Build from source]]

== Linux Live CD ==

{{man warn|Outdated version warning|Note this '''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} (an older version released 2010-11-17) and it is not recommended for general use}}

[[File:Download_link.png|150px|left|link=https://sourceforge.net/projects/gramps/files/gramps-cdrom/lgenealogy-6.1-desktop-i386.iso/download]]
'''Linux live CD Demonstration''' includes Gramps {{Version Linux Live CD}} pre-installed to trial, without touching anything on the hard drive. To start this boot the Computer with this Live Linux Desktop on a CD in the CD/DVD-ROM Drive. (Requires that you write this image to a CD-ROM using CD-Burner software eg:Nero, Imgburn, [https://rufus.ie/en/ Rufus]..). [[Linux_Genealogy_CD#Download_the_CD|Download the CD]] (727 MB). The [[Linux Genealogy CD|Linux Genealogy CD is based on Ubuntu 10.10 (Maverick Meerkat)]]. If you are interested in Gramps, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install latest [http://www.ubuntulinux.org/ Ubuntu] and Gramps from the CD anytime you like.
{{-}}

== Online Demonstration ==
{{man warn|Buyer Beware|The following is a limited trial of a commercial cloud VM service (rollApp) that operates by subscription. The listing here is '''''not''''' an endorsement by the Gramps-project. Beware of giving third parties access to your genealogical data.}}

You can also try an online demonstration of version 5.2.3 of Gramps on rollApp (''"Cloud platform for native applications"'') categorized under '''[https://www.rollapp.com/apps/utilities Utilities]''' - ''[https://www.rollapp.com/apps/diagrams #diagrams]'':

* https://www.rollapp.com/app/gramps

Select '''Launch Online''' then '''Test Drive(Opening/saving files will not be available)'''

{{-}}

== Notes ==
Backup to '''Gramps XML''' format when updating. ''Although Gramps reads and writes '''GEDCOM 5.5.1''' format fluently (because it is the de facto format for genealogical data interchange), never depend on such a rudimentary format for archiving your research. GEDCOM cannot store all the intricacies found in Gramps data.'' Always backup with the more robust Gramps XML format.

[[File:Menubar-FamilyTrees-overview-FamilyTree-Loaded-example-60.png|thumb|right|450px|Menubar - {{man menu|"Family Trees > Make Backup..."}}]]

You will find a [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Backing_up_a_Family_Tree|{{Man menu|Make Backup...}}]] option in the {{Man menu|Family Trees}} menu of recent Gramps versions. Alternately, use [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|{{Man menu|Export...}}]] in the same menu but deselect the privacy and filtering options in the Exporter Assistant to avoid omission of any data.

See: [[How to make a backup]]

== See also ==
===Installing Gramps for Desktops===
Installation instructions specific to the different OSes are on the [[File:linux_32x32.png|link=Installing_Gramps_for_Linux_computers#Linux_distributions]], [[File:windows_32x32.png|link=Installing_Gramps_for_Windows_computers]],[[File:macos_200x200.png|32px|link=Installing_Gramps_for_macOS_computers]] and [[File:Bsd daemon.png|32px|link=BSD_platforms]] pages.

===GitHub Gramps for Desktops Releases===
:* [{{github_url}}/releases/v{{version}} {{version}} version]
:* [{{github_url}}/releases/ Archive of Gramps releases]
Wiki pages
* [[Previous releases of Gramps]]
* [[:Category:Versions|Versions on various platforms]]

===Installing Gramps Web for online collaboration===
[https://gramps-project.org/blog/web/ Gramps Web] is a frontend for a hosted instance of Gramps.
* [https://www.grampsweb.org/Deployment/ Docker]
* [https://www.grampsweb.org/LetsEncrypt/ Let's Encrypt und Docker Compose]

[[Category:Documentation]]

Windows AIO themes

2025-10-14T08:48:46Z

ErickLedger: /* Example theme installation */ missing letter

[[File:Dark-theme-example-60.png|thumb|right|450px|Example Dark GTK3 Theme]]

The Gramps theme on the Windows AIO(All in one) installation can be changed so long as the Gramps AIO is version 5.0.x or newer and uses Gtk 3.18 to 3.24 you can select a theme that MUST support those versions (also themes that are designed for a later version may not work).

;GTK Themes:can be found in the '''[https://www.gnome-look.org/browse?cat=135&ord=latest GTK3/4 Themes]''' section on '''gnome-look.org''' that provide '''Eyecandy for your GTK Desktop'''.

__FORCETOC__
=Example theme installation=
For this example the '''[https://www.gnome-look.org/p/2299211 MacTahoe-gtk-theme]''' (By vinceliuice) provides a good looking dark theme.

* Start by download the file of latest release from https://github.com/vinceliuice/MacTahoe-gtk-theme/releases
* After downloading the theme file (often a tar.gz or a .zip ) decompress it using 7-zip of similar. In this example the filename was ''MacTahoe-gtk-theme-2025-08-22.zip''

* Once decompressed look in the ''MacTahoe-gtk-theme-2025-08-22'' folder for the ''release'' folder and you will see a list of sub themes select the '''MacTahoe-Dark.tar.xz''' file and decompress it, you should now have a folder named '''MacTahoe-Dark''' with various folders and files.
** Copy the '''MacTahoe-Dark''' folder to the Windows users directory called '''.themes''' if it does not exist create it first "C:\Users\<username>\.themes" .

You should now see the files stored in "<code>C:\Users\<username>\.themes</code>" (replace <username> with your user name) so that the final directory structure looks like:
C:\Users\<username>\.themes\MacTahoe-Dark\
...
gtk-3.0\
...

* Find your Gramps AIO installation folder and create/edit the ''settings.ini'' file in "C:\GrampsAIO64-6.0.5\etc\gtk-3.0\settings.ini"
** In the '''[Settings]''' section add in a line that says '''gtk-theme-name = MacTahoe-Dark''' (or whatever your theme name is). The complete file may look like this:
[Settings]
gtk-theme-name = MacTahoe-Dark

* Start Gramps and you should see the resulting theme shown in the screenshot above.

{{man note|Note: When starting Gramps with the new theme|your console may show some ''Gtk-WARNING **: Theme parsing error'' messages. These are usually harmless, but if there are a lot, and your Gramps screen doesn't look right, then your theme may not be compatible with the version of Gtk Gramps AIO is using, remove and find a new theme.}}

==Checking your Gramps AIO Gtk version==
You can check the Gramps AIO Gtk version by starting Gramps from the console;
gramps -v

C:\Program Files\GrampsAIO64-6.0.5>gramps -v
Gramps Settings:
----------------
gramps : AIO64-6.0.5--1
o.s. : Windows

Required:
---------
Python : 3.12.11
Gtk++ : 3.24.50
...

=See also=
* [[GEPS_029:_GTK3-GObject_introspection_Conversion#GTK_3_theme|GTK 3 theme - GEPS 029: GTK3-GObject introspection Conversion]]
* [[GrampsAIO_cx_freeze-based|GrampsAIO-cxfreeze-based]]
* [[Addon:ThemePreferences|Addon:Theme Preferences]] - a simpler way to use Gramps with a Dark theme as you only need to install this addon and select the {{man label|[ ] Dark Variant}} checkbox.

[[Category:GEPS|T]]
[[Category:Documentation]]
[[Category:Developers/General]]

Talk:Gramps 6.0 Wiki Manual - Navigation

2025-10-13T06:06:20Z

ErickLedger:

=Addon Manager move to another page?=
This page is intended to provide information about '''navigation''' methods in the various screens of Gramps.

It appears that Chapter 10 in the page, which is meant to '''describe navigation in the Enhanced Addon Manager''', gives excessive detail about its usage, including all the available options in the Addon Manager.

Wouldn’t it be better to move all this information to a dedicated page for the "Enhanced Addon Manager"?
--[[User:Avma|avma]] ([[User talk:Avma|talk]]) 08:38, 10 August 2025 (UTC)

:By "Enhanced Addon Manager" do you mean [[Addon:Plugin_Manager]]? if so then no the addon manager shown on this manual page is the builtin one. Apart from that the addon manager is not really about "Navigation" like you say and probably belongs on another page or more appropriately an appendix of its own, like alot of the pages in the user manual. [[User:ErickLedger|ErickLedger]] ([[User talk:ErickLedger|talk]]) 06:06, 13 October 2025 (UTC)

Census Addons

2025-10-05T06:42:07Z

ErickLedger: /* Future Enhancements */ Guessing this is mute ( No longer supported The Census Addons have been replaced in Gramps 4.2.X by the Forms Gramplet addon )

{{Third-party addon}}
{{man warn|No longer supported|2=The Census Addons have been replaced in Gramps 4.2.X by the [[Addon:Forms_Gramplet|Forms Gramplet addon]]}}

There are two census addons: a gramplet and a report.

The gramplet allows users to create and edit census data in a single form.

The report prints census events in a format similar to the original census entries.

==Configuration==

Before using the census addons you need to define which of your sources are census sources.

To do this you need to edit each source and add an entry in the Attributes tab. The entry must have a key of "Census" and a value which is a code that identifies the census.

Prior to v4.1, use the Data tab. After typing the value code you must press "Enter" before clicking "OK", or the value will not be saved.

{{man tip| Translated Gramps |2=If you are using a Gramps in other language than english, type the value key in translated form. E.g. in finnish "Väestönlaskenta".}}

[[Image:SourceForCensus.png]]

=== Supported definitions ===

A number of supported [[Census Definitions|definitions]] are included with the download.

A full list of codes is available. See: [[Census Definitions]]

=== Writing your own definitions ===

If a census you require is not in the list of supported definitions then you can write your own.

Census defintions are stored in a XML files. These are located in the Census directory beneath your plugins directory. The file called census.xml, provided in the download, contains some common definitions. Additional files called custom.xml and test.xml will also be searched.

Definition files consist of an XML declaration followed by a censuses element.

<?xml version="1.0" encoding="UTF-8" ?>
<censuses>

'''Note:''' Make sure that your definition file is saved using UTF-8 encoding.

The censuses element contains a number of census elements, each representing a census definition. The census start-tag contains 3 attributes:

* id : A unique code to identify the census definition.
* title : A description of the census.
* date : The date of the census in a Gramps date format.

<census id='UK1841' title='1841 UK Census' date='6 Jun 1841'>

Each census element should contain a column element for each column in the census. Column elements describe information that may be recorded for each person on the census.

A column element contains:

* An _attribute element. This contains the key used to store column information in the Attributes of Event Reference objects within the Gramps database. Once defined this text must not be changed.
* An optional _longname element. This contains a fuller description of the column that is used in the tooltips in the editor and for the heading in the census report.
* A size element. This contains the size of the column in the census report. It is a percentage of the page width. The sum of all size elemnts in a definition should total 100.

<column>
<_attribute>At Home</_attribute>
<_longname>Working at Home</_longname>
<size>7</size>
</column>

Note: The underscore is important and indicates that the text should be translated by translators.

Each census element may optionally contain heading elements. Heading elements describe information that is recorded once for each census.

A heading element contains:

* An _attribute element. This contains the key used to store census information in the Attributes of Event objects within the Gramps database.

<heading>
<_attribute>City or Borough</_attribute>
</heading>

Although you can add your definitions to the pre-defined entries in census.xml, you can create a separate file called custom.xml for this purpose.

=== Submitting your definitions ===

Once you have written some custom definitions, you may wish to share them with the Gramps community.

A [[Census Testing]] area is available for this purpose.

==Census Gramplet==

The census gramplet consists of a census listing and a census editor.

===Census Listing===

When the gramplet is loaded it lists all the census events for the active person. The listing displays the census source, date and place.

A new census event can be created by clicking the "New" button at the bottom of the gramplet.

An existing census event can be edited either by highlighting a row and clicking the "Edit" button or by double-clicking on a row.

===Census Editor===

[[File:census edition.png|thumb|400px|right|Census edition]]

The census editor is designed so that most census data can be entered into a single form.

* The first thing to enter is the census source. This is selected from a drop-down list at the top of the editor.

* Once the source has been selected the census date is populated automatically.

* Next a source reference can be entered. This should comprise of one or more references that uniquely identify the census entry. In the case of a UK census you will need to enter the PRO reference, Piece, Folio and Page.

* A place can be selected in the usual Gramps manner.

At the bottom of the editor there is a table which allows the user to enter data specific to individual people listed on the census return. A new person can be created and then added to the census by clicking the "+" button. A person already in Gramps can be added to the census by clicking the second button ("share"). A census source must be selected before people can be added to the list, and after the first person is added, the source can no longer be changed.

The cells in the table are editable. By clicking on a cell, the user can enter data from the census return into a corresponding column in the table.

A person can be removed from the list by clicking the "-" button.

The order of people in the list can be changed by highlighting a row and then using the up and down arrow buttons.

The census data can then be saved by clicking the "OK" button or discarded using "Cancel".

==Samples==

===Census Report===

The census report prints census events in a format similar to the original census entries.

Which censuses are printed is determined by settings in the Report Options.

A drop-down list allows the following options:

* By Person
* By Source
* By Person and Source
* All Census records

Use the first option to print all census records for a given person. This defaults to the current person but can be changed using a selector.

Use the second option to print all census records for a given source. Select the required source from the drop-down list.

The third option can be used to print a single census. Both the person and source selections are taken into account.

The last option prints all censuses in the database.

''Census Report for Martin, John''
1881
Date: 3 Apr 1881
Source Reference: 17 Hope Terrace - RG 11 /2854 page 27
Address: Wednesbury

Name Relation Condition Age Occupation Where Born Disability
Martin, John Head Married 36 Laborer Wednesbury /
N., Zillah Wife 36 Golds Greence
Martin, Arthur Son 11 Scholar Wednesbury
Martin, Zillah Daughter 7 Scholar Wednesbury
Martin, Catherine Daughter 5 Scholar Wednesbury

===NarrativeWeb Report===

[[File:narrative census.png|thumb|370px|right|Census data on individual form for NarrativeWeb Report]]

[[File:narrative events.png|thumb|370px|left|Shared Event]]

 

==Data Storage==

[[File:census data.png|thumb|400px|right|Census data]]

Each census return is stored as a single event record with an event type of "Census".

The chosen source is attached to the event and contents of the "Reference" field are stored and the "Volume/Page" field of the associated source reference object.

The "Date" and "Place" fields are stored in the event object.

Each person in the table is attached to the event. The contents of the table are stored as attributes in the associated event reference object. The attribute type is set to the column heading and the value is set to the contents of the cell. An additional attribute called "Order" contains an integer which defines the position that the person appears in the census.

The addons will read existing data in this format. If "Order" attributes do not exist, they will be created when the editor saves a record. Until then the order of the people in the census will not be defined.

Data can also be edited using the usual Gramps editors.

==Editing stored census return==

Add Census Gramplet to Person Category. Search a person with Event reference to the stored census return you wish to edit. Clicking the stored census return opens Census Editor. In case no person is yet recorded in Census return's Details tab, go to Person Category, link an existing person or a new person to to the stored census return. Continue with opening the stored census return in Census Gramplet.

==Example of using the Census Addon==

This is an example of how to get started with the Census Addon after it is installed as described above. The 1841 UK census is used as the example:
# Start or open a family tree in Gramps.
# Add a person (name and gender) if this is a new family tree.
# Go to the Source view.
# Add a source with a title like "Source for 1841 Census"
# Add a Census key (v4.1):
## Open that source and go to the "Attributes" tab.
## Click on the plus symbol to add a key and value.
## Fill in the Attribute field with "Census".
## Fill in the Value field and with "UK1841". It is important here to not have a space in the Value. Use "UK1841", not "UK 1841".
## Click on OK.
# Add a Census key (Prior to v4.1):
## Open that source and go to the "Data" tab.
## Click on the plus symbol to add a key and value.
## Fill in in the key column with "Census" and hit enter.
## Click on Value column and fill in "UK1841", hit enter. It is important here to not have a space in the Value. Use "UK1841", not "UK 1841".
## Click on OK.
## Reopen the Source to see if the key and value pair have been successfully stored in the "Data" tab (optional).
# Go to the People view and switch on the sidebar (View->sidebar).
# Add the "Census Gramplet" by rightclicking on the side bar and choosing "Add Gramplet->Census Gramplet".
# Select the person that you created (or an existing person that appears in that census) in the main window.
# In the Census Gramplet on the sidebar, click "New".
# The New Census" gramplet form should open and you can click on the arrow down bútton to the right of "Source". You should see the "Source for 1841 Census". Select this.
# Now you can enter all of the details from the census (e.g. Reference to the page and the address), and then add people in the normal Gramps way.
# Fill in the details from the census page against each person.

==Known Issues==

When using the census editor the user should not edit the same event using the standard Gramps event editor.

When the save button in the editor is clicked, the person records of the people in the census are updated. If a person is being edited using the Gramps person editor and the record is saved then data saved using the census editor will be lost for this person.

==External Links and resources==

* [[Census]] page on Gramps wiki
* [[File:CanadianCensus.gramps.gz|Census source definitions for available Canadian Censuses]] - Download file
* [[Events_manager#Census_Addon|Sample of use]]
* [http://www.chradams.co.uk/censusxml/howitworks.php Census XML project]
* [http://www.nappdata.org/napp/index.shtml North Atlantic Population Project]

[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Reports]]
[[Category:Gramplets]]

Addon:WebSearch

2025-09-29T22:25:56Z

ErickLedger:

{{Third-party addon}}
[[File:WebSearchGramplet-Addon-detached-example-60.png|right|thumb|450px|WebSearch Gramplet - detached - example - showing context menu]]
[[File:WebSearchGramplet-Addon-in-sidebar-example-60.png|right|thumb|450px|WebSearch Gramplet - in People category (Groupled people) - sidebar example]]
[[File:WebSearchGramplet-Addon-configuation-tab-60.png|right|thumb|450px|WebSearch Gramplet - Configuration tab]]

The {{man label|WebSearch Gramplet}} allows searching for information about people, places, and sources in popular genealogy databases. It automatically generates search links based on data from your genealogy records. The search parameters are filled in from the data objects in your Family Tree.

When you select a person or place in Gramps, WebSearch generates a list of links leading to relevant genealogy websites such as FamilySearch, MyHeritage, Ancestry, and more.

:''The {{man label|WebSearch Gramplet}} is an evolution of the [[Addon:Web_Connect_Pack|Web Connect Pack]] addons which created a set of Context Menus for Persons. The original interface for searching web databases proved too fussy. And the backend was too limited and linkrot maintenance was too convoluted. It is hoped that the CSV files will be easier to maintain and expand.''

== Usage ==

After [[Addon:WebSearch#Installation|installing]], then use the {{man menu|Add a gramplet}} menu to select the {{man menu|WebSearch}} entry in the sidebar as the gramplet's layout is oriented vertically with a list at the top and buttons at the bottom. So the sidebar container for Gramplets will be more effective than the bottombar.

The {{man label|WebSearch Gramplet}} focuses on the '''active record''' in the People, Families, Places or Sources categories. It determines if that record contains the data needs to do various targeted searches. If so, the gramplet creates a query link to search that online database. It automatically offers a collated list of search links related to the selected object.

Select a different Person, Family, Place or Source and then in the {{man label|WebSearch Gramplet}} double-click on the desired weblink, and that search will open in your browser with the results.

Select a different Person, Family, Place or Source and the list in the gramplet updates.

If performing searches on a series of objects, undock the Gramplet. This will ensure that the list of available searches will update and remain accessible as you navigate between view categories and navigate the active record focus.

====WebSearch Context menu====
The WebSearch Context menu options when selecting a link are:
<hr>
* {{man menu|Add link to note}} : Person links only
* {{man menu|Add link to attribute}} :
* {{man menu|Show QR-code}} : Quickly open links on a mobile device via a camera application
* {{man menu|Copy link to clipboard}}
* {{man menu|Hide link for selected item}}
* {{man menu|Hide link for all items}}
<hr>

====WebSearch Configuration====
Use the {{man menu|View -> Configure}} menu access the {{man label|WebSearch}} tab where you can change the selected sets of searches that are to be considered.

You can limit to specific lists (saved in Comma Separated Value or CSV files) of databases for different locales and special interests. Some lists are for databases in specific locales (regions.countries) and others are for global databases.

=== What search parameters are available ===

WebSearch supports multiple navigation types with basic pre-defined parameters:
* Person: given name (with basic parsing into forename and middle names), surname, birth year, death year, birth place, et cetera
* Place: name, geographic coordinates (longitude and latitude), administrative place type
* Family: parent details, marriage place and year, divorce details
* Source: source title

Extensive parameters are also available for each type of record. The additional options are listed in the documentation for the WebSearch repository. But these basic parameters are the most common fields found in online genealogical search forms.

=== How to customize? ===

WebSearch works immediately after installation, but you can customize it:

Choose which websites to use for searches.

Modify the format of generated search URLs.

Use additional variables for search queries.

More detailed information about configuration can be found in the full [https://github.com/jurchello/WebSearch/blob/main/README.md README].

=== Additional Features ===

====Custom links based on Attributes====
Custom links based on Attributes : substitutes values from named unique identifiers into a URL)
: As an example, many genealogy application files export the FamilySearch profile IDs in a <code>_FSFTID</code> custom GEDCOM tag. If WebSearch finds an Attribute named <code>_FSFTID</code> and is configured to show the UID CSV records, it will offer a series of FamilySearch links to this Profile identifier: the person details, sources, pedigree charts. Users who are logged into the FamilySearch system can navigate to those pages with a simple double-click.

{| class="wikitable sortable"
|+ Recognized UIDs include:
|-
! Attribute name
! Website
! Description
! Example value
|-
! '''_FSFTID'''
| FamilySearch.org
|person profile
|<code>KNDX-MKG</code>
|-
! '''FacebookID'''
| Facebook.com
|account
|<code>groups/370692133138445</code>
|-
! '''FindAGraveID'''
| FindAGrave.com
|memorial profile
|<code>1075</code>
|-
! '''GeneeeID'''
| Geneee.org
|(Geneweb) person profile
|<code>george/washington</code>
|-
! '''GeniID'''
| Geni.com
|person profile
|<code>George-Washington-1st-President-of-the-United-States/6000000008211776777</code>
|-
! '''GNDID'''
| d-nb.info
|Dun & Bradstreet business profile
|54-0564701 (Mount Vernon Ladies' Association of the Union)
|-
! '''InstagramID'''
| Instagram.com
| account
|@mount_vernon
|-
! '''LinkedInID'''
| LinkedIn.com
|person professional profile
|mountvernon
|-
! '''RogloID'''
| Roglo.eu
|(Rauglaudre collaborative GeneWeb database) person profile
|1825727
|-
! '''VIAFID'''
| viaf.org
|(Virtual International Authority File) OCLC identifier
|31432428
|-
! '''WeRelateID'''
| WeRelate.org
|person profile
|<code>George_Washington_(6)</code>
|-
! '''WikidataID'''
| Wikidata.org
|knowledgebase article name
|<code>Q23</code>
|-
! '''WikipediaID'''
| wikipedia.org
|knowledgebase article name
|<code>George_Washington</code>
|-
! '''WikiTreeID'''
| WikiTree.com
|person profile
|<code>Washington-11</code>
|-
! '''XINGID'''
| XING.com
|job listing
|
|-
|}

Sorting and filtering – Easily find the necessary links.
Use OpenAI (optional) – Get additional search recommendations (may require an OpenAI API key).

== Installation ==
Stable versions are published for installation from a personal curated addon collection via the '''[[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Using_the_Addon_Manager|Addon Manager]]'''. Experimental version are updated more frequently but require manual download and installation.

===Addon Manager project settings===
<hr>
* '''Project name:''' <code>WebSearch (5.2)</code>
:;URL:
:;<nowiki>https://raw.githubusercontent.com/jurchello/WebSearch/dist/gramps52</nowiki>
<hr>
* '''Project name:''' <code>WebSearch (6.0)</code>
:;URL:
:;<nowiki>https://raw.githubusercontent.com/jurchello/WebSearch/dist/gramps60</nowiki>
<hr>

WebSearch installs as a standard Gramplet for Gramps [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Addon_Manager|via the Addon Manager]]. Experimental versions can be [[{{man version}}_Addons#Manually_installed_Addons|manually installed]] after downloading the compressed package from [https://github.com/jurchello/WebSearch JUrchello's WebSearch development repository].

== See also ==
Discourse community support forum
* [https://gramps.discourse.group/t/a-new-websearch-gramplet-is-ready/7188 A new WebSearch gramplet is ready] Urchello 2025-03-10 - '''I would like to mention that this Gramplet is a full replacement for several existing regional Gramplets (available from the Web Connect Pack - Addon)'''
* [https://gramps.discourse.group/t/new-ua-web-connect-pack-addon-how-to-integrate-into-gramps/7172 New UA Web Connect Pack addon – How to integrate into Gramps?]

GitHub
* [https://github.com/jurchello/WebSearch WebSearch repository]

[[Category:Addons]]
[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Gramplets]]

Addon:Web Connect Pack

2025-09-29T22:23:27Z

ErickLedger: /* See Also */ Not a Gramplet only a menu for "Web Connection"

{{Third-party addon}}
{{man warn|Install the country you require only|otherwise many websites will be duplicated in the "Web Connection" menu.}}
[[File:Web-connect-pack-UK-menu-51.png|thumb|right|450px|Web Connect Pack - UK websites menu]]
The ''Web Connect Packs'' contain a collection of Web sites for [[Addon:Web_Connect_Pack#Available_Web_connect_Packs|various countries]].

==Usage==
From the {{man label|{{icon|peop}} '''People'''}} Category view select a person then right-click and from the context menu select the {{man label|Web Connection}} entry to show the website choices that you can search on. Selecting a website will send the selected persons following data:
* <code>%(surname)s</code> : Surname
* <code>%(given)s</code> : Given name
* <code>%(middle)s</code> : Middle name
* <code>%(birth)s</code> : Birth year
* <code>%(death)s</code> : Death year
to be queried and the result if any will be displayed.

==Prerequisites==
Before using you must install libwebconnect library and one of language packs.

* Requires '' 'libwebconnect' '' be installed.
'' 'libwebconnect' '' is the support ''Library for web site collections''.

==Available Web connect Packs==
{{man warn|Install the country you require only|otherwise many websites will be duplicated in the "Web Connection" menu.}}
Available Web connect Packs:
*DEWebConnectPack - German
** See also [[Resources_and_related_sites#German|German resources]]
*FRWebConnectPack - French
** See also [[Resources_and_related_sites#French|French resources]]
*NLWebConnectPack - Netherlands
** See also [[Resources_and_related_sites#Netherlands|Netherlands resources]]
*RUWebConnectPack - Russia
** See also [[Resources_and_related_sites#Russian|Russian resources]]
*SVWebConnectPack - Swedish
** See also [[Resources_and_related_sites#Swedish|Swedish resources]]
*UAWebConnectPack - Ukrainian
** See also [[Resources_and_related_sites#General_information_sites |General information sites]]
*UKWebConnectPack - United Kingdom
** See also [[Resources_and_related_sites#General_information_sites |General information sites]]
*USWebConnectPack - United States of America
** Includes [[Resources_and_related_sites#Australian|Australian sources]]/French(selected)/Norway
** See also [[Resources_and_related_sites#United_States_of_America|US resources]]

==Issues==
If the external website that "[https://gramps-project.org/bugs/tag_view_page.php?tag_id=281 Web Connect Pack]" queries against changes its query method, please raise an issue on the bug tracker.

===Updating a webpack===
If the query no longer works because the website updated the way searches happen these addons will need updating also.

So a Python line in the <code>WEBSITES</code> section of WebPack.py that reads like:
<pre>["Person", "WikiTree", "WikiTree", "https://wikitree.sdms.si/function/WTWebProfileSearch/Profiles.htm?&Query=%(given)s+%(surname)s+B%(birth)s+D%(death)s&MaxProfiles=500&SortOrder=Default&PageSize=10"],</pre>
creates a {{man menu|WikiTree }} submenu line to the contextual pop-up menu's {{man menu|Web Connection}} group in the People category view.

Selecting that a {{man menu|WikiTree }} submenu line for a Person Gramps records as being named ''Richard Milhous Nixon''; born ''12 January 1913'' in ''Yorba Linda, California''; died ''23 April 1994'' in ''Manhatten, New York''; would send the following query line to your default browser:

https://wikitree.sdms.si/function/WTWebProfileSearch/Profiles.htm?&Query=Richard+Nixon+B1913+D1994&MaxProfiles=500&SortOrder=Default&PageSize=10

==See Also==
* [[Web Solutions for Gramps]]
* [https://sourceforge.net/p/gramps/mailman/gramps-devel/thread/298891.95437.qm%40web24105.mail.ird.yahoo.com/#msg26715892 2010 mail list discussion] about creating the Web Pack system
* [[Addon:WebSearch]] Gramplet that is a full replacement for existing regional "Web Connection" menus available from the Web Connect Pack - Addon

[[Category:Addons]]
[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Reports]]
[[Category:Prerequisites]]

Import from another genealogy program

2025-09-29T22:08:25Z

ErickLedger:

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs|note information maybe outdated.}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===
[https://genopro.com/ GenoPro] software for drawing family trees and [https://en.wikipedia.org/wiki/Genogram genograms].

==== GEDCOM ====

GenoPro can generate custom (invalid) GEDCOM [https://sourceforge.net/p/gramps/mailman/message/27539893/] but also better one [https://sourceforge.net/p/gramps/mailman/message/27547464/].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}[https://gramps-project.org/bugs/view.php?id=2757#c27362 gno2gramps.py].

=== Heredis ===
[https://home.heredis.com/en/ Heredis] Family tree software.

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

<hr>
=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (easy)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* Gramps [[Import_from_another_genealogy_program#Gramps_Addon_TMG_importer|TMG importer]] Addon - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "[[Gramps_6.0_Wiki_Manual_-_Settings#Input_Options|Default family relationship]]" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

<hr>

=== Visuged ===
[http://www.visuged.org/ Visuged]

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-29T22:06:27Z

ErickLedger: /* Visuged */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===
[https://genopro.com/ GenoPro] software for drawing family trees and [https://en.wikipedia.org/wiki/Genogram genograms].

==== GEDCOM ====

GenoPro can generate custom (invalid) GEDCOM [https://sourceforge.net/p/gramps/mailman/message/27539893/] but also better one [https://sourceforge.net/p/gramps/mailman/message/27547464/].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}[https://gramps-project.org/bugs/view.php?id=2757#c27362 gno2gramps.py].

=== Heredis ===
[https://home.heredis.com/en/ Heredis] Family tree software.

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

<hr>
=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (easy)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* Gramps [[Import_from_another_genealogy_program#Gramps_Addon_TMG_importer|TMG importer]] Addon - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "[[Gramps_6.0_Wiki_Manual_-_Settings#Input_Options|Default family relationship]]" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

<hr>

=== Visuged ===
[http://www.visuged.org/ Visuged]

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-29T22:01:10Z

ErickLedger: /* Heredis */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===
[https://genopro.com/ GenoPro] software for drawing family trees and [https://en.wikipedia.org/wiki/Genogram genograms].

==== GEDCOM ====

GenoPro can generate custom (invalid) GEDCOM [https://sourceforge.net/p/gramps/mailman/message/27539893/] but also better one [https://sourceforge.net/p/gramps/mailman/message/27547464/].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}[https://gramps-project.org/bugs/view.php?id=2757#c27362 gno2gramps.py].

=== Heredis ===
[https://home.heredis.com/en/ Heredis] Family tree software.

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

<hr>
=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (easy)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* Gramps [[Import_from_another_genealogy_program#Gramps_Addon_TMG_importer|TMG importer]] Addon - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "[[Gramps_6.0_Wiki_Manual_-_Settings#Input_Options|Default family relationship]]" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

<hr>

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-29T21:58:53Z

ErickLedger: /* GenoPro to Gramps */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===
[https://genopro.com/ GenoPro] software for drawing family trees and [https://en.wikipedia.org/wiki/Genogram genograms].

==== GEDCOM ====

GenoPro can generate custom (invalid) GEDCOM [https://sourceforge.net/p/gramps/mailman/message/27539893/] but also better one [https://sourceforge.net/p/gramps/mailman/message/27547464/].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}[https://gramps-project.org/bugs/view.php?id=2757#c27362 gno2gramps.py].

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

<hr>
=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (easy)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* Gramps [[Import_from_another_genealogy_program#Gramps_Addon_TMG_importer|TMG importer]] Addon - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "[[Gramps_6.0_Wiki_Manual_-_Settings#Input_Options|Default family relationship]]" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

<hr>

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-29T21:54:40Z

ErickLedger: /* GenoPro */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===
[https://genopro.com/ GenoPro] software for drawing family trees and [https://en.wikipedia.org/wiki/Genogram genograms].

==== GEDCOM ====

GenoPro can generate custom (invalid) GEDCOM [https://sourceforge.net/p/gramps/mailman/message/27539893/] but also better one [https://sourceforge.net/p/gramps/mailman/message/27547464/].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

<hr>
=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (easy)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* Gramps [[Import_from_another_genealogy_program#Gramps_Addon_TMG_importer|TMG importer]] Addon - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "[[Gramps_6.0_Wiki_Manual_-_Settings#Input_Options|Default family relationship]]" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

<hr>

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-29T21:53:13Z

ErickLedger: /* GenoPro */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== GEDCOM ====

GenoPro can generate custom (invalid) GEDCOM [https://sourceforge.net/p/gramps/mailman/message/27539893/] but also better one [https://sourceforge.net/p/gramps/mailman/message/27547464/].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

<hr>
=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (easy)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* Gramps [[Import_from_another_genealogy_program#Gramps_Addon_TMG_importer|TMG importer]] Addon - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "[[Gramps_6.0_Wiki_Manual_-_Settings#Input_Options|Default family relationship]]" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

<hr>

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Addon:Web Connect Pack

2025-09-29T21:45:54Z

ErickLedger: /* See Also */

{{Third-party addon}}
{{man warn|Install the country you require only|otherwise many websites will be duplicated in the "Web Connection" menu.}}
[[File:Web-connect-pack-UK-menu-51.png|thumb|right|450px|Web Connect Pack - UK websites menu]]
The ''Web Connect Packs'' contain a collection of Web sites for [[Addon:Web_Connect_Pack#Available_Web_connect_Packs|various countries]].

==Usage==
From the {{man label|{{icon|peop}} '''People'''}} Category view select a person then right-click and from the context menu select the {{man label|Web Connection}} entry to show the website choices that you can search on. Selecting a website will send the selected persons following data:
* <code>%(surname)s</code> : Surname
* <code>%(given)s</code> : Given name
* <code>%(middle)s</code> : Middle name
* <code>%(birth)s</code> : Birth year
* <code>%(death)s</code> : Death year
to be queried and the result if any will be displayed.

==Prerequisites==
Before using you must install libwebconnect library and one of language packs.

* Requires '' 'libwebconnect' '' be installed.
'' 'libwebconnect' '' is the support ''Library for web site collections''.

==Available Web connect Packs==
{{man warn|Install the country you require only|otherwise many websites will be duplicated in the "Web Connection" menu.}}
Available Web connect Packs:
*DEWebConnectPack - German
** See also [[Resources_and_related_sites#German|German resources]]
*FRWebConnectPack - French
** See also [[Resources_and_related_sites#French|French resources]]
*NLWebConnectPack - Netherlands
** See also [[Resources_and_related_sites#Netherlands|Netherlands resources]]
*RUWebConnectPack - Russia
** See also [[Resources_and_related_sites#Russian|Russian resources]]
*SVWebConnectPack - Swedish
** See also [[Resources_and_related_sites#Swedish|Swedish resources]]
*UAWebConnectPack - Ukrainian
** See also [[Resources_and_related_sites#General_information_sites |General information sites]]
*UKWebConnectPack - United Kingdom
** See also [[Resources_and_related_sites#General_information_sites |General information sites]]
*USWebConnectPack - United States of America
** Includes [[Resources_and_related_sites#Australian|Australian sources]]/French(selected)/Norway
** See also [[Resources_and_related_sites#United_States_of_America|US resources]]

==Issues==
If the external website that "[https://gramps-project.org/bugs/tag_view_page.php?tag_id=281 Web Connect Pack]" queries against changes its query method, please raise an issue on the bug tracker.

===Updating a webpack===
If the query no longer works because the website updated the way searches happen these addons will need updating also.

So a Python line in the <code>WEBSITES</code> section of WebPack.py that reads like:
<pre>["Person", "WikiTree", "WikiTree", "https://wikitree.sdms.si/function/WTWebProfileSearch/Profiles.htm?&Query=%(given)s+%(surname)s+B%(birth)s+D%(death)s&MaxProfiles=500&SortOrder=Default&PageSize=10"],</pre>
creates a {{man menu|WikiTree }} submenu line to the contextual pop-up menu's {{man menu|Web Connection}} group in the People category view.

Selecting that a {{man menu|WikiTree }} submenu line for a Person Gramps records as being named ''Richard Milhous Nixon''; born ''12 January 1913'' in ''Yorba Linda, California''; died ''23 April 1994'' in ''Manhatten, New York''; would send the following query line to your default browser:

https://wikitree.sdms.si/function/WTWebProfileSearch/Profiles.htm?&Query=Richard+Nixon+B1913+D1994&MaxProfiles=500&SortOrder=Default&PageSize=10

==See Also==
* [[Web Solutions for Gramps]]
* [https://sourceforge.net/p/gramps/mailman/gramps-devel/thread/298891.95437.qm%40web24105.mail.ird.yahoo.com/#msg26715892 2010 mail list discussion] about creating the Web Pack system
* [[Addon:WebSearch]] Gramplet that is a full replacement for existing regional Gramplets (available from the Web Connect Pack - Addon)

[[Category:Addons]]
[[Category:Plugins]]
[[Category:Developers/General]]
[[Category:Reports]]
[[Category:Prerequisites]]

Addon:Isotammi addons

2025-09-26T04:58:45Z

ErickLedger: remove extra "the"

{{languages|Addon:Isotammi_addons}}
{{#vardefine:chapter|Isotammi}} 
The [https://github.com/Taapeli '''Taapeli Project'''] (which is a national database of ''Suomen Sukututkimusseura ry'' : the [https://wikipedia.org/wiki/Genealogical_Society_of_Finland Finnish Genealogical Society]) curates their own set of "''Isotammi lisäosia''" : “Big Oak (the mythological World Tree) addons” for Gramps. The [https://web.archive.org/web/20240329010243/https://isotammi.net/ '''Isotammi Project'''] (discontinued in 2024) was a platform that coordinates validated merging of remote researcher's independent work into a collaborative genealogical collection.

This group of addons are designed to help Gramps users make their data compliant to Isotammi project. (Their server also contains tools for cleaning up GEDCOM dialects from other software.)

Isotammi users can import data as .gramps and .gpkg formats and browse it. Isotammi software is built on [https://neo4j.com/product/neo4j-graph-database/ Neo4j] (a high-speed graph database), Python and [https://palletsprojects.com/p/flask/ Flask] (a lightweight <abbr title="Web Server Gateway Interface">[https://wsgi.readthedocs.io/ WSGI]</abbr> web application framework), and increasingly [https://vuejs.org/ Vue] (a progressive JavaScript Framework for building user interfaces).

The main challenge now is auditing and merging user’s candidate material to approved data. Future plans include a live API to Isotammi. The API would allow transferring common identifiers, reference places and sources back to the researchers’ Gramps database.

The reason for competing with world-wide services is to get better harmony with Scandinavian name formats and local archives. And, in compliance with regional privacy regulations, to keep the data safely in Finland.

{{Third-party addon}}
{{man warn|Please note this group of addons require an additional step to install.|Follow the [[#Installation|installation instructions]] on this page.}}
[[File:Tools-Isotammi-tools-menu-51.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Isotammi Tools menu]]

Once [[#Installation|installed]]:
* [[#Gramplets|Gramplets]] are available from the:
** Dashboards {{man menu|add a gramplet}} right click menu. (Isotammi configuration / Deep Connections Graph / PropertyEditor )
** Events category {{man menu|add a gramplet}} drop down on the bottombar ( Dates )
* Tools are available under the {{man menu|[[#Tools|Tools > Isotammi tools -> ...]]}} menu.
* New [[#Rules|Rules]] are available as described below.
* Exporter for {{man label|[[#Isotammi_XML_export|Isotammi XML export]]}}

== About Isotammi ==
[https://www.genealogia.fi/en/webservices/isotammi/ Isotammi.net was an online service] provided by the Genealogical Society of Finland (Suomen Sukututkimusseura, abbreviated SSS) made by volunteers that took into account the special characteristics of Finnish genealogical research.

The SSS name is composed of three Finnish words:
* "Suomen" - This is the genitive case of the word "Suomi", meaning "Finland".
* "Suku" - This word means "family", "kin", or "lineage".
* "tutkimus" - This word means "research" or "study".
* "seura" - This word means "society" or "association".

So, the full name "Suomen Sukututkimusseura" literally translates to "Finland's Family Research Society" or "The Genealogical Society of Finland".

The service contains sourced family trees compiled by users, so called HisKi-trees made from materials in HisKi as well as place name databases compiled from communion books. Users are also provided with quality guidelines, recommendations and tools.

{{man note|The Isotammi team decided to end the Isotammi.net service on May 31, 2024|The [https://groups.google.com/g/gramps-finland/c/5IopnsV0UTY publicly announced reasoning] was that the costs are too high compared to the use and that further development of the application would have required resources that we did not have available. The team states that they have reached their goal of promoting good research practice with the ease of references to original sources and the researcher's own quality controls. Isotammi, instructions and Gramps accessories have been made with Finnish development work in the era of transnational giants. The service's software is still available as open source code, and other publication channels are being sought for its databases (location information, Hiskipuut, common family trees). The [https://www.facebook.com/groups/1748636758793391 Isotammi] Facebook group and the [https://groups.google.com/g/gramps-finland Gramps Finland] focused Google group still serve. The Isotammi team (Jorma, Juha, Kari, Pekka, Timo) thanks the users and their partner SSS for the past 10 years. The Society will retain and archive the content of the web service, genealogical data and geographical databases.
 Isotammi extensions developed for Gramps will not be affected by the end of the online service. }}

===The Service and its Aims===

Isotammi is developed domestically in Finland and this is where it begins it difference from commercial services. It relies on open source software and its own programming. The service is wholly non-commercial and all its public information is owned and controlled by the Society. The Society's role and it being domestically developed means that the service supports the special features of Finnish genealogy.

The user can also edit materials to Isotammi and browse materials uploaded to it online and on mobile devices. With the user's permission some materials are also public for all users. Registration is required to use Isotammi.

The aim of Isotammi is to support the principles of good research practices and to raise the quality of researchers' genealogy materials. The information on family trees should be supported by primary sources. References to them should be to as precise information as possible. Changes to personal names are managed with alternative names. The location of events are specified by attaching a hierarchy to them, i.e. giving information as to what larger whole it to which it belongs. For example, farm-house-village-municipality. Dozens of Place Name Databases in Isotammi help with these hierarchies.

==Installation==
[[File:IsotammiProject-52.png|Right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Isotammi Project for the Addon Manager (Linux)]]
For Gramps 5.2 and newer, go to the [[Gramps_5.2_Wiki_Manual_-_Navigation#Projects|Projects]] tab of the {{man menu|Edit -> Addon Manager}} and add the Isotammi Project description and URL:

<nowiki>Isotammi Project on Github</nowiki>
<nowiki>https://raw.githubusercontent.com/Taapeli/isotammi-addons/master/addons/gramps52</nowiki>


{{-}}
[[File:IsotammiExpertAddon-52.png|Right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Expert audience plugins for Addon Manager (Linux)]]
All the Isotammi addons are registered as '''Expert''' audience addons. Users have to change the {{man label|Addon Manager}} audience filter from '''Everyone''' to '''Expert'''.
{{-}}
=== Addon Management for 5.1 and earlier ===
{{man warn|Beware the false "The addon repository appears to be unavailable. Please try again later." message|Please note the Isotammi server has Finnish, Swedish & English lists. Old versions of the Plugin Manager Enhanced gave a false failure message if Gramps is running in any other language.

Update the Plugin Manager Enhanced if checking the Isotammi server for updates returns the message: "The addon repository appears to be unavailable. Please try again later."}}
[[File:EditPreferences-General-tab-example-51.png|Right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} General Preferences (Linux)]]
Isotammi [https://github.com/Taapeli/isotammi-addons#isotammi-addons addons installation] to get started for Gramps 5.1.x go to Gramps preferences ({{man menu|Edit > Preferences}}) and replace the value of {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Settings#Third_party_addons_management|Where to check:]]}} with:

<nowiki>https://raw.githubusercontent.com/Taapeli/isotammi-addons/master/addons/gramps51</nowiki> 
Click {{man button|Check for updated addons now}} and install all shown addons or at least the {{man label|[[#Isotammi_configuration|Isotammi configuration]]}} Gramplet.

After downloading the Isotammi addons restore the original value of {{man label|Where to check:}} with:

<nowiki>https://raw.githubusercontent.com/gramps-project/addons/master/gramps51</nowiki>



After installation go to Gramps Dashboard and add the {{man label|[[#Isotammi_configuration|Isotammi configuration]]}} Gramplet which will allow you to select which source to use for installing addons in the future: Gramps default or Isotammi addons
{{-}}

== Isotammi addons == 
[[File:Available Isotammi addons-51.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Available Isotammi addons (Gramps 5.1.3)]]



From the website


* https://github.com/Taapeli/isotammi-addons


Follow the [[#Installation|instructions to install]] the Gramps Isotammi addons associated with the Isotammi project.


So far, the following three gramplets, two rules, and one tool are available:


Gramplets:
* [[#Isotammi_configuration|Isotammi_configuration]]
* [[#Dates|Dates]] - This gramplet helps to correct invalid dates...
* Position tool
Rules:
* Events with an invalid date
* Events with a valid date
Tool:
* Generate source references based on more information

Here are brief descriptions of the above extensions:

=== Gramplets ===

==== Isotammi configuration ==== 
{{man warn|Deprecated for Gramps 5.2|The Isotammi Configuration dashboard gramplet is no longer needed. The Isotammi URL functionality was replaced with the Projects portion of the [[Gramps_5.2_Wiki_Manual_-_Navigation#Using_the_Addon_Manager...|Addon Manager]] in the Gramps 5.2 version. The API key feature was never leveraged.}}
A false "The addon repository appears to be unavailable. Please try again later." message may appear when using obsolete versions of the [[Addon:Plugin_Manager|Plugin Manager Enhanced]] addon in an unsupported locale. Please note the Isotammi server supports Finnish, Swedish and English lists. A false failure message can appear if Gramps is running in any other language.

Update the Plugin Manager Enhanced if checking the Isotammi server for updates returns the message: "The addon repository appears to be unavailable. Please try again later."}}
{{man label|Isotammi configuration}} Gramplet can be added to the Dashboard to allow you to select from which source the addons are installed e.g. from the default location of Gramps or from the Isotammi addons.

[[File:isotammi-config.png|Right|thumb|350px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Isotammi Configuration]]

The Addon source radio buttons switches the '''Where to check''' URL of the '''Third party addons management'''.

The 2 supported Repositories are: the Default location (the Gramps-Project repository on GitHub):
<nowiki>https://raw.githubusercontent.com/gramps-project/addons/master/gramps</nowiki>{{Stable_branch}}
and the Isotammi (the Taapeli repository also on GitHub):
<nowiki>https://raw.githubusercontent.com/Taapeli/isotammi-addons/master/addons/gramps</nowiki>{{Stable_branch}}
{{-}}
[[File:EditPreferences-General-tab-example-51.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} General Preferences (Linux)]]
The '''Gramps preferences''' button opens the preferences, allowing the selected Addons repository to be manually checked.
{{-}}

==== Dates ==== 
[[File:Dates-Gramplet-Isotammi-51.png|thumb|332px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Dates Gramplet - detached]]
The {{man label|Dates Gramplet}} is used in the Events category sidebar. It can be used to manipulate event date information, especially to correct dates in the unsupported formats.

First, select one (or more) events to which you want to modify and the appropriate transformation function to make the date into yyyy/mm/dd (or yyyy-mm-dd) format. Pressing the {{man button|Execute}} button applies the transformation.

Used in combination with the "[[#Events_with_an_invalid.2Fvalid_date|Events with an invalid date]]" addon custom filter rule will help target Event dates that Gramps sees as text strings rather than date objects.

The transformations of date tuples can recognize multiple delimiters: period/dot, dash/hyphen, comma, or slash.

=====Usage=====

* Replace text and Use regular expressions : a find&replace with a RegEx pattern matching option
: Find:
: Replace:
* 31.12.1888 ⇒ 1888-12-31
: convert ('reverse' transform) dd.mm.yyyy decimal notation to "yyyy-mm-dd"
* 12.31.1888 ⇒ 1888-12-31
: convert ('rotate' transform) mm.dd.yyyy decimal notation to "yyyy-mm-dd"
* 1888.12.31 ⇒> 1888-12-31
: convert (revalidate) yyyy.mm.dd decimal notation to "yyyy-mm-dd"
* 1888.31.12 ⇒ 1888-12-31
: convert ('swap' transform) yyyy.dd.mm.dd decimal notation to "yyyy-mm-dd"
* .12.1888 ⇒ 1888-12
: convert unknown day ".mm.yyyy" decimal notation to "yyyy-mm"
* 31..1888 ⇒ 1888-00-31
: convert unknown month "dd..yyyy" decimal notation to "yyyy-mm"
* ..1888 ⇒ 1888
: convert unknown month and day "..yyyy" decimal notation to "yyyy"
* 1888-99 ⇒ 1888-1899
: convert implied same century in span "ccyy-yy" notation to "ccyy-ccyy"
* <1888 (or -1888) ⇒ before 1888
: convert '''''either''''' the "<yyyy" '''''or''''' the open-ended "-yyyy" notation to "before yyyy"
* >1888 (or 1888-) ⇒ before 1888
: convert '''''either''''' the ">yyyy" '''''or''''' the open-ended "yyyy-" notation to "after yyyy"

=====Find and Replace=====

======Regular Expressions======
The RegEx feature in the Dates gramplet is a powerful tool for reformatting date ranges in Gramps. It addresses the challenge of converting ambiguous or non-standard date formats into a consistent, Gramps standard formats.

Consider the problem of having imported date text in the following pattern: `31-12-1881 - 17-3-1882`.

This format presents several issues. First, it uses hyphens to separate day, month, and year, which can be confused with the hyphen separating the two dates. Second, the order of day, month, and year is not immediately clear, as different regions use different conventions. Third, it is unclear if this should represent a date range (Between/And) or a date span (From/To).

The Third item is a judgement call that is based on context. We'll pretend that we investigated and determined that these are ranges when an Event could have occurred, not a span where the Event was definitely in progress.

The objective is to reformat this date range into a "between mm/dd/yyyy and mm/dd/yyyy" format, which Gramps can interpret correctly as a date range. From the context of the dates provided, we can deduce that the original format is dd-mm-yyyy. This knowledge is crucial for correctly reordering the date components.

To achieve this transformation, we use a regular expression to capture the individual components of each date, then rearrange them in the desired order. The regular expression `(\d+)-(\d+)-(\d+) - (\d+)-(\d+)-(\d+)` breaks down the original text into six groups: day, month, and year for each date in the range.

The replacement pattern `bet \2/\1/\3 and \5/\4/\6` reorders these captured groups and inserts slashes betwixt groups. Here, `\2/\1/\3` represents the first date in mm/dd/yyyy format, and `\5/\4/\6` represents the second date in the same format. The word "bet" at the beginning signals to Gramps that this is a "between" date range.

When applied, this regex transformation converts `31-12-1881 - 17-3-1882` to `bet 12/31/1881 and 3/17/1882`. Gramps then interprets this standardized format as a date range and displays it according to the user's preferred date format settings, resulting in a clear and consistent "between 31 Dec 1881 and 17 Mar 1882" display.

This regex approach effectively solves the problem of ambiguous date formats, providing a reliable method to convert various date range notations into a format that Gramps can accurately process and display as a date range.

When such transforms are necessary because a Source hands off poorly formatted data, it is a good idea to include a Private note in the Source about the bad data and the workflow to clean it.

{{-}}

==== Place tool ==== 
[[File:PlaceTool-Gramplet-Isotammi-51.png|thumb|450px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} PlaceTool Gramplet - detached]]
The {{man label|PlaceTool Gramplet}} can be used to manipulate multiple location data at once. It can form a hierarchy of places from comma-separated place names, the type of places can be changed, it can be used to move places (e.g., villages) inside the right keeper and to correct systematic typos. PlaceTool can be added to the bottombar in the Places category list view.
{{-}}

==== Deep Connections Graph ====
[[File:DeepConnectionsGraph-Gramplet-Isotammi-51.png|thumb|450px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} '''Deep Connections Graph''' gramplet detached from Dashboard category]]

The {{man label|Deep Connections Graph}} gramplet produces a graphical diagram of the relationships between two people - The chart shows not only the relationships, but also, for example, sponsorships and other events connections through Associations and through links in Notes.

The {{man label|Deep Connections Graph}} gramplet for the Dashboard category is the control for controlling a locally hosted, browser interface to charts of the [[Addon:Deep Connections Gramplet|Deep Connections]] data. It allows a [https://wikipedia.org/wiki/Localhost LocalHost] server to be created, the current Tree data to be posted. The server has a Form interface to select two Persons and options for diagramming their direct or indirect connection.
{{-}}
=====Usage=====
Add the {{man label|Deep Connections Graph}} gramplet to the [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Dashboard_Category|Dashboard category]].

The gramplet has the following options:
*{{man label|Port:}} <code>8888</code> (default)
*{{man button|Start server}} button.
*{{man button|Stop server}} button.
*{{man button|Refresh tree}} button.
*{{man button|Start browser}} button.

Launch the '''Deep Connections Graph browser interface''' by selecting the {{man button|Start browser}} button. Where you {{man label|Select person 1}} and {{man label|Select person 2}} and decide if you want to '''[ ]Use events / [ ] Use notes / [ ] Use associations''' or not and then you can select the {{man button|Get connections}} button to show the result.

[[File:DeepConnectionsGraph-browser-Isotammi-51.png|thumb|650px|center|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Deep Connections Graph browser interface]]

[[File:DeepConnectionsGraph-browser-example2-Isotammi-60.png|thumb|650px|center|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Deep Connections Graph browser interface - example result]]

You can also use the swap people {{man button|<- ->}} button and then {{man button|Get connections}} button to show the result for the second person.

;Note:Many of the error messages (when the server is unable to generate a graph/chart) are in [https://translate.google.com/saved?sl=fi&tl=en&op=translate Finnish].
{{-}}

==== PropertyEditor ====
[[File:NewSource-editor-dialog-example-50.png|thumb|404px|left|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} sample Edit Source dialog]]
[[File:PropertyEditor-Gramplet-Isotammi-51.png|thumb|384px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Property Editor source gramplet- detached]]
The Property Editor is a Source category gramplet allowing "Search and Replace" mass updates to selected subsets of Source records.

This tool was designed for use within the Isotammi collaborative Finnish genealogy project. It simplifies harmonization and merging of Source records.
===== See also =====
* [[Addon:EventDescriptionEditor|Event Description Editor]] addon tool - Find and Replace text within the Description of Event records.
* [[Addon:SetAttributeTool|Set Attribute]] addon tool - Overwrite text within the Attribute records in any Category.
* [[Addon:Isotammi_addons#SuperTool|SuperTool]] addon tool - create custom mass updates when at specialized tool does not exist.
{{-}}

==== Add Sources Gramplet ====

This '''Event''' category gramplet works together with the "[[#Generate_source_citations_from_notes|Generate citations based on additional information]]" tool (generatecitations).

This gramplet generates the necessary additional information without having to open the event. All you have to do is select the desired events and copy the additional information in the input field of the gramplet and press the button 'Add to selected events'. Co. additional information can be obtained from the digital directory or sshy's page (in the case of sshy, a browser extension is required https://addons.mozilla.org/en-US/firefox/addon/sshy-selainlaajennus/ or https://chrome.google.com/webstore/detail/ sshy browser extension/caomdaijfcdopklkecajpkoaiamaegkb).

'''Dialog: ''' 
Lisää sama lähdeviitelisätieto moneen tapahtumaan kerrallaan. 
[Add the same additional source reference information to several transactions at a time.]

Lopuksi aja 'generatecitations'-työkalu (Muodosta lähdeviitteet lisätietojen perusteella). 
[Finally, run the 'generatecitations' tool ([[#Generate_source_citations_from_notes|Generate citations based on additional information]]).]

'''Textbox: ''' 
Lähdeviite [Reference]

'''Button:''' 
Lisää valittuihin tapahtumiin [Add to selected events]

So this does not make source references until the end, but "[[#Generate_source_citations_from_notes|Create source references based on additional information]]" must be run at the end anyway.

----

Direct translation from [https://github.com/Taapeli/isotammi-addons/tree/master/source/AddSourcesGramplet AddSourcesGramplet/README.md]

==== Multimerge Gramplet ====
''Excerpted from the [https://github.com/Taapeli/isotammi-addons/blob/master/source/multimergegramplet/README.md ReadMe.md] for the MultiMerge addon in the Isotammi GitHub Repository.''

The Multimerge Gramplet allows the merging of multiple objects in a single step. This applies to the following object views:
* People
* Families
* Events
* Places
* Citations
* Sources
* Repositories
* Notes
* Media

[[Gramplets_development#Gramplet_Interface|Add the MultiMergeGramplet]] in the sidebar or bottombar of the corresponding view.

===== Usage =====
[[File:IsotammiMultiMergePeople.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Isotammi MultiMerge Gramplet for 3 selected People]]
Select the objects to be merged and click the button "Merge selected objects".

The gramplet will ask which of the selected objects should be the primary object.The gramplet executes the standard merge function pairwise for the selected objects. The user can select the primary object but otherwise the merges are performed using the defaults for each case.

All changes are done under a single transaction and they can be undone from the Gramps menu {{man menu|Edit -> Undo}}.

===== Special handling for families =====

Two families cannot be merged if the primary family is missing a parent but the other family has the corresponding parent. The gramplet checks for this situation and does not allow selecting such family as the primary family. If there is no suitable primary family among the selected families then the gramplet issues the error "Impossible to merge" and stops.

===== Special handling for places =====

Gramps prohibits deleting a Place if it encloses another place. So pruning a branch of the Place hierarchy normally requires deleting from the bottom of the hierarchy upwards.

However, the hierarchy of enclosing places is managed when collapsing a multitude of selected places. So it is possible to select that whole branch, merge the selected branch into a single place and then delete that surviving merged place.

===== Special handling for notes: =====

By default, when merging notes only the text of the primary note is preserved. This gramplet allows saving text from all merged notes by appending the text after the text of the primary note:
{{-}}
===== Automerge =====
[[File:IsotammiAutoMergePlaces.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} After using automerge for all Places with the same Title]]
There is also an "Automerge" feature. Automerge is accessible from its own tab when the Multimerge Gramplet is added to the splitbars of the Places, Sources and Repositories category views.

This will automatically merge all objects with the same name (or title for Source and Places). As instructed by the Radio Button choice, this affects either: only the selected objects; or, all objects. After the operation, a list of merged objects will be displayed.
{{-}}



==== Filter+ ====
[[File:IsotammiFilter+.png|thumb|right|434px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Families category's Filter gramplet compared to the Filter+ addon]]
It is often desirable to use the Filter gramplet interactively find a subset of records. But since Tools, Reports and Exports do not have the option to restrict themselves to that filtered data, this subset either had to be manually re-built as a Custom Filter (which meant discovering which rules corresponded to filter fields) or to Tag the view contents then create a Custom Filter for that Tag.

Filter+ has the option to create a Custom Filter directly from the Filter parameters.

Filter+ gramplets are designed to look very similar to the builtin Filter Gramplets. But Filter+ addon gramplets are slightly enhanced versions. These addons do NOT upgrade the builtins. Just add the Filter+ gramplets to the sidebar of each Category. (It is advisable to remove the builtin from the sidebar as the addons include all the original features.)

The enhancements are:
* There is a new {{man button|Define filter}} button that automatically creates a custom filter based on the given criteria. This makes it easy to create simple custom filters.
* Selecting the Find button also displays the elapsed time to run the filter.
* The “Father”, “Mother” and “Child” allow searching for multiple partial names in the Families Filter+ fields. This behaves the same way as searching Names in the “People” filter. The un-enhanced filter tried to match the entire string exactly. (For example, “en w” matches for the Father in [[Example.gramps|example.gramps]] will find 34 families including: “Lawrence Gill” and “Edward Green”. Adding a Child “b te” reduces the list to 4 families.) This 5.1 enhancement is already present in the 5.2 [[Gramps_{{man version}}_Wiki_Manual_-_Gramplets#Family_Filter|Family category Filter Gramplet]].
* The Citation Filter+ uses “Very low” as the default confidence level. The regular filter defaults to “Normal” (which might miss some citations).

[[File:IsotammiDefineFilter.png|thumb|right|360px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} A Families category custom filter defined by Filter+ gramplet]]
Clicking the {{man button|Define filter}} button will scrape the Gramplet parameters into rules for a Custom Filter. After you add a name for the new Custom Filter, the {{man button| OK }} button becomes active.

The Rules used to simulate the Filter Gramplet in each category (except the Dashboard) are illustrated and listed in the [[Gramps_5.2_Wiki_Manual_-_Gramplets#Filter|Gramplets]] section of the wiki: 
  {{icon|peop}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#People_Filter|People]],
{{icon|rela}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Relationships_Filter|Relationships]],
{{icon|fami}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Families_Filter|Families]],
{{icon|ance}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Charts_Filter|Charts]],
{{icon|even}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Events_Filter|Events]],
{{icon|plac}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Places_Filter|Places]], 
  {{icon|plac}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Geography_Filter|Geography]],
{{icon|sour34}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Sources_Filter|Sources]],
{{icon|cite}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Citations_Filter|Citations]],
{{icon|repo}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Repositories_Filter|Repositories]],
{{icon|medi}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Media_Filter|Media]],
{{icon|note}} [[Gramps_5.2_Wiki_Manual_-_Gramplets#Notes_Filter|Notes]]

[[File:IsotammiFilter+People.png|thumb|right|180px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} People category Filter+ gramplet with Death Event parameters]]
The People category Filter+ Gramplet is expanded to include parameters for searching Death Events.

=====Added Rules:=====
The Filter+ needed some addon rules to support the same parameter filtering as the Filter gramplet.
* HasEventBase+ : HasEventBase+ - used by Filter+
*HasSourceBase+ : HasSourceBase+ - used by Filter+
{{-}}

=== Tools ===
[[File:Tools-Isotammi-tools-menu-51.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Isotammi Tools menu]]
After [[#Installation|installation]] the expert-level Isotammi Tools are available under the {{man menu|[[#Tools|Tools ➡ Isotammi Tools ▶]]}} submenu.

===== Usage =====
* {{Man menu|[[#FilterParams_tool|Tools ➡ Isotammi Tools ▶ FilterParams…]]}}
* {{man menu|[[#Generate_source_citations_from_notes|Tools ➡ Isotammi Tools ▶ Generate source citations from notes…]]}}
* {{man menu|[[#Name_Editor_Tool|Tools ➡ Isotammi Tools ▶ Name Editor Tool…]]}}
* {{man menu|[[#Name_Merge_Tool|Tools ➡ Isotammi Tools ▶ Name Merge Tool…]]}}
* {{man menu|[[#SuperTool|Tools ➡ Isotammi Tools ▶ SuperTool…]]}}
* {{man menu|[[#ZipInstall|Tools ➡ Isotammi Tools ▶ ZipInstall…]]}}
{{-}}
==== Generate source citations from notes ==== 
This tool works together with the "[[#Add_Sources_Gramplet|Add Sources]]" gramplet for the Event category.

The {{man label|Generate source citations from notes}} tool is a specialized tool that can interpret a source reference obtained from a digital directory or SSHY page, which is stored in Gramps. (e.g., for additional information about an event.) Suomen Sukuhistorisallinen yhdistis ry (SSHY, "Suomen" - Finland's, "Sukuhistoriallinen" - Family Historical, "yhdistys" - Association, "ry" - Registered Association) is a nationwide non-profit association founded in 2004 in Finland. Their purpose is to promote genealogy, to store archival material important in genealogy and to publish it in digital form on the Internet. SSHY's digitization project (Digiarkisto) enables archival material to be studied via the Internet. You can find digitized source materials on our website.

The tool then forms the based on the text reference to the source, source, and archive Gramps and deletes the original additional information. The additional information must not contain other text and the source reference must be copied there as it is. The tool processes all additional information in this format at the same time. The SSHY source reference must be retrieved using a special SSHY browser extension (https://addons.mozilla.org/en-US/firefox/addon/sshy-selainlaajennus/ or https://chrome.google.com/webstore/detail/sshy-selainlaajennus/caomdaijfcdopklkecajpkoaiamaegkb )

==== [http://wiki.isotammi.net/wiki/Name_Editor_Tool Name Editor Tool] ====
[[File:Name-Editor-tool-Isotammi-51.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Name editor - tool]]
The {{man label|Name Editor}} Tool standardizes family names in the family tree to eliminate random scribe practices and, to make it easier to find duplicates in the family tree and to merge. For example, Gramps' "MultiMerge" and "Family Auto Merge Tool" work more efficiently the more consistent the nomenclature. In addition, the tool maintains the primary and alternative name types of individuals.
{{-}}
===== Usage =====
After [[#Installation|installing the Isotammi addon]] in Gramps, the tool can be found as the {{Man menu|Tools ➡ Isotammi Tools ▶ Name Editor Tool}} menu item.

The name editing tool lists the people in the family by line, alphabetically by surname and first name, after a short time. At the top left of the list window is a line of text for filtering. Its value targeting can be refined by name parts and gender as well as name type. Regular expressions (regex) can also be used. At the top right of the list window are the editing preferences, which are described in more detail below.

In the list, the person lines are alphabetically by last name and first name. The information in the line is the person's ID in Gramps (Id), gender (M = male, F = female,? = Unknown), surname Prefix, actual Surname, First names, Suffix (contains patro / matrimonial information according to Isotammi's practice), Title (person's Title) and Type (birth, marriage, known, etc.).

The following figure, which filters people with the letter "r" in the list, provides examples of the need to edit. The situation is very typical when the family tree is combined with material from several sources, in which case there is no uniform practice.

* the matronymic should be moved to the Suffix

* suffixes (patronyms and matronyms are mixed in Finnish and Swedish

* patronym is abbreviated (Joh.sson)

* the surname deviates from the recommendation of how to mark the unknown part of the name

* first name and patronymic are the same

===== Use =====
If the filter text targets a name part, uncheck the "All" box and check the desired part (s). If gender does not matter, leave the "All" option on it, otherwise the sexual. The Regex box is checked when the corresponding rule is in the "Filter" text. Filtering is started with the "Search" button and the list then contains only the person lines that match the criteria. The "List All" button returns to the unfiltered list.

Practically worth it

* look at rows filtered, e.g., by women’s first names, because then changes to the rows may not be appropriate for men (e.g., “Christ:” can be safely interpreted as a woman’s name, “Christina,” but for men, it would be “Christer” or Christian).

* first take care of the abbreviations of the name parts. For their initial filtering, write "Filter" in the text "Filter", for example ";", ".", ";", ".sson" or other string used by scribes to abbreviate parts of names in the congregation.

* targets conversions to people selected from the list bar. The selection can be made on all rows at once or by picking individual rows. The latter method can be tedious if the original filter selected a large number of rows. This will refine the filtering text (e.g. ":" i.e. select all people's abbreviated first names and patronymics, but "men, first name," Henr: "would only list lines where the first name" Henr: "can be safely decompressed to" Henric ".

===== Name type =====

Gramps has a number of standardized name types (Birth Name, Avion Name, Known Name, Unknown), in addition to which the genealogist can define his own types (common ones include Military Name, Taken Name, Noble Name, Artist Name). A person can have several names, one of which is selected as the primary and appears in the person list, and the others are set as alternate names. However, each must have a first name and a patronymic and / or surname. See See also Quality Guidelines for Genealogists on naming conventions.

The tool loads all name types in the genealogy from the selection list and rows can be filtered and edited by name type. In the person line of the list, the primary name type is in bold.

===== Editing rules =====

At the top right of the list window are fields and buttons for editing. In basic operation, first select the line of the name part to be edited, write the current value ("Old value") and the desired value ("New value"). For example, in men "Joh." in the first name filtered, the current value is written Joh. and the new value Johan.

The edit only affects the rows that are selected in the list. Filtering alone does not select rows!

All rows are selected at once with the key combination CTRL + A.

The replacement affects part of the text. For example, if the first name is "Lars Sim:" and "Sim:" is to be converted to "Simon", write the old value Sim: and the new value Simon. The first name after this is "Lars Simon".

The Regex rule is available by ticking.

Editing can be activated with "Special Functions", the ticking of which opens up possibilities for moving parts of names between them. (examples of use!)

The editing is performed with the "Replace" button. The "Undo previous change" button cancels the last corrections. An incorrect conversion can also be undone by holding the selected rows and performing a counter conversion, e.g. Old = "Henricz"> New = "Henric".

Due to the possibility of cancellation, it is worth learning how to use the tool by boldly trying different variants, eg for one or a few names at a time.

===== Please note =====

Clicking on the list bar opens the respective personal editor. Point-specific changes can be made to it, i.e. only the modification necessary for the person concerned, such as transfers between the primary and alternative names, the correction of a very rare surname clerical error, or the transfer of a surname that has crept into the patronymic to the surname.

Gender is an integral part of editing. The name editing tool cannot be used to edit genders, but the "NameMerge" and "SetGender" tools are available. When used in advance or interrupted by the Name Editor, interrupting the gender encoding improves the impact of the Name Editor.
{{-}}

==== [http://wiki.isotammi.net/wiki/Name_Merge_Tool Name Merge Tool] ====
[[File:Name-Merge-tool-Isotammi-51.png|thumb|450px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Name Merge tool]]
The {{man label|Name Merge}} Tool standardizes family names by combining the same but slightly differently spelled first or last name names so that the names of the people are in the genealogy for the Genealogist's own use or for the recipients of the genealogy, either as printouts or gedcom transfer files. The merger significantly reduces the name editing work with the ''Name Update Tool''. The Gramps ''MultiMerge'' and ''Family Auto Merge Tool'' also work more efficiently the more consistent the nomenclature.

Some common first names have been written by parish scribes in dozens of different forms, based on Swedish and German naming practices (e.g. the name family Heikki <Henric, Henrik, Heinrich, Hinnrich, Hindrick, Hen:, ...). The same variegation exists in other parts of the names (e.g., v/w/fv and f/ph spellings have been used). There is a similarity in surnames, especially in the registration of long foreign surnames.

===== Usage =====
After starting Gramps, the tool can be found in the Isotammi Tools group - NameMerge opens after a short time after thinking about the list of names of all people's first names, with their personal numbers - at the top of the list window there are gender selections,

The list shows the relevant part of the name and gender in alphabetical order. If the same part of the name has known and unknown genders, the same form of name is in the list of two, followed by the number of persons in the cases in question.

At the top is the "Set gender" checkbox, which automatically updates the gender in the merger for each person involved in the merger, if there is a single case of gender that is known to be merged.

===== Use =====
To merge names from a list, follow these steps:

To be merged, left-click and CTRL + left-click the last name in successive names. Discontinuous names can be selected and canceled with the left mouse click of SHIFT + - you can remove the name from the selected ones with the left mouse click of SHIFT + (a good way if there are non-merged names among the ones selected in succession)

The merge is performed with the MERGE button at the top. The merge is canceled by selecting Gramps Edit> Cancel. In the picture, three "Adolf" name spellings are selected and the Merge button is pressed. The tool suggests the form with the most people as the primary one.

The Merge button opens a new window Select primary name ". Where the desired name format is selected as the primary (eg" Adolf "e instead of Adolph" in the figure). When you double-click the merged person after merging, the "Show person" window opens, listing all the people involved in the merger. When you select a person from the list, their Personal Edit window can be opened with the Open button.

In the main Gramps window, the cursor moves in the People list. to the selected person, in which case you can open the person's Relationships window (if necessary, remove the filter from the list and the transfer will take place). This is useful if, for example, the person's first name contains information about his or her parents. In this case, it is not possible to form family relationships automatically when forming huskies. Parents can be corrected in the Relationships window. Note that the most direct way to add parents is to select "add a child to an existing family" using the father's or mother's last name as the search key.

After merging, only the selected primary name format, the number of people and the set gender remain in the tool list.

===== Tip =====
There are cases at the end of surnames that require other means than merging surnames. The following image shows a few examples of these:

* The last name starts with a lowercase letter (e.g. "barck"). If the number is small, the fastest way is to select the last name from the list, open the person for editing with a right-click and correct the last name directly in the person's name.

* The part of the prefix left in the surname (e.g. "d." in the name "d. Pahlen") is corrected as above.

* The surname contains information about its type (e.g. "eine geborene", "f.", "Född"). The first, rare situation is corrected as above. There are usually dozens of the latter cases. The correction is made with the "Name Editor" tool at once, replacing the text "F." Or "Född" with the last names. Note that the text to be replaced includes a space and that the text is replaced by leaving the new value blank.

==== Family Auto Merge Tool ====
The [http://wiki.isotammi.net/wiki/Family_Auto_Merge_Tool Family Auto Merge Tool] is intended for cleaning the parish's Hiskipuut stock. The tool merges the children of the parents into one family and adds a Marriage event to the family. Only parents whose names are in exactly the same form in the marriage and baptismal events of Hezekiah are directly interpreted as the same family. The tool records how many connected families it formed. The efficiency of the tool can be improved by using the Name Merge Tool and Name Editing tools mentioned above.

The next step is the researcher's own judgment. Family reunion continues in Gramps Families view. It is first sorted by the name of the husband, after which it is easy to identify the families left behind by the tool due to small differences in the name of the wife joining. Merging families in a view is done two at a time with Gramps' "Merge" tool or "Multimerge" tool for merging multiple families at once.

Once the men have been dealt with, the Families list is further sorted by wife's name, allowing families with small differences in husband's names to be combined accordingly.

In the Gramps interface, you should add the "Kids" tab to the Bottom bar and the "Events" tab to the Sidebar. They can be used to check that there are no visible flaws in the reunited family, e.g., the children have too long a time interval or the marriage event does not fit the children’s time. These are signs that unrelated families or children have been merged into the same family.

{{-}}
==== SuperTool ====
[[File:SuperTool-tool-Isotammi-51.png|thumb|450px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} SuperTool]]
From [https://github.com/Taapeli/isotammi-addons/blob/master/source/SuperTool/README.md SuperTool/README.md] on GitHub

This is a general purpose scripting tool that can be used to do "ad-hoc" queries against a Gramps family tree/database. The queries are expressed in the Python programming language so the tool is most useful for programmers. But the intent is also that the tool is easy enough to allow regular Gramps users to make use of it.

The queries can be saved as script files that any user may then load into the tool — without necessarily understanding the details. The queries can also be saved as Generic rule-based Custom Filters that may be used throughout Gramps.
=====Table of contents=====
From the SuperTool user docs on GitHub

* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#introduction Introduction]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#user-interface User interface]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#basic-examples Basic examples]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#pre-defined-variables Pre-defined variables]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#example Example]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#accessing-gramps-objects Accessing Gramps objects]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#general-variables General variables]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#help-feature Help feature]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#options Options]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#row-limit Row limit] - 1,000 Gtk toolbox Row limit mitigated in May 2024 {{new|1.4.2 of SuperTool}}
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#editing-objects Editing objects]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#download-or-copy-as-csv Download/copy as CSV]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#title-field Title field]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#initialization-statements Initialization statements]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#statements-executed-for-every-object Statements executed for every object]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#supported-object-types Supported object types]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#parameterized-queries Parameterized queries]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#modifying-the-database Modifying the database]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#deleting-objects Deleting objects]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#saving-the-query-as-a-script-file Saving the query as a script file]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#saving-the-query-as-a-custom-filter Saving the query as a custom filter]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#using-predefined-custom-filters Using predefined custom filters]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#running-from-the-command-line Running from the command line]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#proxy-objects Proxy objects]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#date-arithmetic Date arithmetic]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#include-files Include files]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#the-result-object The 'result' object]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#settings Settings]
* [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#more-examplesMore examples]

* '''[https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#reference Reference]'''
** Properties supported by the various object category types.
** [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#global-variables-and-functions global variables and functions]
** [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#command-line-options Command line options]
** [https://github.com/Taapeli/isotammi-addons/tree/master/source/SuperTool#sample-files Sample files]

=====Direct Access to Gramps Functions=====
Initially, the higher order functions of certain [https://docs.python.org/3/library/ Python Standard Library] modules ([https://docs.python.org/3/library/os.html os], [https://docs.python.org/3/library/sys.html sys], [https://docs.python.org/3/library/re.html re], [https://docs.python.org/3/library/functools.html functools], [https://docs.python.org/3/library/collections.html collections]) are available in SuperTool by default. And the Gramps [https://gramps-project.org/api_5_0_x/gen/gen_lib.html?highlight=gen%20lib%20family#primary-objects Primary Object] matching the currently active view ([https://gramps-project.org/api_5_0_x/gen/gen_lib.html?highlight=gen%20lib%20family#module-gramps.gen.lib.person Person], Family etc) are implicitly defined when the tool is started. [https://gramps-project.org/api_5_0_x/gen/gen_lib.html?highlight=gen%20lib%20family#secondary-objects Secondary objects] (like [https://gramps-project.org/api_5_0_x/gen/gen_lib.html?highlight=gen%20lib%20family#module-gramps.gen.lib.eventtype EventType], PlaceName) are ''not'' defined and the script has to explicitly import them (in the "Initialization Statements" section) if they are needed.

This tool works in the Gramps versions 5.x and later. It will be installed in the "Isotammi tools" submenu under the Tools menu.

The tool allows arbitrary Python code so it can also be used to modify the database.

For instructions on how to use this tool please visit the [https://github.com/Taapeli/isotammi-addons/blob/master/source/SuperTool/README.md SuperTool] - Instructions on Github.

===== Generic Rules for Supertool =====
[[File:IsotammiGenericRule.png|thumb|450px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Isotammi Generic Rule]]
SuperTool simplifies designing a new database query and provides an option to immediately apply that query design to the Tree.
However, to use that query design as a limit elsewhere (in a View, with a Tool, on a Report, or when Exporting a portion of your Tree) in Gramps, the query 'initialization' and 'statements' specifications must be inserted into a Generic Rule. And then that Titled (named) Rule can be used in Custom Filters.

* Generic person filter
* Generic family filter
* Generic event filter
* Generic place filter
* Generic source filter
* Generic citation filter
* Generic repository filter
* Generic media filter
* Generic note filter
=====SuperTool Scripts=====
If you create library folder with a series of Scripts, it is helpful to [[Gramps_{{man version}}_Wiki_Manual_-_Settings#File_Chooser|add a Bookmark for that folder to the GTK File Chooser]]. This simplifies navigating to your script library folder.

'''Discourse support forum threads''' ([https://gramps.discourse.group/tag/supertool-script supertool-script] and [https://gramps.discourse.group/search?q=tags%3Aisotammi isotammi] category searches)
* '''Names'''
:*Scripting Tutorial: [https://gramps.discourse.group/t/tree-vivisection-experiments-with-the-isotammi-supertool/1621 mark surname origin as '''Patrilineal'''] if matches father surname
:* Scripting Tutorial: [https://gramps.discourse.group/t/tree-vivisection-experiments-with-the-isotammi-supertool/1621/11 mark surname origin as '''Taken'''] if matches spouse surname
:* Scripting Tutorial adaptation: [https://gramps.discourse.group/t/family-nick-name-propagation/1654/7 Family Nickname propagation to descendants]
:* Scripting Tutorial adaptation: [https://gramps.discourse.group/t/hacking-with-display-formats-for-names/1673/5 monogram placeholders for sorting] (French)
:* [https://gramps.discourse.group/t/how-to-display-two-surnames-ie-primary-married-name/3216/23 Generating a Couverture name (the "née" form) as a Primary name]
:* [https://gramps.discourse.group/t/supertool-script-to-move-surnames-with-patronymic-type-to-given-names/5888 Append Patronymic origin surname to Given name]
:* [https://gramps.discourse.group/t/supertool-script-to-move-surnames-with-patronymic-type-to-given-names/5888/4 Transform Given/Patronymic/Taken origin surnames] (split "Taken" in multiple surnames to separate "Married name")
* '''Date scripts'''
:* [https://gramps.discourse.group/t/making-date-input-more-flexible/2814/18 Re-parse date text strings]
:* [https://gramps.discourse.group/t/making-date-input-more-flexible/2814/4 Invalid ccyy-yy Date re-Formatter] (Brother's Keeper ccyy-yy date spans)
:* [https://gramps.discourse.group/t/making-date-input-more-flexible/2814/6 Switch locale and parse Italian dates]
:* [https://gramps.discourse.group/t/bulk-move-data-from-one-field-to-another/1623/1 migrate date entered in wrong field]
* '''Citations'''
:* [https://gramps.discourse.group/t/duplicate-citations-with-supertool/1692/4 Duplicating Citations]
:* [https://gramps.discourse.group/t/i-really-need-a-citations-filter-which-gives-the-citations-belonging-to-a-subset-of-people/2995 Creating Citations filter rules with SuperTool]
* '''Media'''
:* [https://gramps.discourse.group/t/creating-new-filter-rules-should-i-use-supertool-for-these/3171 Creating Media filter rules with SuperTool]
:* [https://gramps.discourse.group/t/how-are-relative-vs-absolute-paths-marked/5707/3 Discriminate between Relative and Absolute Media Paths]
:* [https://gramps.discourse.group/t/supertool-script-to-bulk-edit-media-descriptions/7026 Media Title and Integrity Checker] : Urchello's Bulk Media Title update. (For use after renaming media files on storage device and re-linking with the [[Addon:Media_Verify_Tool|Media Verify]] addon tool.) This script updates the media object's Title to match the new filenames
* '''Notes'''
:* [https://gramps.discourse.group/t/styled-note-markup-trimmer-gramplet/5396/10 Note Markup cleanup] : Kari Kujansuu's Note cleanup tool. Remove selected overlapping markup by type
* '''Privacy'''
:* [https://gramps.discourse.group/t/how-to-display-non-private-attributes-and-make-them-private-with-supertool/3468/6 make selected object '''Private''']
:* [https://gramps.discourse.group/t/how-to-display-non-private-attributes-and-make-them-private-with-supertool/3468 Find specific Attributes and tag as '''Private''']
:* [https://gramps.discourse.group/t/how-to-set-private-record-for-multiple-people/2885/6 Set selected people as Private]
* '''Miscellaneous'''
:* [https://gramps.discourse.group/t/how-to-save-a-list-of-plugins/1992/4 gather a list of registered Gramps Plugins]
:* Simple Access Tutorial: [https://gramps.discourse.group/t/what-is-the-minimalistic-experiment-with-simple-access/4404 Adapting the example developer snippets in the Gramps Simple Class to SuperTool] (link a standard Gramps module)
:* [https://gramps.discourse.group/t/using-supertool-to-import-attributes-and-urls-an-example/2094 Parse URL and ID numbers from Ancestry CSV]

'''The SuperTool scripts of Patrice Legoux''' (source and note in French. Coming soon!)
[https://gramps.discourse.group/t/supertool-changing-sources-of-citations/2117/4 ''Recommended reference documents for SuperTool'']

* '''On Discourse:'''
:* [https://gramps.discourse.group/t/correcting-the-spelling-of-names/3402/22 Tweaking the Sort Order for Names override]
:* [https://gramps.discourse.group/t/supertool-help-accessing-groups-as-value/2026/3 Global reset the Sort Order for Names override]
:* [https://gramps.discourse.group/t/create-excel-csv-list-of-people-dates-and-places/3168/5 generate a CSV list of People, dates and Places]
:* [https://gramps.discourse.group/t/reversing-an-object-handle-to-its-creation-date/2614/5 Calculate an object's creation date from its handle]
:* [https://gramps.discourse.group/t/help-searching-for-citations/2283/10 find Citations for tagged persons]
:* [https://gramps.discourse.group/t/creating-a-citation-attribute/1628 Set citation URL attribute] (requires correction)
:* [https://gramps.discourse.group/t/dateval-field-of-date-object-content/2039 The boolean at the end of dates returned with <code>obj.date.dateval</code>]
:* [https://gramps.discourse.group/t/merge-pop-up-menu-choice-for-the-clipboard/1981/7 Merge multiple objects]
:* [https://gramps.discourse.group/t/a-little-answer-to-geps-015-repository-research-support-using-supertool/1771 create a Repository research plan]
:* [https://gramps.discourse.group/t/need-to-build-a-path-field-for-my-media-objects/1758/2 set .jpg media paths]
* [https://plegoux.notion.site/Include-des-filtres-Supertool-ST_filters_init-py-version-1-6-9aa15c5eb961403294381a1c17ea71f2 PLegoux filter library]
* [https://plegoux.notion.site/Filtre-Supertool-automatisant-la-recherche-d-individus-ou-de-familles-dont-un-v-nement-n-a-pas-de-s-2c29fb65042445b7bb8cd7a730d081bc Filtre Supertool automatisant la recherche d’individus ou de familles dont un événement n’a pas de source probante] [filter for unsourced Events]
* [https://plegoux.notion.site/Import-d-un-fichier-Gedcom-obtenu-sur-Internet-afin-d-y-trouver-des-points-communs-avec-mes-propres--1b2a86f2b36e498e95fc9d99c14d1d88#59280f6480404bd2913cdbd30bf20804 Import Gedcom to find points-in-common]
* [https://plegoux.notion.site/G-n-rations-avec-SuperTool-155b33dc2f5e801e9899e34b907b86ff?pvs=4 Ses ancêtres par générations avec SuperTool] (His ancestors by generations with SuperTool)
* [https://www.geneanet.org/forum/viewtopic.php?p=2460492#p2460492 Supertool et attributs d'évèments partagés] (updating shared event attributes)
*


=====See also:=====
* [https://gramps.discourse.group/t/supertool-run-a-set-batch-of-scripts/5835 creating and using SuperTool script batch files] for regular maintenance Command Line/Terminal/Console
* [[Addon:Generic DB Access lib|Generic DB Access lib (aka libaccess)]] addon - an experimental library that provides generic access to the database and the gen.lib interface(AKA The core library of Gramps objects ).
{{-}}

==== FilterParams tool ====

[[File:IsotammiFilterParams125.png|thumb|450px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Isotammi FilterParams v1.2.5 dialog]]
===== Usage =====
After [[#Installation|installing the Isotammi addon]] in Gramps, the tool can be found as the {{Man menu|Tools ➡ Isotammi Tools ▶ FilterParams…}} menu item.

===== Introduction =====
Originally designed for Gramps 5.1 to simplify access to the Parameters in Custom Filters, this tool evolved into a complete enhanced replacement for the {{man menu|<category> Filter Editor}} found in each View category's {{man menu|Edit}} menu. The FilterParams tool dialog flattens the number of steps needed to adjust parameters in a custom filter.

This tool within Gramps provides flexible functionality for creating, editing, pruning, and testing custom filters. It does not apply the filters directly to the Gramps views. The '''FilterParams''' tool helps to more efficiently revise and test Custom Filters. The '''Test run''' button not only validates the Custom Filter is working, generates a functional (open an Object Editor, make the record "active" or copy to clipboard) dialog with counted filtered results. It also offers advanced usability features like quick access to key options and simultaneous updates for repeated parameters.

===== Filter Management =====

* '''Add New Filter:''' Build custom filters to find specific groups within your family tree data.
* '''Delete active filter:''' Remove filters you no longer need. (After a Delete, the list advances to the next Custom Filter in the list. The up and down cursor keys move the previous/next filter.)
* '''Edit Existing Filters:''' Modify your filters to refine your searches and get more accurate results.
* '''Clone Filters:''' Duplicate an existing filter to use as a starting point for a new, similar filter.
* '''Test run the active filter:''' Run an interruptible progress bar test of the active file
* '''Save modifications:''' Commit the selection changes to the active filter.
* '''Export and Import:''' Editable clipboard with XML of the current filter [https://github.com/Taapeli/isotammi-addons/blob/master/source%25252FFilterParams%25252FREADME.md#export-and-import {{New|FilterParams v1.2.5}}]

===== Filter Application (Test Run) =====

Doing a '''Test run''' of the selected Custom filter will generate an independent window with the counted results of the filter. (This means you can close the main FilterParams dialog without closing this window. The name of the Custom Filter heads the results table and can be used to re-open the Filter Params dialog to that filter.)

* '''Apply Filters (Test Only):''' Run your custom filters to generate a ''test'' list of individuals, families, or events that match your criteria. Results are displayed in a separate dialog.
* '''Targeted Searches (Test Only):''' Narrow down your research focus for testing purposes.
* '''Progress Indicator with Cancel Button:''' Monitor the progress of your filter during the ''test'' run. A functional '''Cancel''' button, allows you to stop the process if you accidentally created a loop in the filter design.
* '''Error Handling:''' Displays error messages if something goes wrong with the filter creation or execution.

===== Quick Access Options =====

* '''Invert Search Results:''' Quickly reverse the search results to find entries that *do not* match your criteria.
* '''Enable/Disable Regular Expressions:''' For advanced users, RegEx can be used to search for data that fits specific patterns.
* '''Quick Change of Rule Parameters:''' Adjust rule parameters directly without needing to drill down into the full editor interface.
* '''Simultaneous Parameter Updates:''' If a parameter is used multiple times within a filter, updating it once will automatically update all instances across the filter.
* '''Color Coding:''' The tool uses color coding to clarify multi-stage and multi-rule structuring of custom filters, making it easier to understand how different parts of the filter interact. It is fully compatible with both light and dark mode themes in Gramps.
{{-}}
===== Import and Export =====
[[File:IsotammiFilterParamsExport.png|thumb|450px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Export XML editing dialog]]

===== Examples =====
Example export illustrates the following 3 stage custom filter:

<nowiki>
<filters>

<object type="Person">
<filter name="Some Event in place X" function="and" comment="People filter : who have the events">
<rule class="MatchesEventFilter" use_regex="False" use_case="False">
<arg value="Event in place x"/>
</rule>
</filter>
</object>

<object type="Event">
<filter name="Event in place x" function="and" comment="Event filter : occurred in a place">
<rule class="MatchesPlaceFilter" use_regex="False" use_case="False">
<arg value="In place x"/>
</rule>
</filter>
</object>

<object type="Place">
<filter name="In place x" function="and" comment="Place filter : enclosed by a place">
<rule class="IsEnclosedBy" use_regex="False" use_case="False">
<arg value="P0450"/>
<arg value="0"/>
</rule>
</filter>
</object>

</filters>
</nowiki>


==== ZipInstall ====
[[File:IsotammiZipInstall.png|Right|thumb|350px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Isotammi ZIPInstall]]
Tool to install an addon from a ZIP or a .tgz compressed download file.

This is very efficient when downloading GitHub code ZIP files. The ZIPInstall GtkFileChooser dialog has a button to change to the "Downloads" folder. Sort on date and your recent download is on the first line. The install option automatically checks the Gramps Registry and puts the updated code in the correct plugin subfolder.

The ZIPinstall will confirm that you want to overwrite and offer the option to backup the existing addon.

Isotammi [https://github.com/Taapeli/isotammi-addons/tree/master/source/zipinstall ZipInstall] GitHub folder.

==== Import CSV sources ==== 
The "''[https://github.com/Taapeli/isotammi-addons/tree/master/source/importsources Import CSV sources]''" Tool is a specialized tool that can load Gramps sources from a csv (comma separated values) file. For each line of the file, the tool generates an Archive (optional, source, Additional source-related Information (optional) and Property (optional) for Gramps.

The tool is installed in the Gramps Tools> Isotammi tools folder.

The tool is fed with a .csv file that reads the information under the following column headings:
- title (pakollinen)
- author
- abbrev
- pubinfo
- repository
- ....

Heading titles should be written exactly like that, in lower case. The order of the columns does not matter and not every one needs to be included. Other columns are ignored.

Each line creates a new source and is given a sequential ID numbering: S0001, S0002, etc. Therefore, any gramps-id information in the file is not used. If there are already sources and archives in the database, duplicate ID values may become available (but they can be renumbered later with Tools -> Family Tree Processing -> "Rearrange Gramps IDs" to Select Source and Archive Items)

The contents of the columns title, author, abbrev, and pubinfo are stored as is in the source.

The Repository column has special handling:

- The repository can be empty, so the source is not attached to any archive.

- If the column contains an id in square brackets (format [Rxxxx]), then the source is appended to the corresponding archive if it is already in the database. If. archive does not exist, a new archive named "[Rxxxx]" is created and the source is attached to it.

- If there is another value in the column, it is interpreted as an archive name, creating a new archive with that name and appending the source to it. However, if the same name is used multiple times, the tool only creates one archive. If the name is already in a position in an existing archive, the tool cannot associate the new name with it (this can be corrected later by merging the archives in question).
{{-}}
==== Convert NARC URLs ====
Convert the obsolete URLs of the Finnish National Archive's digital resources found in the Gramps database into Astia addresses.

Example:
Typically converts [http://digi.narc.fi/digi/view.ka?kuid=nnnnnnnn http://digi.narc.fi/digi/view.ka?kuid=nnnnnnnn]   to [https://astia.narc.fi/uusiastia/viewer/?fileId=xxxxxxxxx&aisenoId=yyyyyyyyyyy https://astia.narc.fi/uusiastia/viewer/?fileId=xxxxxxxxx&aisenoId=yyyyyyyyyyy]

Uses the conversion service of the National Archives, which unfortunately does not work for all addresses.

Affects the addresses in Notes and on the people's Internet tab.

[[How_to_make_a_backup|Make a backup]] first. Start from the {{man menu|Tools -> Isotammi}} submenu. The conversion starts immediately, it can be interrupted with the {{man button|Cancel}} button. The changes made can be canceled with the {{man menu|Edit -> Undo}} function or the {{man menu|Family Trees -> Abandon Changes and Quit}}.

{{-}}

=== Rules ===
{{stub}}

==== Events with an invalid/valid date ==== 
[[File:IsotammiInvalidDateRule.png|thumb|450px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Events with Invalid Date Rule]]
''Events with an invalid date''/''Events with a valid date'' are rules that can be used to search for events with incorrect dates. These are not exactly opposites of each other, as the event may also lack date information, in which case it does not match either rule.
{{-}}
====Generic <Object> filter ====
[[File:IsotammiGenericRule.png|thumb|450px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Isotammi Generic Rule]]
Generic Rules allow a Query to be directly saved as a reusable custom Rule. These Generic Rules were created as an accessory to the '''[[#SuperTool|SuperTool]]''' query builder, editor, and executing shell. Queries in the SuperTool have a compatible syntax and segmentation with fields of the Generic Rule.

If you prefer to design queries manually, a simple free-form text editor and query execution shell in the [[Addon:QueryGramplet|Query Gramplet]] addon. However, for use in a Generic Rule the query must be composed in the exact syntax expected. There is no validation nor safety nets in the Generic Filter Rules. For this reason, it is recommended that syntax be tested in SuperTool. Then the Custom Filter be 'Test run' with the [[#FilterParams_tool|FilterParams]] addon tool... which is the ''only'' custom filter tool with a capability to abort a query in progress.
* Generic person filter
* Generic family filter
* Generic event filter
* Generic place filter
* Generic source filter
* Generic citation filter
* Generic repository filter
* Generic media filter
* Generic note filter

=== Exporter ===
{{stub}}

{{-}}
==== Isotammi XML export====
[[File:Isotammi-XML-export-Isotammi-51.png|thumb|450px|right|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Isotammi XML export - Export options dialog.(Options Highlighted)]]
Exporter for {{man label|Isotammi XML export}} expands the options available compared to the builtin [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Gramps_XML_.28family_tree.29_export|Gramps XML (family tree) export(er)]].

Choose Menu {{man menu|Family Trees ->Export...}} then select {{man button|Next}} and select {{man label|Isotammi XML export}} then select {{man button|Next}} and choose the file format specific export options you want to use and then select {{man button|Next}} to choose your filename and location and output the file.

===== File format specific export options=====
Listed underneath the "Filters and privacy" section you have the following file format specific export options:

* Use Compression
* Include media
* Description: adds a user description to the output file.
* Material type - describes the internal annotation in the header of the export file. Used by the Isotammi project's automated processing tools to correctly route the data into their master database.
** Family tree
** Place Data
** Hiski Tree - [https://hiski.genealogia.fi/historia/indexe.htm HisKi project includes lists of christenings, marriages, burials and moves for most Finland parishes] - HisKi is a [https://www.britannica.com/topic/portmanteau-word portmanteau] of the finnish term "historiakirjat" (in english, "historical parish books"). HisKi Trees are isolated branches related to a single citation processed by members of the Genealogical Society of Finland. (In their project, if a parish book has separate citation worthy entries for a christening, marriage and funeral; then there might be 3 duplicate Persons and duplicates for each unique associated person in the citation. Merging is processed as a separate operation from data entry.)

{{stub}}

Using any of these options adds the following unsupported section entries to [[Gramps XML]] output:

<pre>
<isotammi>
<researcher-info>
</researcher-info>
<material_type>Family Tree</material_type>
<user_description>
This is my family tree test with Isotammi addons
</user_description>
</isotammi>
</pre>
{{-}}

==See also==
* [https://isotammi.net/ Isotammi], the national database of the Finnish Genealogical Society.
* [https://github.com/Taapeli/stk-addons stk-addons] - Additional modules and programs for the genealogy application Gramps.
* Search [https://mattkmmr.github.io/gramps-addons-listings/?catg=All&proj=isotammi Matt's Gramps Addon List] for Isotammi contributions.
* Inspect the current updates [https://raw.githubusercontent.com/Taapeli/isotammi-addons/master/addons/gramps51/listings/addons-en.txt /listings/addons-en.txt] file in the Isotammi Where to check: https://raw.githubusercontent.com/Taapeli/isotammi-addons/master/addons/gramps51 URL in the [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Third_party_addons_management|Third party addons management]] Preferences. (See the [[{{man version}}_Addons#See_also|main addons list]] for the default list.)
*Feature Request [https://gramps-project.org/bugs/view.php?id=12546 12546]: Expand Gramps XML to support "Description" tag from Isotammi XML export(er)

{{man note|Webpage originally duplicated from Isotammi and translated to English and expanded.|Collected 11 May 2021 [http://wiki.isotammi.net/wiki/Gramps-laajennukset http://wiki.isotammi.net/wiki/Gramps-laajennukset]}}

[[Category:Addons]]
[[Category:Plugins]]

Addon:Historical Context

2025-09-26T04:58:32Z

ErickLedger: remove extra "the"

{{languages|Addon:Historical_Context}}
{{Third-party addon}}
[[File:HistoricalContext-gramplet-detached-example-60.png|thumb|right|450px|Example of the detached/undocked "Historical Context Gramplet" default output showing untinted rows for Historical Context during the life time of Blanco, Daniel (1752-1805) from the Example.gramps family tree.]]
The {{man label|Historical Context gramplet}} based on the basic concept is that the events in world history during a Person's lifetime provide context to the other events of their life. So the default lists of world events might include pandemics, wars and other socio-political pressures. You can edit the lists or add your own. So you might make a list of genealogical record stores that are valuable to be checked for specific eras.

Some additional documentation is currently in the GitHub (online code development management system) repository of addon developer Kaj Mikkelsen. Review the [https://github.com/kajmikkelsen/HistContext/blob/master/README.md README.md] in the [https://github.com/kajmikkelsen/HistContext HistContext] repository.

==Usage==
Available to be added on the Dashboard, People and Relationship category views, this Gramplet displays historical events that occurred within the lifespan of the active person.

It references [[Addon:Historical_Context#Event_Lists|Historical Context event lists]] which have the start year, end year, the Event descriptions and a URL about that Event.

The default list output shows untinted rows for Historical Context during the life time of the active person.

A double-click on a row will open your preferred browser at the provided Link.
{{-}}
=== Configuration options ===
[[File:HistoricalContext-gramplet-options-tab-defaults-60.png|thumb|right|450px|Configuration options dialog]]

The {{man menu|View -> Configure...}} offers a variety of filtering options for the lists of Events.

* {{man label|Rows starting with this in the text column will be hidden:}} <code>Filter out</code> string - excludes Events where the "Text" column starts with a particular exact string
: If the string is set to "Cen", then all lines where the text starts with "Cen" will be filtered out. (i.e., "Census" as well as "Century")
* {{checkbox|0}} {{man label|Use filter:}} - ''Use filter'' (deselected by default),enables the filter if selected.
* {{man label|Show outside life span:}} {{checkbox|1}} ''Show outside life span'' (selected by default), show only those in the life span of the Active Person.

* {{man label|Foreground color items in lifespan:}} - (black, default) text color
* {{man label|Background color items in lifespan:}} - (white, default) shading
* {{man label|Foreground color items outside lifespan:}} - (black, default) text color
* {{man label|Background color items outside lifespan:}} - (light grey, default) shading
* {{man label|Select from files}} - Shows the available [[Addon:Historical_Context#Event_Lists|Event Lists]]

Select the {{man button|Save}} button to apply the changes.

=== File locations ===
The ''Event Lists'' can be saved in the following location:
* file path: gramps\gramps60\plugins\HistContext
==== Event Lists ====
The Historical Context event lists are CSV lists of dated Historical Events (with the semicolon as the delimiter) that are loaded and compared against the lifespan (birth year through death year) of the Active Person. These seven files come with the addon and can be changed with any editor that saves in plain text:
* [https://github.com/gramps-project/addons-source/blob/maintenance/gramps60/default_data_v1_0.txt <code>default_data_v1_0.txt</code>] - combined list of historic events
* [https://github.com/gramps-project/addons-source/blob/maintenance/gramps60/pandemi_v1_0.txt <code>pandemi_v1_0.txt</code>] - list of Pandemic Events (after 1500 CE)
* [https://github.com/gramps-project/addons-source/blob/maintenance/gramps60/da_DK_data_v1_0.txt <code>da_DK_data_v1_0.txt</code>] - list of Dansk historical events
* [https://github.com/gramps-project/addons-source/blob/maintenance/gramps60/en_US_data_v1_0.txt <code>en_US_data_v1_0.txt</code>] - list of USA Presidential terms
* [https://github.com/gramps-project/addons-source/blob/maintenance/gramps60/HistContext/en_US_involuntary_v1_0.txt <code>uk_UA_data_v1_0.txt</code>] - list of Ukrainian historical events
* [https://github.com/gramps-project/addons-source/blob/maintenance/gramps60/HistContext/en_US_involuntary_v1_0.txt <code>en_US_involuntary_v1_0.txt</code>] - involuntary commitment policies in the USA
* [https://github.com/gramps-project/addons-source/blob/maintenance/gramps60/HistContext/en_US_prejudice_v1_0.txt <code>en_US_prejudice_v1_0.txt</code>] - socio-political prejudice trends in the USA
* If you have created a custom Event file (named <code>custom_v1_0.txt</code>) it will be shown.

===== CSV format =====
You can create a custom Event file (named <code>custom_v1_0.txt</code>) and those Events will be merged into the list.
{{man menu|After creating the custom Event file, adding it as a Media object means the file will be included in backups with media. And if the default viewer for .txt files is a text editor instead of a simple view, then you can use Gramps to add or remove Events from its historical event list.}}

The format is one Event per line, each line. Short lines or those with too few (less than 3) delimiters will be skipped:

<code>start date;end date;description;URL hotlink</code>

For Events that only last one year, enter the same year for both start and end date. For ongoing Events, use <code>Today</code> for the end year. If either of the dates are missing, the gramplet assumes a life span of the Preferences limit for "Maximum age probably alive".

When entering a URL from services like Wikipedia, remove the subdomain language (i.e., <code>en.</code> for English) or platform (e.g., <code>m.</code> for mobile indicator subdomain). This allows Wikipedia to adapt to the target machine.

==== configuration options ====
The customizations for this Gramplet are stored in 3 locations: a common <code>HistContext.ini</code> the gramplet's folder, distributed splitbar <code>.ini</code> files for each view mode (e.g., <code>People_personlistview_sidebar.ini</code> in the <code>gramps/gramps{{Stable_branch}}</code> folder) and the <code>gramps.ini</code> file in the [[Gramps_Glossary#user_directory|Gramps User Directory]].

The undocked size options are saved independently in the <code>.ini</code> files for the splitbars in each view mode. The <code>gramps.ini</code> file merely has the window position for the undocked dashboard gramplet.

<pre>
[HistContext]
name=HistContext
height=20
expand=True
detached_width=602
detached_height=496
state=maximized
help_url=Addon:Historical_Context
navtypes=['Person', 'Dashboard']
page=3
</pre>

Configuration options are saved in the HistContext.ini found in the addon's subdirectory in the gramps/gramps{{Stable_branch}}/HistContext.ini file. Once the {{man menu|View -> Configuration}} is uses and saved, there will be <code>HistContext.ini</code> in the addon folder with the options:

<pre>
[myopt]
;;bg_sel_col='#ffffff'
;;bg_usel_col='#ededed'
;;fg_sel_col='#000000'
;;fg_usel_col='#000000'
;;files='custom_v1_0.txt'
;;filter_text='String in beginning of text'
;;hide_outside_span=1
;;use_filter=0
</pre>
{{-}}

=== Alternative Color Picker ===
Click on any color swatch in the Colors tab of the {{man menu|Edit -> Preferences}} to show the palette '''Pick a Color selector''' dialog. Then click the {{man button|+}} button in the Custom colors at the bottom to show the color picker. Copy the value to the ''Historical Context options''. Cancel the gradient Pick a Color dialogs.

See also:
* [[Gramps_{{man version}}_Wiki_Manual_-_Settings#Pick_a_Color_selector|Pick a Color selector]]
{{-}}

==See Also==
* GitHub
** [https://github.com/kajmikkelsen/ kajmikkelsen repository]
** [https://github.com/kajmikkelsen/HistContext HistContext]
* Discourse
** [https://gramps.discourse.group/t/my-first-gramplet-for-gramps-5-2/6348/45 My first gramplet - for gramps 5.2]
** [https://gramps.discourse.group/t/error-building-a-listing-for-a-new-gramplet/6330/11 error building a listing for a new gramplet]
** [https://gramps.discourse.group/t/add-option-for-boolean-options-in-gramplet/6371 add option for boolean options in gramplet]
** [https://gramps.discourse.group/t/translating-addons/6106 translating addons]
** Discourse tag: [https://gramps.discourse.group/tag/timeline timeline]
* MantisBT
** Feature Requests {{bug|13498}}: To be implemented in Historical Context gramplet

* [[Addon:House_Timeline_Gramplet|House Timeline]] - addon person gramplet
* [[Addon:Historical_Context|Historical Context]] - addon person gramplet
* [[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_4#Timeline_Chart|Timeline Chart]] builtin Report
* [[Addon:Timeline_Pedigree_Report|Timeline Pedigree Report]] - addon Web pages Report
* [[Addon:TimelinePedigreeView|Timeline Pedigree]] - addon Charts view mode
* [[Addon:TimeLinesMap|Timelines Map]] - addon Geography view mode
* [[Addon:Timeline_Quickview|Timeline]] - addon Quick view for Persons
* [[Addon:CombinedView#Timeline_tab|Timeline tab]] of the Combined view mode addon in Relationships category

[[Category:Addons]]
[[Category:Plugins]]

Talk:Gramps 5.2 Wiki Manual - Reports - part 7

2025-09-26T04:58:02Z

ErickLedger: Has an extra "the the" that I'm unable to remove!

Has an extra "the the" that I'm unable to remove!

Gramps 6.0 Wiki Manual - Reports - part 7

2025-09-26T04:57:22Z

ErickLedger: remove extra "the"

{{man index|Gramps 6.0 Wiki Manual - Reports - part 6|Gramps 6.0 Wiki Manual - Reports - part 8|6.0}}
{{languages|Gramps_6.0_Wiki_Manual_-_Reports - part 7}}
{{#vardefine:chapter|13.7}}
{{#vardefine:figure|0}}
Back to [[Gramps_6.0_Wiki_Manual_-_Reports|Index of Reports]].
<hr>
{{-}}
[[File:MenuOverview-Reports-WebPages-60.png|right|thumb|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} {{man menu|Reports >Web Pages>...}} Menu overview]]
This section describes the {{man label|Web Pages}} reports, [[Gramps_6.0_Wiki_Manual_-_Reports_-_part_7#Narrated_Web_Site|Narrated Web Site]] and [[Gramps_6.0_Wiki_Manual_-_Reports_-_part_7#Web_Calendar|Web Calendar]] as part of the different reports available in Gramps.
== Web Pages ==
===Narrated Web Site===

{{man tip|For this report to work requires that the optional prerequisite PyICU be installed|See:
* [[Gramps_6.0_Wiki_Manual_-_Reports_-_part_7#Prerequisites_for_Narrated_Web_Site|Prerequisites for Narrated Web Site]]}}
{{man warn|{{man menu|Do you really want to use the entire Family Tree database}}|Be aware that if you select the '''Entire Database''' filter option for your Family Tree database that a large number of files will be generated (depending on the size of your Family Tree database). It is recommended to start with a smaller filter (for example: ancestors of a certain person) to simplify the output while you learn about the Narrated Web Site Report.}}

[[File:NarratedWebSite-WebPages-Individuals-index-page-example-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Individuals (index) page - default HTML output - example]]

The {{man label|Narrated Web Site}} report generates a web site (that is, a set of linked web pages), for a set of selected individuals and provides the user with options that allow a wide range of customization. You can run this report via the menu {{man menu|Reports-->Web Pages-->Narrated Web Site...}}.

The Narrated Web Site report creates pages that closely follow the World Wide Web Consortium’s Recommendations for XHTML 1.0 Strict and CSS 1. These recommendations include a separation of content from presentation. Due to this practice, the style and appearance of the new web pages can be completely controlled from one CSS stylesheet without altering individual pages.

Introduction pages can be added to provide additional information, such as a family history.

Genealogy records can generate a lot of files. Many web servers have a difficult time with a large number of files in a single directory. The Narrated Web report attempts to keep the number of files per directory to a manageable level. To do this, a hierarchy of directories is created. The generated file names are not intuitive, but are unique for each person. Subsequent runs will generate identical file names, making it easy to update specific files.

{{man tip|1=Generating Pages...|2=When you select the {{man button|OK}} button, the generation of the web pages will start. So first check all options on the each of the [[Gramps_6.0_Wiki_Manual_-_Reports_-_part_7#Dialog_tabs|Dialog tabs]]}}
{{-}}
====Dialog tabs====

The {{man label|Narrated Web Site}} report dialog has the following tabs each are reviewed below.
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Report Options|Report Options]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#HTML_Options|HTML Options]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Display|Display]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Page Generation|Page Generation]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Extra_pages|Extra pages]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Images_Generation|Images Generation]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Download|Download]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Advanced Options|Advanced Options]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Include|Include]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Place Map Options|Place Map Options]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Other_inclusion_.28CMS.2C_web_calendar.2C_PHP.29|Other inclusion (CMS, web calendar, PHP)]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Translations|Translations]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Calendar_Options|Calendar Options]]
{{-}}
=====Report Options=====

[[File:NarratedWebSite-WebPages-ReportOptions-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Report Options - tab default options]]

* {{checkbox|0}} {{man label|Store web pages in .tar.gz archive}} (Checkbox unchecked by default) If you have trouble transferring the files to an external web host, you can create a single gzip'd tar file to more easily upload the data. The large number of files and directories in this web output may make it difficult to transfer the files to an external web host. Gramps has the capability of saving all of your Narrative Web files in one compressed archive using the gzip and tar formats (casually known as a ‘tarball’). This single file can quickly be transferred to your server and uncompressed on the website host. '''{{man menu|Unfortunately not all web servers support saving web files in this way, so contact your hosting provider for more information.}}'''
* {{man label|Destination:}} (<code>~/yourhomedirectory/<Family Tree Name>+NAVWEB</code> default) The destination directory for the web files.
* {{man label|Web site title:}} (<code>My Family Tree</code> default) The title of the web site. You can enter a custom site title in this option. {{man menu|Strongly suggested you change this from the default}}
* {{man label|Filter:}} (Any person matching this filter who is not excluded due to the privacy rules, will be included in the output.) choose between
** '''Entire Database''' (Default)
** Descendants of active person
** Descendant families of active person
** Ancestors of active person
** People with common ancestor with active person
* {{man label|Filter Person:}} The center person for the report. (defaults to Active person)
** {{checkbox|0}} {{man label|Show the relationship between the current person and the active person}} (Checkbox unchecked by default) - For each person page.

{{man warn|Please note that compliance with privacy laws and individuals' privacy concerns is '''''your''''' responsibility as the researcher.|The Gramps project cannot be held responsible for privacy law compliance or other privacy issues. Privacy of personal information is an important issue. Gramps provides tools and settings that give some control over the privacy of your data... but these controls were built to meet the regional considerations for that tool's programmer. You are responsible for verifying compliance before publication.}}

* {{man label|Living People}} How to handle living people. You can control the display of sensitive information based on whether or not an individual is currently alive. However, since Gramps is a research tool, it is likely that there are individuals with no known date of death in your database. To deduce if an individual is ''possibly still alive'' Gramps employs an algorithm that compares death dates, birth dates, baptism/christening dates, death dates of ancestors and birth dates of ancestors. The algorithm assumes that each individual is ''possibly still alive'' unless the cross-referenced dates make the individual’s ''possibility of being alive'' unlikely.
**'''Exclude''' – (Default) Excludes all information of all individuals who are ''[[Gramps_6.0_Wiki_Manual_-_Probably_Alive|possibly still alive]]''
**'''Include Last Name Only'''
**'''Include Full Name Only'''
**'''Include''' – Include all information of all individuals even if they are ''possibly still alive''
* {{man menu|Years from death to consider living:}} (<code>30</code> default) This option is inactive if the "Living People" option is set to '''Include'''. {{man warn|Privacy requirements can extend after Death. Laws vary regionally|Some countries have laws that specify a certain number of years after death before an individual's information can be published. Here you can comply with such laws by specifying the number of years after death to continue to apply Privacy redactions.}}
* {{checkbox|0}} {{man label|Include data marked private}}: Whether to include private objects. If your intention is to provide a complete record of your research, checking this box will include all entries marked '''private''' along with the rest of your database. (checkbox unchecked by default)

{{-}}

=====HTML Options=====

[[File:NarratedWebSite-WebPages-HTMLOptions-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - HTML Options - tab default options]]

* {{man label|File extension:}} The extension to be used for the web files.
** '''.html''' (Default)
** .htm
** .shtml
** .php
** .php3
** .cgi
* {{man label|Copyright:}} - When creating a public a web site it is important to specify the copyright conditions under which you are publishing your data. International copyright law reserves all rights of your data to your discretion. You own the data and individuals must have your permission if they wish to reuse that data. In genealogical research sharing data with other researchers is a common practice.
** '''Standard copyright''' (default)
** ''Creative Commons - By attribution''- A range of six Creative Commons licenses, offering various use restrictions or none at all. Learn more about the Creative Commons at https://creativecommons.org/
** ''Creative Commons - By attribution, No derivations''
** ''Creative Commons - By attribution, Share-alike''
** ''Creative Commons - By attribution, Non-Commercial''
** ''Creative Commons - By attribution, Non-Commercial, No derivations''
** ''Creative Commons - By attribution, Non-Commercial, Share-alike''
** ''No copyright notice''
{{-}}
[[File:NarratedWebSite-Stylesheet-examples-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} "HTML Options" tab - "StyleSheet" eight samples (shown top down order of list.)]]
* {{man label|StyleSheet:}} Gramps provides nine built in style sheets for you to choose from to determine the appearance or your web pages. Choose between these stylesheets:
** '''Basic-Ash''' (a 'Basic' color scheme) ( default)
** ''Basic-Blue'' (a 'Basic' color scheme)
** ''Basic-Cypress'' (a 'Basic' color scheme)
** ''Basic-Lilac'' (a 'Basic' color scheme)
** ''Basic-Peach'' (a 'Basic' color scheme)
** ''Basic-Spruce'' (a 'Basic' color scheme)
** ''Mainz'' -
** ''Nebraska''
** ''No style sheet'' (do not overwrite existing stylesheets)
** ''Visually Impaired''
:Regardless of the style you choose, the style sheet can be found in ''<code>css/narrative-screen.css</code>''. You may edit this file to further customize the appearance of your web pages. If you make modifications to your style sheet be aware that regenerating your pages with the same output destination will overwrite your custom style sheet.
:The option of not including a stylesheet ('''No style sheet''') it for users who have already created a custom style sheet when generating a previous Narrated Web Site report. To preserve your custom style sheet through subsequent web page updates select {{man label|No style sheet}}.
:If you want your own stylesheet, you can copy one of the existing stylesheet in ''<code>$HOME/.gramps/css/</code>''. If this directory doesn't exist. You must create it before copying your future stylesheet. Change its name. If you ask for a new report, this new stylesheet will be added to the list of pre-existing stylesheets.
* {{man label|Navigation Menu Layout:}} Choose which layout for the Navigation Menus. (Only available for selected Stylesheets)
** '''Horizontal -- Default'''
** Vertical -- Left Side
** Fade -- [https://en.wikipedia.org/wiki/WebKit Webkit] Browsers Only
** Drop-Down -- Webkit Browsers Only
* {{man label|Citation Referents Layout:}} Determine the default layout for the Source Page's Citation Referents section
** '''Normal Outline Style''' (Default)
** Drop-Down -- Webkit Browsers Only
* {{checkbox|1}} {{man label|Include ancestor's tree}}: Checking this box will include an ancestor graph on each individual’s detail page if they have defined ancestors in your database. (checkbox checked by default) ( Note: [[Narrated Website Ancestry Tree Design Notes]] discusses creating a compact Ancestry trees using the [[Narrated_Website_Ancestry_Tree_Design_Notes#buchheim|Buchheim]]/[[Narrated_Website_Ancestry_Tree_Design_Notes#walker|Walker]] algorithm.)
** You can change the number of generations shown from the {{man label|Display}} tabs ''[[Gramps_6.0_Wiki_Manual_-_Reports_-_part_7#Display|Graph generations:]]'' option.
* {{checkbox|0}} {{man label|Add previous/next}} (checkbox unchecked by default) - adds links to the navigation bar.
* {{checkbox|0}} {{man label|This is a secure site (HTTPS)}} (checkbox unchecked by default)
* {{checkbox|0}} {{man label|Toggle sections}} (checkbox unchecked by default) - Check if you want to open/close a section
{{-}}

=====Display=====

[[File:NarratedWebSite-WebPages-Display-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Display - tab default options]]

* {{man label|Name Format:}} Select the format to display the names. Choose from '''Surname, Given Suffix''' / Given Surname Suffix / Given / Main Surnames, Given Patronymic Suffix / SURNAME, Given (Common)
* {{checkbox|0}} {{man label|Do we use multiple translations?}} (checkbox unchecked by default) - Whether to display the narrative web in multiple languages. See the {{man label|[[Gramps_6.0_Wiki_Manual_-_Reports_-_part_7#Translations|Translation]]}} tab to add a new languages to the default one defined in the next field.
* {{man label|Translation:}} - The translation to be used for the report.
* {{man label|Date format:}} - The format and language for dates, with examples.
* {{man label|Gramps ID:}} - Option determines whether to hide or show the Gramps ID of objects in your web page output.
** '''Do not include''' (default)
** Include
* {{man label|Tags:}} - Whether to include tags
** '''Do not include''' (default)
** Include
* {{checkbox|0}} {{man label|Sort all children in birth order}}(checkbox unchecked by default) - Whether to display children in birth order or in entry order?
* {{checkbox|0}} {{man label|Do we display coordinates in the places list?}}(checkbox unchecked by default) - Whether to display latitude/longitude in the places list?
* {{checkbox|0}} {{man label|Sort places references either by date or by name}}(checkbox unchecked by default) - Sort the places references by date or by name. Not set means by date.
* {{man label|Graph generations}} :This option is inactive if the ''[[Gramps_6.0_Wiki_Manual_-_Reports_-_part_7#HTML_Options|Include ancestor's tree]]'' option on the ''HTML Options'' tab is not checked. The default number of generations shown in the ancestor graphs is <code>4</code> with options of 2, 3, 4 or 5. The individuals represented in the ancestor graphs are the same individuals whose information is provided elsewhere in your web pages.
* {{checkbox|1}} {{man label|Include narrative notes just after name, gender}}(checkbox checked by default) - Unchecked will show them just before attributes.
{{-}}

=====Page Generation=====

[[File:NarratedWebSite-WebPages-PageGeneration-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Page Generation - tab default options]]

The ''Page Generation'' tab provides options for creation of commonly expected supplemental webpages and annotations common to all webpages throughout the generated website.

The first options are used to control generation of three supplemental pages: '''Home''' ([https://en.wikipedia.org/wiki/Home_page Home] webpage), '''Introduction''' ([https://wikipedia.org/wiki/FAQ#In_web_design FAQ] or [https://www.searchenginejournal.com/about-us-page-examples/250967/amp/ About Us] webpage) and '''Publisher Contact''' ([https://wikipedia.org/wiki/Contact_page Contact Us] webpage).

Each of supplemental pages may be assigned a specific [[Gramps_Glossary#media|Media]] or [[Gramps_Glossary#note|Note]] item. By default, no content (neither media nor text from a Note) is assigned to these pages.

Content for these pages '''''must''''' originate as Media or Notes items that have been created before running the report. Once the desired items have been added to your Tree, you will be able to choose them from a list of Notes or Media Objects.

{{man note|Planning for sustainability|These special-purpose items do not need to have [[Gramps_Glossary#references|References]] associated with any other record in the Tree. However, you might find it helpful to [[Gramps_6.0_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#New_Source_dialog|add a Source]] your generated Website as a distinct Source ([[Gramps_6.0_Wiki_Manual_-_Getting_started#Privacy|marked as Private]]) to your Tree. This [[Gramps_Glossary#private_tag|private]] Source could use the [[Gramps_Glossary#references|References]] as a special-purpose item checklist... with an added Note to document the options used to generate the Narrated Website. Add another note documenting any idiosyncracies encountered when publishing the site. ''Such internal documentation makes reproducing the same appearance easier when generating website updates in the future.''}}

* {{man label|Home page note:}} Display an individual Note of your choice.
* {{man label|Home page image:}} Display an individual Media Object of your choice.
* {{man label|Introduction note:}} Display an individual Note of your choice.
* {{man label|Introduction image:}} Display an individual Media Object of your choice.
* {{man label|Publisher contact note:}} Display an individual Note of your choice.
* {{man label|Publisher contact image:}} Display an individual Media Object of your choice.
{{man warn|Privacy & Spam Exposure Risk |Please use the Publisher contact page with caution if you will be publishing your web pages on a publicly accessible web server. Consider using a single-use (disposable) eMailbox or secure form mail system.}}
* {{man label|HTML user header:}} Display an individual Note of your choice. This annotation text will appear directly below the site title on every web page.
* {{man label|HTML user footer:}} Display an individual Note of your choice. This annotation text will appear within the footer, above the copyright statement on every web page.
* {{man label|PHP user session:}} A note to use for starting the php session. This option will be available only if the .php file extension is selected.
{{-}}

=====Extra Pages=====

[[File:NarratedWebSite-WebPages-ExtraPages-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Extra Pages - tab default options]]

* {{man label|Extra page name:}} (blank) - Your extra page name like it is shown in the menubar.
* {{man label|Your extra page path:}} (blank) - Your extra page path without extension.
** {{man button|find folder}} button
{{-}}

=====Images Generation=====

[[File:NarratedWebSite-WebPages-ImageGeneration-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Image Generation - tab default options]]

* {{checkbox|1}} {{man label|Include images and media objects}} This option determines whether to include/exclude a gallery of media objects on your website. (checkbox checked by default)
* {{checkbox|0}} {{man label|Create the images index}} This option allows you to create the images index. (checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include unused images and media objects}} This option determines whether to include/exclude a gallery of unused media objects on your website. (checkbox unchecked by default)
* {{checkbox|0}} {{man label|Create and only use thumbnail- sized images}} : This option allows you to create only thumbnail images instead of full-sized images on the Media Page. This will allow you to have a much smaller total upload size to your web hosting site. (checkbox unchecked by default)
* {{checkbox|0}} {{man label|Create the thumbnail index}} : This option allows you to create the thumbnail index (checkbox unchecked by default)
* {{man label|Max width of initial image:}} (<code>800</code> default) This allows you to set the maximum width of the image (in pixels) shown on the media page.

* {{Man warn|Considerations for choosing image width|The width options need further expansion but discussions on the MailLists provide some added insight. See also: [https://sourceforge.net/p/gramps/mailman/message/22452425/ (Gramps-devel) NarrativeWeb and large images - Mk II] Some idiosyncratic browser support for images on iPad has been reported: [https://sourceforge.net/p/gramps/mailman/message/36888000/ (Gramps-users) Narrated website images don't appear on iPad [SOLVED]]
 If the image contains regions, the size will be resized to max_width. If the width of an image is less than max_width, no resizing will occurs.}}
{{-}}

[[File:NarrativeWeb-Media-tab-ImageReferenceRegions-example-50.png|right|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Example of
[[How_to_create_image_reference_regions|image reference regions]] - Media tab of HTML output for "Narrative Web" Report]]

Note that [[How_to_create_image_reference_regions|image reference regions]] are also displayed in the Narrative Web HTML pages created with Gramps. There are no special options necessary for this feature, other than the existence of reference regions for 1 or more images. Narrative Web displays reference regions for people and place objects only.
{{-}}

=====Download=====

[[File:NarratedWebSite-WebPages-Download-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Download - tab default options]]

* {{checkbox|0}} {{man label|Include download page}}: Whether to include a database download option. (checkbox unchecked by default)
* {{man label|How many downloads:}} (<code>2</code> default) The number of download files to include in the download page
* {{man label|Download Filename #1:}} Select the file to be used for downloading of database.
* {{man label|Description for download:}} (<code>Family Tree #1</code> default) Give a description for this file.
* {{man label|Download Filename #2:}} Select the file to be used for downloading of database.
* {{man label|Description for download:}}(<code>Family Tree #2</code> default) Give a description for this file.
* {{man label|Download Filename #3:}} Select the file to be used for downloading of database.
* {{man label|Description for download:}}(<code>Family Tree #3</code> default) Give a description for this file.
{{-}}

=====Advanced Options=====

[[File:NarratedWebSite-WebPages-AdvancedOptions-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Advanced Options - tab default options]]

These settings address the amount of information displayed on the Surname detail and Individual index web pages.

* {{man label|Character set encoding:}} The encoding to be used for the web files.
** '''Unicode UTF-8 (recommended)''' (Default)
** ISO-8859-1 ''- [https://wikipedia.org/wiki/ISO/IEC_8859 ISO/IEC character set standard:] Part 1 (Latin 1: Western European)''
** ISO-8859-2
** ISO-8859-3
** ISO-8859-4
** ISO-8859-5
** ISO-8859-6
** ISO-8859-7
** ISO-8859-8
** ISO-8859-9
** ISO-8859-10
** ISO-8859-13
** ISO-8859-14
** ISO-8859-15
** koi8_r ''- [https://wikipedia.org/wiki/KOI8-R Kod Obmena Informatsiey, 8 bit ("Code for Information Exchange - 8 bit")'']
* {{checkbox|0}} {{man label|Include link to active person on every page}}: (If they have a webpage) (checkbox unchecked by default)
* {{checkbox|1}} {{man label|Include a column for birth dates on the index pages}}(checkbox checked by default)
* {{checkbox|0}} {{man label|Include a column for death dates on the index pages}}(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include a column for partners on the index pages}}(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include a column for parents on the index pages}}(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include half and/ or step-siblings on the individual pages}}(checkbox unchecked by default)

{{-}}

=====Include=====

[[File:NarratedWebSite-WebPages-Include-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Include - tab default options]]

* {{checkbox|0}} {{man label|Include family pages}}(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include event pages}}(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include places pages}}(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include unused place pages}}(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include sources pages}}(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include repository pages}}(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include GENDEX file (/gendex.txt)}}. This option creates a GENDEX file placed at the top of the website. You can see sites which support this format and read more about it at the [http://en.wikipedia.org/wiki/GENDEX GENDEX Wikipedia article].(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include address book pages}}(checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include the statistics page}}(checkbox unchecked by default)
{{-}}

=====Place Map Options=====

[[File:NarratedWebSite-WebPages-PlaceMapOptions-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Place Map Options - tab default options]]

* {{man label|Map Service:}} Choose your choice of map service for creating the Place Map Pages
** '''OpenStreetMap''' (default)
** Stamen Map
** Google : For this option to work requires a {{man label|Google maps API key}} to be entered. To apply for one goto the Google maps platform ( https://cloud.google.com/maps-platform/ ) and select "Get Started" (top right corner) and follow the instructions (may involve a credit card) and then select the "Credentials" option on the "API Manager" menu . Then click on the "Create Credentials" button on the "Credentials" window. Click on "API Key "on the next pop-up window. Copy the generated API key to your clipboard and paste in to Gramps "Google maps API key:" field. I strongly suggest that after generating and placing your report online that you go back to the google maps platform and Click the "Restrict key" button on the API key created window and add your domain (this will stop other website hijacking your api key and making you pay! These new Google Maps API changes came into affect from the 11th of June 2018. see the pricing table https://cloud.google.com/maps-platform/pricing/sheet/ "You also get a recurring $200 credit on your billing account each month to offset your usage costs, and you can set usage limits to protect against unexpected cost increases"
* {{checkbox|0}} {{man label|Include Place map on Place Pages}}: Whether to include a place map on the Place Pages, where Latitude/ Longitude are available. (checkbox unchecked by default)
* {{checkbox|0}} {{man label|Include Family Map Pages with all places shown on the map}}: Whether or not to add an individual page map showing all the places on this page. This will allow you to see how your family traveled around the country. (checkbox unchecked by default)
* {{man label|Google/ FamilyMap Option:}} Select which option that you would like to have for the Google Maps Family map pages...
** '''Family Links''' (default)
** Drop
** Markers
* {{man label|Google maps API key:}} The API key used for the Google maps. This key is mandatory and must be valid
* {{man label|How to get the API key:}} https://developers.google.com/maps/documentation/javascript/get-api-key
{{man warn|To get a "Google maps API key:"|visit https://cloud.google.com/maps-platform/pricing/sheet/ as a cost may be involved as well as the use of a credit card}}
* {{man label|Stamen Options:}}
* {{man label|Stamen maps API key:}}
* {{man label|How to get the API key:}}
* {{man label|openlayers version to use:}}
* {{man label|Coordinates format:}}
{{-}}

=====Other inclusion (CMS, web calendar, PHP)=====

[[File:NarratedWebSite-WebPages-OtherInclusionCMSWebCalendarPHP-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Other inclusion (CMS, web calendar, PHP) - tab default options]]

* {{checkbox|0}} {{man label|Do we include these pages in a CMS web?}} (Checkbox unchecked by default)
** {{man label|URI:}} <code>/NAVWEB</code> (default) - Where do you place your website ?
* {{checkbox|1}} {{man label|Include the news and updates page?}} (Checkbox checked by default) Whether to include a page with the last updates
* {{man label|Max days for updates:}} <code>1</code> (default) - You want to see the last updates on how many days?
* {{man label|Max number of updates per object to show:}} <code>1</code> (default) - How many updates do you want to see max?
{{-}}
See also:
* [[Howto:_Make_a_genealogy_website_with_Gramps#Integration_of_NarrativeWeb_in_a_CMS_or_MVS]]
* Feature request {{bug|5530}} Integration of the Narrative Web Site into a CMS or MVC
{{-}}

=====Translations=====

[[File:NarratedWebSite-WebPages-Translations-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Translations - tab default options]]

On the Translation tab you can choose which languages to display the report in.

To use this section enable the {{man label|[x] Do we use multiple translations?}} language option on the {{man label|[[Gramps_6.0_Wiki_Manual_-_Reports_-_part_7#Display|Display]]}} tab and you can also choose the {{man label|Translation:}} language to display the narrative web report in if different from the default.

* {{man label|Second language:}} <code>''Default''</code> - Default language Gramps is using.
* {{man label|Site name for your second language:}} <code>''This site title''</code> - Change it to suit the language for this translation or use the default site title for the default language Gramps is using.
* {{man label|Third language:}} <code>''Default''</code> - Default language Gramps is using.
* {{man label|Site name for your third language:}} <code>''This site title''</code> - Change it to suit the language for this translation or use the default site title for the default language Gramps is using
* {{man label|Forth language:}} <code>''Default''</code> - Default language Gramps is using.
* {{man label|Site name for your fourth language:}} <code>''This site title''</code> - Change it to suit the language for this translation or use the default site title for the default language Gramps is using
* {{man label|Fifth language:}} <code>''Default''</code> - Default language Gramps is using.
* {{man label|Site name for your fifth language:}} <code>''This site title''</code> - Change it to suit the language for this translation or use the default site title for the default language Gramps is using
* {{man label|Sixth language:}} <code>''Default''</code> - Default language Gramps is using.
* {{man label|Site name for your sixth language:}} <code>''This site title''</code> - Change it to suit the language for this translation or use the default site title for the default language Gramps is using

See also:
* [https://github.com/gramps-project/gramps/pull/1051 Multiple languages for the narrative web and optional other additions #1051] added Nov 9, 2020
{{-}}

=====Calendar Options=====

[[File:NarratedWebSite-WebPages-CalendarOptions-tab-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Calendar Options - tab default options]]

* {{checkbox|0}} {{man label|Do we include the web calendar?}} (Checkbox unchecked by default)
* {{man label|First day of week:}} <code>Sunday</code>
* {{man label|Birthday surname:}} <code>Wives use their own surname</code>
* {{checkbox|0}} {{man label|Create on day event pages for Year At A Glance calendar}} (Checkbox unchecked by default)
* {{checkbox|1}} {{man label|Include birthdays}} (Checkbox checked by default)
* {{checkbox|1}} {{man label|Include anniversaries}} (Checkbox checked by default)
* {{checkbox|0}} {{man label|Include death dates}} (Checkbox unchecked by default)
* {{checkbox|1}} {{man label|Include only living people}} (Checkbox checked by default)
* {{man label|Show data only after year:}} <code>1914</code>

* [https://github.com/gramps-project/gramps/pull/1051 Multiple languages for the narrative web and optional other additions #1051] added Nov 9, 2020 "The web calendar doesn't work when multiple languages is in use and we link people to the narrative web. after multiple tries without succes, I integrate webcal in the narrative web. For each language, I use the related holidays calendar. (#07151)"
{{-}}

====Example Web Site output====

The following sections show the default appearance of web pages the Narrative Website web page report with optional pages enabled. (Using the [[example.gramps]] family tree.)

{{-}}
=====Home=====
(optional page)
{{stub}}
{{-}}
=====Introduction=====
(optional page)
{{stub}}
{{-}}
=====Individuals=====
Individuals (index) (default page) Filename: <code>individuals.html</code>
[[File:NarratedWebSite-WebPages-Individuals-index-page-example-52.png|right|450px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Narrated Web Site - Web Pages - Individuals (index) page - default HTML output - example]]

{{stub}}
{{-}}

=====Surnames=====
Surnames (index) (default page) Filename: <code>index.html</code>
{{stub}}
======Surnames count======
Surnames (count index - sorted by "Number of People" column) (default page) Filename: <code>surnames_count.html</code>
{{-}}
{{stub}}
=====Families=====
(optional page)
{{-}}
{{stub}}
=====Events=====
(optional page)
{{-}}
{{stub}}
=====Places=====
Places (index) (default page) Filename: <code>places.html</code>
{{-}}
{{stub}}
=====Sources=====
Sources (index) (default page) Filename: <code>sources.html</code>
{{-}}
{{stub}}
=====Repositories=====
(optional page)
{{-}}
{{stub}}
=====Media=====
(default page)
{{-}}
{{stub}}
=====Thumbnails=====
(default page)
{{-}}
{{stub}}
=====Download=====
(optional page)
{{-}}
{{stub}}
=====Address Book=====
(optional page)
{{-}}
{{stub}}
=====Contact=====
(optional page)
{{-}}
{{stub}}
=====Updates=====
Updates (default page) Filename: <code>updates.html</code>
{{-}}
{{stub}}

===='''HTML Code type Notes'''====

{{man tip|''In this subsection, the word '''tag''' does not refer to Gramps marker tags|but instead refer to HTML formatting tags!''}}

Gramps [[Gramps_6.0_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Editing_information_about_notes|'''Notes''']] set to the '''HTML Code''' [[Gramps_6.0_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#note_type|type]] will be inserted under the object to which they are attached. This allows special ''HTML chunks'' to be included in the report.

The HTML chunks must be well-formed, with all tags properly closed, to avoid conflicts with the rest of the webpage generated by the report. Only insert tags in a '''HTML Code'''-type Note that would normally be contained within the body of a HTML document.

The following tags will always be ignored:
<code>html</code>, <code>meta</code>, <code>doctype</code>, <code>head</code>, <code>meta</code>, <code>title</code>, <code>link</code>, <code>script</code>, <code>body</code>

All other tags will be available :
<code>i</code>, <code>a</code>, <code>p</code>, <code>ol</code>, <code>ul</code>, <code>div</code>, <code>h1</code>-<code>h7</code>, <code>button</code>, <code>svg</code>, <code>table</code>, <code>tr</code>, <code>td</code>, …
{{-}}

====Prerequisites for Narrated Web Site====
For Gramps 6.0.x, you need to install Pyicu and the associated packages.

See also:
* {{bug|13407}} Navweb will not load ( Name localAlphabeticindex is not defined ) [If optional prerequiste PyICU not installed ]

=====Possible problems=====
*If the report shows "Failed Loading Plugin" name 'localAlphabeticIndex' is not defined : do you have the prerequisite <code>pyicu</code> installed ?
** Run ''<code>gramps -v</code>'' from the command line to see if any additional information that may help you is shown.
*Other errors: [[Using_the_bug_tracker|Report a bug]]

===Web Calendar===
{{man note|The Narrated Web Site Report does not hyperlink back into the Web Calendar Report.}}

[[File:WebCalendar-WebPages-example-DecemberCalendar2018-50.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Web Calendar Report - Web Pages - default Calendar for December 2018 - HTML output]]

The {{man label|Web Calendar}} shows events for the selected individuals on a set of monthly calendars. You can run this report via the menu {{man menu|Reports > Web Pages > Web Calendar...}}.

There are options to filter the individuals, to choose which years to include (by default, only the current year is included); whether to include only living people and whether to include birthdays or anniversaries or both; notes can be included on monthly pages and abbreviated pages can be included.

The report is designed to work with the [[Gramps_6.0_Wiki_Manual_-_Reports_-_part_7#Narrated_Web_Site |Narrative Web Site Report]]. If selected there is a 'Home' link on each page to the home page of the Narrative Web Site Report. There is also an option to include links from the individuals on the calendar to the same individual on the Narrated Web Site.

Working with the Narrated Web Site Report requires that the two reports have been constructed in a compatible way by the user. There is no automated check that the two are compatible. If the pages are not compatible, then the user will likely get a '[https://en.wikipedia.org/wiki/HTTP_404 Page not found]' error.

Compatibility depends on:

# Including the same individuals in the two reports,
# Storing the pages in compatible directories.

In order to include the same individuals in the two reports, the same filters should be used, and similar options with regard to including living individuals (the Web Calendar does not have an option to remove 'private' information).

By default, the Narrated Web Site Report is stored in the directory "<code>~/<Family Tree Name>+NAVWEB</code>", and by default the Web Calendar is stored in the directory "<code>~/<Family Tree Name>+WEBCAL</code>". If these defaults are retained, then the various links should work properly. If the directories have been changed, then the 'Home link' under the 'Content Options' and the 'Link prefix' under the 'Advanced Options' will need to be changed accordingly.

If the Web Calendar is to be used without an associated Narrative Web Site, then uncheck the {{man label|Link to Narrated Web Report}} option on the {{man label|Advanced Options}} tab this will ensure that no 'Home' link is generated.

====Dialog tabs====

The Web Calendar report dialog window {{man label|Web Calendar}} has the following tabs each are reviewed below.
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Report_Options_2|Report Options]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Report_Options_.282.29|Report Options (2)]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Content Options|Content Options]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Advanced_Options_2|Advanced Options]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Jan - Jun Notes|Jan - Jun Notes]]
*[[Gramps 6.0 Wiki Manual - Reports_-_part_7#Jul - Dec Notes|Jul - Dec Notes]]
{{-}}
=====Report Options=====

[[File:WebCalendar-WebPages-ReportOptions-tab-52.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Web Calendar - Web Pages - Report Options - tab default options]]

* {{man label|Destination:}} <code>~/yourhomedirectory/<Family Tree Name>+WEBCAL</code> The destination directory for the web files.
** {{man button|find folder}} button
* {{man label|Calendar Title:}} (<code>My Family Calendar</code> default) The title of the calendar.
* {{man label|Filter:}} choose between
** '''Entire Database''' (Default)
** Descendants of active person
** Descendant families of active person
** Ancestors of active person
** People with common ancestor with active person
* {{man label|Filter Person:}} The center person for the filter. (Default: Active person)
* {{man label|File extension:}} The extension to be used for the web files.
** '''.html''' (Default)
** .htm
** .shtml
** .php
** .php3
** .cgi
* {{man label|Copyright:}} The copyright to be used for the web files.
** '''Standard copyright''' (Default)
** ''Creative Commons - By attribution'' - A range of six Creative Commons licenses, offering various use restrictions or none at all. Learn more about the Creative Commons at https://creativecommons.org/
** ''Creative Commons - By attribution, No derivations''
** ''Creative Commons - By attribution, Share-alike''
** ''Creative Commons - By attribution, Non-Commercial''
** ''Creative Commons - By attribution, Non-Commercial, No derivations''
** ''Creative Commons - By attribution, Non-Commercial, Share-alike''
** ''No copyright notice''
* {{man label|StyleSheet:}} The stylesheet to be used for the web pages.
** '''Basic-Ash''' (a 'Basic' color scheme) ( default)
** ''Basic-Blue'' (a 'Basic' color scheme)
** ''Basic-Cypress'' (a 'Basic' color scheme)
** ''Basic-Lilac'' (a 'Basic' color scheme)
** ''Basic-Peach'' (a 'Basic' color scheme)
** ''Basic-Spruce'' (a 'Basic' color scheme)
** ''Mainz'' -
** ''Nebraska''
** ''No style sheet'' (do not overwrite existing stylesheets)
** ''Visually Impaired''
{{-}}

=====Report Options (2)=====

[[File:WebCalendar-WebPages-ReportOptions2-tab-52.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Web Calendar - Web Pages - Report Options (2) - tab default options]]

* {{man label|Name Format:}} - Select the format to display the names. This choice in normally taken from the default setting in [[Gramps_6.0_Wiki_Manual_-_Settings#Display_Options|{{man menu|Edit > Display Options}}]] tab for {{man label|Name format:}}. Or to override that setting for the report choose from:
** ''Surname, Given Suffix'' (Default in a new Family Tree )
** Given Surname Suffix
** Given
** Main Surnames, Given Patronymic Suffix
** SURNAME, Given (Common)
* {{checkbox|0}} {{man label|Include data marked private}} (checkbox unchecked by default)
* {{checkbox|1}} {{man label|Include only living people}} (checkbox checked by default) - eliminates ancestors for webcalendars being used as reminder tools instead of historical tools.
* {{man label|Translation:}} The translation to be used for the report. Language selector showing all languages supported by Gramps. Defaults to the language you are using Gramps in.
* {{man label|Date format:}} The format and language for dates, with examples
** Default - Choose this option to use the default set in {{man menu|[[Gramps_6.0_Wiki_Manual_-_Settings#Display_Options|Edit > Display Options]]}} tab for {{man label|Date format *:}} option.
** '''YYYY-MM-DD(ISO)(2018-03-14)''' (default for report)
** Numerical(14/3/2018)
** Month Day, Year(March 14, 2018)
** MON DAY, YEAR(Mar 14, 2018)
** Day Month Year(14 March 2018)
** DAY MON YEAR(14 Mar 2018)
{{-}}

=====Content Options=====

[[File:WebCalendar-WebPages-ContentOptions-tab-52.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Web Calendar - Web Pages - Content Options - tab default options]]

* {{checkbox|0}} {{man label|Create multiple year calendars}} (checkbox unchecked by default) Whether to create Multiple year calendars or not.
** {{man label|Start Year for the Calendar(s):}} (Defaults to current year)
** {{man label|End Year for the Calendars(s):}} (Defaults to current year)
* {{man label|Country for holidays:}} Select the country to see associated holidays. (Defaults to blank)
* {{man label|First day of week:}} Select the first day of the week for the calendar. (Default: '''Sunday''')
* {{man label|Birthday surname:}} Select married women's displayed surname.
** '''Wives use their own surname''' (Default)
** Wives use husband's surname (from first family listed)
** Wives use husband's surname (from last family listed)
{{-}}

=====Advanced Options=====

[[File:WebCalendar-WebPages-AdvancedOptions-tab-52.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Web Calendar - Web Pages - Advanced Options - tab default options]]

* {{man label|Character set encoding:}} The encoding to be used for the web files
** '''Unicode UTF-8 (recommended)''' (Default)
** ISO-8859-1
** ISO-8859-2
** ISO-8859-3
** ISO-8859-4
** ISO-8859-5
** ISO-8859-6
** ISO-8859-7
** ISO-8859-8
** ISO-8859-9
** ISO-8859-10
** ISO-8859-13
** ISO-8859-14
** ISO-8859-15
** koi8_r
* {{checkbox|0}} {{man label|Create one day event pages for Year At A Glance Calendar}} (checkbox unchecked by default)
* {{checkbox|1}} {{man label|Include birthdays}} (checkbox checked by default)
* {{checkbox|1}} {{man label|Include anniversaries}} (checkbox checked by default)
* {{checkbox|0}} {{man label|Include death dates}} (checkbox unchecked by default)
* {{checkbox|0}} {{man label|Link to Narrated Web Report}} (checkbox unchecked by default)
** {{man label|Show data only after year:}} (<code>1914</code> default) Show data only after this year. Default is current year - 'maximum age probably alive' which is defined in the dates preferences tabs.
** {{man label|Link prefix:}} '''<code>../../Family Tree 1_NAVWEB/</code>''' A Prefix on the links to take you to Narrated Web Report.
{{-}}

=====Jan - Jun Notes=====

[[File:WebCalendar-WebPages-Jan-JunNotes-tab-52.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Web Calendar - Web Pages - Jan-Jun Notes - tab default options]]

Use the {{man button|Select an existing note}} buttons to choose the note from the {{man label|Select Note}} selector for each of the months if needed:
* {{man label|January Note:}}
* {{man label|February Note:}}
* {{man label|March Note:}}
* {{man label|April Note:}}
* {{man label|May Note:}}
* {{man label|June Note:}}
{{-}}

=====Jul - Dec Notes=====

[[File:WebCalendar-WebPages-Jul-DecNotes-tab-52.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Web Calendar - Web Pages - Jul-Dec Notes - tab default options]]

Use the {{man button|Select an existing note}} buttons to choose the note from the {{man label|Select Note}} selector for each of the months if needed:
* {{man label|July Note:}}
* {{man label|August Note:}}
* {{man label|September Note:}}
* {{man label|October Note:}}
* {{man label|November Note:}}
* {{man label|December Note:}}
{{-}}

====Example Web Site output====
[[File:WebCalendar-WebPages-example-DecemberCalendar2018-50.png|thumb|right|450px|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Web Calendar Report - Web Pages - default Calendar for December 2018 - HTML output]]

{{-}}

===See Also===
* [[Web Solutions for Gramps]]
<hr>
Back to [[Gramps 6.0 Wiki Manual - Reports|Index of Reports]].
{{man index|Gramps 6.0 Wiki Manual - Reports - part 6|Gramps 6.0 Wiki Manual - Reports - part 8|6.0}}
{{languages|Gramps 6.0 Wiki Manual - Reports - part 7}}
{{grampsmanualcopyright}}

[[Category:Documentation]]
[[Category:Plugins]]

Translating the Gramps User manual

2025-09-26T04:56:49Z

ErickLedger: remove extra "the"

{{languages|Translating the Gramps User manual}}

{{man note|The user manual|is also available from within Gramps using the {{man key press|F1}} key (which opens this manual in a browser window), or from the help menu.}}
An explanation of how you can translate the [[User manual|Gramps User manual]].

==Getting started==

Translating Gramps' documentation into a new language is a worthwhile process and the Gramps team thanks you.

Documentation was moved completely to this wiki starting with Gramps version 3.0. So for translation you donot need to use or even install any fancy applications to help us. You can use your browser and start immediately. Just go to the [[User manual]] page, select the current manual and then click on your language. You should could keep the English manual open to check if there is a help page missing.

The general [[Help:Contents|wiki help page]] will help you with editing wiki pages. This wiki uses the [https://www.mediawiki.org/ MediaWiki] software, which is the same that is used by [https://wikipedia.org/wiki/Wikipedia Wikipedia], so it could feel familiar.

==Translating==

===Recommendations===
We recommend that before updating any of the user manuals:

* You have identified what your Languages two letter code is.
* You are familiar with Mediawiki [https://www.mediawiki.org/wiki/Wikitext wikitext/wiki markup/wiki code] and templates and have practiced editing on Wikipedia for a little while at least.

====Where to begin...?====

=====Practice=====
Let's practice by creating and translating a version of this page to learn what needs to be done for the user manual.

Start by initially creating a new page in your language for the translation:
* Start with the English version of the page name and add add a fowardslash <code>/</code> and then your Languages two letter lowercased code <code>xx</code> to end of the URL '''<code>/xx</code>''' eg:
<nowiki>https://gramps-project.org/wiki/index.php/Translating_the_Gramps_User_manual</nowiki>
becomes
<nowiki>https://gramps-project.org/wiki/index.php/Translating_the_Gramps_User_manual</nowiki>'''/de'''
Then press {{man button|Enter}} and wiki will show the following message:
<hr>
'''There is currently no text in this page. You can search for this page title in other pages, search the related logs, or create this page. '''
<hr>
Select the last link '''create this page.''' in the message for the page editor to open a blank page ready for the initial text.
* where you can then copy the contents of this English page by using the "edit" button at the top wiki page to access the raw wiki contents.

{{stub}}

=====Prepare the templates=====
Using what you learned above create translated versions of the first three [[#Important_re-usable_Templates|User manual templates]] - as they will used on each of the user manual pages.

Then on your languages version this page that you previously created update the Languages Template to your languages version.

=====Start with the User manual index=====
Let's begin with the user manuals index page.

Follow the steps you practiced above
* Start with the English version of the page name and add your Language code.
* Copy the contents raw contents of the English version wiki page to your Languages page.
* Change the pages English templates to use your language code
* Translate the contents of the page.

=====Continue with the rest of User manual=====
Repeat this for the rest of user manual pages.

Optional final steps
* Create screenshots in your Language ....
* Use the wiki pages '''move''' option at top of the page to rename and move your English Languages version of the page name to your language as then it will leave behind a redirection from the English page that is used by the Gramps programs Help function (as the builtin in help only adds the two letter Language code to the English version of the page name)
* links for non English user manuals don't always work because of translated title and redirection! use <code><nowiki></nowiki></code> wrapped around the relevant section title. eg:
* Request that Links to wiki manual in the Gramps program be Enabled for your Language. F1 & help menu.

{{stub}}




=====Important re-usable Templates=====
Translate the following re-usable templates/Annotations used in the user manual and few used in general on the wiki:

* User manual templates:
** [[Template:Languages|label for the Languages bar]]
** [[Template:Man index|Produces the index page in the user manual]]
** [[Template:Grampsmanualcopyright|Copyright template]]

* Important templates used in general on the wiki:
** [[Template:Third-party_addon|Third-party addon notice]] and the associated [[Third-party Addons]] page.
** [[Template:Stub|Stub template]]


* Beyond the user manual
** [[Gramps:Using_Gramps_templates|the 8 subsections of the Using Gramps portal]]


====Tools and Configuration====
[[File:WeblateSearch.png|353px|thumb|right|[https://hosted.weblate.org/projects/gramps-project/gramps/#search Weblate Search form]]]
* Use Gramps localized in that language as a reference and do not simply guess the words. Verify your translated text actually matches what the user will see in the standard localized Gramps installation. You can [https://hosted.weblate.org/projects/gramps-project/gramps/#search search the Weblate translations]. (i.e., searching for the phrase <code>source:"Relationship Information" AND language:fr</code> finds French translation: "Information sur la relation". Clicking that translation says that that phrase was found that phrase in the <code>editfamily</code> code and lists the other nearby translated text. This includes Tips as well as labels.)
* If the localized interface has a typo or incorrect translation, document the '''''EXISTING''''' interface. Do not mislead the user into expecting something else. They might waste time searching for an non-existent update.
* Do not have any third party addons loaded. Use a vanilla version of Gramps unless documenting that particular addon.
* Also, preferably use a fresh copy of the [[Example.gramps]] family tree for any screenshots in your preferred language.

===Handling of Translations Errors===
Translation errors, typos and revisions are inevitable.

It is important that documentation describe software as it currently exists... not as it ''should be'' in a perfect world.

That acknowledgment of a localization problem in the wiki doesn't mean that the problem cannot or will not be fixed. Rather than patch the problem in documentation, file a translation bug report, see [[How to report bugs]]. A good bug report will also include a link to the wiki page that will need to be revised. The wiki page link gives the developer a second viewpoint of the nature of the problem. This helps if the bug report accidentally omits key information.

There is no requirement to pretend a problem doesn't exist while waiting for a fix. It is reasonable to annotate that the translation has the problem in the wiki without misleading the user into expecting something else.

You can make this annotation easier to eliminate after the bug fix. An English version Warning box like below can be inserted with the wiki code snippet that follows it. You might notice that the snippet has a chunk commented out:
<pre></pre>
By moving the comment markers, you can re-cycle this same warning and easily update to inform that a Bug has been filed and when a correction was released. When the manual is rolled over for the corrected release, you can update the main text and any affected screenshots before removing the warning entirely.
{{man warn|1=[https://omniglot.com/language/phrases/hovercraft.htm My hovercraft is full of eels]|2=An unfortunate translation in the Gramps 4.1.0 interface is documented above. A "localization" Gramps bug report {{bug|7854}} has been filed... so any corrections ''(version 4.1.1)'' might make this warning obsolete.

{{WikiContributorRecruiting}} Or join [[Portal:Translators|our volunteers]] translating the interface.
}}
<pre>{{man warn|1=[https://omniglot.com/language/phrases/hovercraft.htm My hovercraft is full of eels]|2=An unfortunate translation in the Gramps 4.1.0 interface is documented above. A "localization" Gramps bug report {{bug|7854}} has been filed... so any corrections ''(version 4.1.1)'' might make this warning obsolete.

{{WikiContributorRecruiting}} Or join [[Portal:Translators|our volunteers]] translating the interface.
}}</pre>

===Screenshots===
Localized screenshots (aka: figures ) are useful for the localized manual.

====Create the screenshots====
If you can provide screenshots that would be great as fortunately, one does not have to speak the language to make screenshots :-)

If you need help, ask on the Gramps forum and somebody will help you.

Use the following file naming convention/scheme:
* '''{<code>filename</code>}-{<code>gramps version number</code>}-{<code>locale</code>}.png''' eg: <code>Mainwin-{{Stable branch}}-fr.png</code>
** Where <code>filename</code> is always exactly the English filename
** <code>gramps version number</code> - Is the current two digit release number eg: Currently version {{Stable branch}}
** <code>locale</code> is your two letter language code. Use the [https://wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements Language code table] on Wikipedia, the free encyclopedia.
** <code>.png</code> - always use this file type to save the images as.
* If the screenshot/figure is language independent (such as an unlabeled icon) then just call it <code>figure_name-{{Stable branch}}.png</code>.

;Screenshot advice:You can use the Linux tool called imagemagick for taking Gramps screenshots for this wiki. (imagemagick should be installed with every Linux distribution. If not with your installation, get it!) Invoke the preferred command options by using : <pre>import -quality 100 -trim -delay 200 -resize 500 -density 100x100 -frame -channel RGB -depth 8 screenshot.png </pre>This creates a fully compressed (<code>-quality 100</code>), timed screenshot after 2 seconds (<code>-delay 200</code>) of size 500 pixels wide (<code>-resize 500</code>), with resolution 100 (<code>-density 100x100</code>), with the window frame attached (<code>-frame</code>) in RGB mode (<code>-channel RGB</code>) and bbp 24 (<code>-depth 8</code>). This creates images of 5 inches wide, which fit nicely on a book page, as well as on a HTML page.

Also see:
* [[Screenshots]] - gallery of available references for screenshots in different languages and past versions.

====Upload the screenshots====
You can learn to upload files to this wiki by following the advice on:
* [https://www.mediawiki.org/wiki/Help:Managing_files Help:Managing files] '''Upload a file''' section - on the Mediawiki website

Make sure to complete the "Summary" before uploading the file to wiki.

==Links to wiki manual==

Your recently translated manual can be made available from within Gramps. When the localized wiki pages pages appear from clicking the {{man button|Help}} button in Gramps dialogs or pressing the {{Man key press|F1}} key, the manual is considered [[User_manual#Enabled|enabled]] or activated.

You activate the manual by editing the following file: '''[https://github.com/gramps-project/gramps/blob/master/gramps/gui/display.py gramps/gui/display.py]''' to contain your language code, you may also contact the developers of Gramps by opening a ''Feature request'' for the new language on the [[Using_the_bug_tracker |Bug tracker]].

In that file, you see:

<pre>
MANUALS = {
'nl' : '/nl',
}
</pre>

This maps a language code to the extension used on the wiki, so to add french, change this to:

<pre>
MANUALS = {
'nl' : '/nl',
'fr' : '/fr',
}
</pre>

*Every '<code>manual|...</code>' entry in the gramp.pot file refers to a section in the manual, so make sure to use good section headings so this does not change too much over time.

Note that reports/tools link to a section in the page with the same name as the report name in Gramps.

*You should be able to edit directly on wiki or using tools like [https://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/txt2po.html#mediawiki txt2po] and [https://weblate.org/ Weblate].

Also previous gettext file for the manual and [https://wikipedia.org/wiki/Translation_memory Translation Memory] may help you to upgrade deprecated/old gettext files.

==Possible improvement==

A project like [https://www.gnucash.org/ GnuCash] provides a complete web site environment by using gettext files, see [https://github.com/Gnucash/gnucash/blob/master/README README file] and current [https://github.com/Gnucash/gnucash environment].

[[Category:Translators/Categories]]
[[Category:Developers/General]]
[[Category:WikiContributors|Translators/enabled manual]]

Descendant B Report

2025-09-26T04:56:38Z

ErickLedger: remove extra "the"

{{Third-party addon}}
{{man warn|No longer available|Merged into Gramps 3.1+ as the [[Gramps_5.1_Wiki_Manual_-_Reports_-_part_4#Descendant_Tree|Graphical Descendant_Tree Report]]}}

[[Image:descend-_chart.jpg|thumb|500px|Sample Descend chart]]
A double graphical descendant report showing (when given a center family):
*This report was run off of the example data within Gramps.
**Report for: Smith: Gustaf, Sr (I07)
**Filter for: Smith: Gustaf, Sr (I07) and Hansdotter, Anna (F06)
**Start with the parent(s) of the selected first
*The best way to understand this report is with the picture. But here is a description:
# This is a descendant report. But you can think of two descendant reports with a combined (center) family
##Arrows point to the center family's father Gustaf (on top) and mother Anna (below).
# Mom's family is unknown at this time
##This report shows that Gustaf and Anna's son, Hans has been married twice.

== Starting the report ==
Once [[#Download_.2F_Install|installed]], You will find the plugin under 'Reports -> Graphical Report -> Descend] Tree'

== Paper Options ==
The standard 'Paper Options' apply.

=== Style ===
For this report there is one more style option; Title. The report title can be sized individually and defaults to seven sizes larger than the standard font size. If there are lots of children under the center family, you may need to make a new style with a smaller font size so the report title isn't too long.

== Report ==
You can define the basic style of the report here.

[[Image:Report Tab.jpg|Report Tab]]

;Report for
:You can select the main person for the report.
;Filter for
:Here you can tell the report to run off of a family instead of an individual.
;Start with the parent(s) of the selected first
:Instead of starting with the selected individual or family, start with their parents.
:note that this will show brothers and sisters of the selected person or parents of the family.
;Generations
:the parents of mom and dad (grandparents) will always be shown
:1 - Show the parents and siblings of the grandparents only (aunts and uncles)
:2 - (default) Show children of the above. Cousins will be shown with this option
:3 - Children of the above (Grandchildren of the parents)
:etc
;Level of spouses
:0 - Do not show any spouses of direct children
:1 - show spouses of the above
:2 - show spouses of the above (spouses of spouses)
:etc

<HR>

There are four basic reports that can be run: Numbers on the report correspond to the numbers listed below. 
[[Image:Descend_All.jpg|All four report types|500px]] 

{|style="background-color:lightgrey"
! colspan="2" align="left"|without the 'Start with the parent(s) of the selected first' option
|-
! |1.
|Given a person, this report will display a descendant report for that person
|-
! |2.
|Given a center family, This report will display a descendant report for that family
|-
! colspan="2" align="left"|with the 'Start with the parent(s) of the selected first' option
|-
! |3.
|Given a person, you will print a descendant report of the selected persons parents
|-
|
|Of course this will print all brothers and sisters of the selected person (2 in the example).
|-
! |4.
|Given a center family, you can choose to start with the parents of the selected family parents
|-
|
|the top half of the report will show a descendant report of the fathers parents.
|-
|
|The bottom half will show a descendant report of the mothers parents (unknown in this example).
|-
|
|The center family will be the junction of the two descendant reports.
|}


== Personal ==

[[Image:Personal Tab.jpg|Personal Tab]]

;Personal Display Format
:How direct descendants (not spouses) will be displayed.
;Bold direct descendants
:Whether direct descendants of the individual or family or parents of parents (grandparents) will be bolded.
:This does not include half or step children
;Compress Personal ans Spousal Display Formats
:If a line is blank because the information is not available, do not print that line.
:this also works for the Spousal Display Format (below)
:example, if a line show 'd. $d $D', this line will not be printed if the person is still alive or no information is given for death.

== Spouse ==
;Use seperate display format for spouses
:If you wish for the spouses to have a different display, (ie, add marriage information), do this here.
;Spousal Display Format
:How spouses will be displayed.
;Indent Spouses
:if selected, spouses will be indented a little from their spouses. Spouses of Spouses will be indented a little bit further, etc.

== Marriage ==
;Include Marriage information
:If you wish for marriage infomation to be displayed in a seperate box, do this here.
;Marriage Display Format
:like the Personal Display Format, how do you wish to format Marriage information for the parents of a family.

== Replace ==
make a line for each replacements that you wish to make like
replace this/with this
This is useful for very long entries. An example birth place would be 'room 2, maternity ward, some hospital, this county, that state, United States of America'
Also abbreviating countries and other things helps, cut down the width of a report. This is very useful so scaling the report and excessive white space can be cut down.

== Print ==
;Scale report to fit
:Do not scale report. This option works great with the 'One Page Report' option.
:Scale report to fit page width only. This option works great for Kinko's 36" wide roll printer (also select the 'One Page Report' option). Also use this option to make 1Xn page reports.
:Scale report to fit the size of the page. With this option the 'One Page Report' option is useles.
;One page report
:Scale up or down the size of the page (whether verticaly or both vertically and horizontally) to fit the natural size of the report. Note that this WILL most likely make irregular page sizes. Great for Emailing to relatives and Kinkos can size to print too.
;Include Report Title
:Will display the names of the uppermost parents.
:Grandparents will be displayed if known/shown. Otherwise the parents will be printed.
;Print a border
:Prints a border around the report if wanted.
;Print Page Numbers
:Page numbers will be printed on the lower right hand corner of the report.
;Include Blank Pages
:on multiple page reports, if nothing is on a page, specify to print the page anyway.
;Compress Tree
:With this option, the tree will NOT be expanded as much as normal. Giving a little bit smaller (in length) report.

== Notes ==
Now we are able to add a personalized note to the report. Yeah.

== Advanced thoughts ==
;Know the page size you want to print to first.
:This is actually very important. There are lots of different things you can do.
:If you are printing at home you know what you can print on. If you are printing somewhere else (I use Kinkos a bit), know what they can print on (and how much). example, my Kinkos has a 36 inch wide printer. The paper is on a roll so height is not an issue. So if the report is too long, use the replace option to get it down. then use the scale to width and one page option.
:Also don't rule out Landscape. I've made quite a few legal paper reports that were landscape, and fitted to width. Makes an easy report to put together, either taped or bound one page after the other.
;Make a new style
:A new style will allow you to play with the report title. Changing the font size will change the width and height. No duh. But if there are LOTS of kids the title can be much wider than the report and that creates a problem. In this case you can scale down the title font size to make the two widths match up better. Also if there is only one or two children, you may want a larger title (if you have the height to do so)

;Generations / Indent Spouses / Replace
:This is more than likely the width of your report. Using replace option correctly can give a better report and maybe room to get in another generation

;Marriage info Vs. Seperate Spousal Display
:If you like the Marriage display box, but your report is still too long, think about moving that infomration into the Spousal Display.

;Compress Personal Display
:Do you want every line printed all of the time so people can write on it? Or remove blank lines to really shrink up the height of a report.

;Replace text
:The size of all of the columns is set to the longest line. Really it is the widest as length does not stipulate width (the letter 'i' is much shorter than the letter 'W"). So changing/abbreviating the widest line will shrink ALL of the columns.

;Scale report to fit page width only
:When using this option, first check the natural size of the report (one page report with no scaling). If the width of the report is wider than the page width, look into using the replace option first. This will get the natural report width closer to the width of the page that you want to print on, and as such, the font size used will not decrease as much. Thus the readability will increase.

== Download / Install ==
You can download Version 1.0 of this software for Gramps 3.0.x: You find it [http://ander882.110mb.com/files/Descend.zip here]

There is NOT a working version for Gramps 2.2.5+. If you modify this report to work here, plese let me know.

Open the file in whatever zip archival program that you use (sorry, my website does not allow the .py extension). There will be ONLY one file in this zip called 'Descend].py' and save it into:

linux: local install: place in ~/.gramps/plugins

!AND! restart GRAMPS (alternatively you can reload all plugins by selecting 'Tools > Debug > Reload Plugins').

== New future features ==
I have asked for comments, criticism, and the kitchen sink. Well everyone has thrown it at me... :)
I am going to move this section into a [[Graphical Descendant Report|new page]].

== Author / Terms ==
As per the end of Cousin.py:
translated_name = _("Descend] Tree"),
status = _("Stable"),
author_name = "Craig J. Anderson",
author_email = "ander882@hotmail.com",
description = _("Produces a graphical descendant tree"),

This is a report. It does NOT write. It is read only. But it still reads YOUR data. So:
DO NOT TEST NEW PLUGINS WITH YOUR RESEARCH DATA. EXPORT DATA FIRST TO HAVE A BACKUP, THEN RUN THE TOOL

But I do wish to have this report incorporated as a standard graphical report. I am still not responsible for any loss/damage when using this report. If any happens, tell me. There is no way it can happen (other than power outage, power spike, etc) and I'd like to know. Still not responsible though. :)

As per the top of Cousin.py:
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
I used this only because Descendant.py (which this was based) used it.

Please contact me at the above with any comments, questions, testing, criticism, opinions, yadda, yadda, yadda. I'm an equal opportunity ignorer (kidding).

== Comments / Thanks ==
I have already used this report for many upon many family
members. And I love this report a LOT and super anxious to
share it with the world. And I am also in the process of
looking for code improvements, clean up, etc. I would like
to release this report to you all for testing, criticism,
opinions, yadda, yadda, yadda.

I would like to thank: (as shown in DescendTree.py)
# Copyright (C) 2000-2007 Donald N. Allingham
# Copyright (C) 2007-2008 Brian G. Matherly
and everyone else that had a hand in this code for their
wonderful work. This report is 80% new code but is/was
STRONGLY based on their code. And I still use this code
for reference.

[[Category:GEPS|D]]
[[Category:Plugins]]
[[Category:Proposed_Report_Specifications]]
[[Category:Reports]]

Add Table of Contents or Index to reports

2025-09-26T04:56:01Z

ErickLedger: remove extra "the"

{{languages|Add Table of Contents or Index to reports}}

How to add a Table of Contents(TOC) or an index to a Gramps generated report in [https://www.libreoffice.org/ LibreOffice]. LibreOffice is a great companion for Gramps.

==Background==
Gramps embeds invisible indexing markers in reports created in the Open Document Text (.odt) format. These indexing markers are also supported in the older Open Office (.sxw) formats.

The HTML and PDF output formats have a different system of named anchors, designed to support hotlinking.

These hidden tags allow the generation of a Table of Contents or an Index of names within reports.

Note that the hidden tags can also be used during post-process collation of Gramps generated reports with other materials. When pages of a such a collated document are re-flowed, the tags can allow a desktop publishing application to control pagination and generate their own style of indices, tables of content & end notes.

Because post-process repagination is so ubiquitous, the addition of dated and paginated footers is both easier and more efficient in those external desktop publishing suites. 

==Getting started==
[[File:Toc tutorial 1.jpg|thumb|right|450px|Fig. 1 Creating a Book Report]]
The first step is to create a report. This example creates a book report to demonstrate that multiple reports can be combined.
From the menu select When you select {{man menu|Reports-->Books...}}

{{-}}
[[File:Toc tutorial 2.jpg|thumb|right|450px|Fig. 2 Book Report]]
This opens the main {{man label|[[Gramps_{{man version}}_Wiki_Manual_-_Reports_-_part_3#Manage_Books_dialog|Manage Books]]}} dialog. It has two lists. The top list shows all the available reports that can be added to the book. The bottom list shows all the reports that have been added.

In this example, you can see that the book will include a ''Title page'', a ''Complete Individual Report'', a ''Detailed Descendant Report'' and a ''Detailed Ancestor Report''. Click {{man button|OK}} to generate the report.

{{-}}

==Insert a Table of Contents==
Once the report has been generated, open it in ''LibreOffice Writer''.

{{-}}
[[File:Toc tutorial 3.jpg|thumb|right|450px|Fig.3 Insert break > Type > Page Break]]
Many people like the Table of Contents to appear after the Title Page. To do so, first insert a page break after the text of the Title Page.

From the {{man button|File}} menu, select {{man menu|Insert->Manual Break ...'}}. Choose {{man button|Page Break}} and click {{man button|OK}}
{{-}}
[[File:Toc tutorial 4.jpg|thumb|right|450px|Fig. 4 Insert->Indexes and Tables->Indexes and Tables .... ]]
Scroll to the newly inserted page and add the Table of Contents by selecting {{man menu|Insert->Indexes and Tables->Indexes and Tables ...}}.

{{-}}
[[File:Toc tutorial 5.jpg|thumb|right|450px|Fig. 5 Indexes and Tables - dialog]]
In the {{man label|Indexes and Tables}} dialog, change the type to {{man label|Table of Contents}}. Also, be sure that the {{man label|Outline}} check box is unchecked and the {{man label|Index Marks}} check box is checked. This tells ''LibreOffice Writer'' to create the TOC from the marks that were embedded by Gramps.

{{-}}
[[File:Toc tutorial 6.jpg|thumb|450px|right|Fig. 6 Example of a Table of Content]]
After you click {{man button|OK}}, the Table of Contents should appear.

{{-}}

==Insert an Index==

[[File:Toc tutorial 3.jpg|thumb|right|450px|Fig. 7 Insert break > Type > Page Break]]
Most people like the index to be at the end of the book. To do so, place the cursor at the very end of the book, and insert a page break like you did for the TOC.

From the {{man button|file}} menu, select {{man menu|Insert->Manual Break ...'}}. Choose {{man button|Page Break}} and click {{man button|OK}}

{{-}}
[[File:Toc tutorial 7.jpg|thumb|right|450px|Fig. 8 Indexes and Tables - dialog]]
Next, open the {{man label|Indexes and Tables}} dialog like you did for the TOC. This time, change the type to {{man label|Alphabetical Index}}.

{{-}}
[[File:Toc tutorial 8.jpg|thumb|right|450px|Fig. 9 Example of an index]]
Click {{man button|OK}} and the index will appear.
{{-}}

==Conclusion==
*Adding a TOC(Table of Contents) and an Index to your documents can be done quickly.

==See also==
* [[Gramps_{{Version manual}}_Wiki_Manual_-_Reports_-_part_3#Books]]

[[Category:Tutorials]]
[[Category:How do I...|A]]

Import from another genealogy program

2025-09-26T04:25:11Z

ErickLedger: /* Known issues */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

<hr>
=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (easy)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* Gramps [[Import_from_another_genealogy_program#Gramps_Addon_TMG_importer|TMG importer]] Addon - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "[[Gramps_6.0_Wiki_Manual_-_Settings#Input_Options|Default family relationship]]" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

<hr>

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-26T04:21:53Z

ErickLedger: /* The Master Genealogist (TMG) */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

<hr>
=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (easy)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* Gramps [[Import_from_another_genealogy_program#Gramps_Addon_TMG_importer|TMG importer]] Addon - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

<hr>

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-26T04:21:27Z

ErickLedger: /* The Master Genealogist (TMG) */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (easy)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* Gramps [[Import_from_another_genealogy_program#Gramps_Addon_TMG_importer|TMG importer]] Addon - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-26T04:19:49Z

ErickLedger: /* The Master Genealogist (TMG) */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (easy)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* [[Addon:TMGimporter]] - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-26T04:18:53Z

ErickLedger: /* The Master Genealogist (TMG) */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

[https://wikipedia.org/wiki/The_Master_Genealogist The Master Genealogist (TMG)] was genealogy software originally created by Bob Velke for Microsoft DOS in 1993, with a version for Microsoft Windows released in 1996. Official support for TMG ceased at the end of 2014.

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (simple)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* [[Addon:TMGimporter]] - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-26T04:17:17Z

ErickLedger: /* The Master Genealogist (TMG) */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

Dis

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (simple)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* [[Addon:TMGimporter]] - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-26T04:16:27Z

ErickLedger: /* The Master Genealogist (TMG) */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

Dis

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (simple)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

Non working option:
* [[Addon:TMGimporter]] - Not released - Abandoned

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-26T04:13:53Z

ErickLedger: /* The Master Genealogist (TMG) */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have three working options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (simple)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-26T04:13:38Z

ErickLedger: /* The Master Genealogist (TMG) */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have three options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]] (simple)
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal (requires purchase)
* [[Import_from_another_genealogy_program#tmg2gramps|tmg2gramps]] script from Cohsoft (advanced)

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-26T04:12:50Z

ErickLedger: /* The Master Genealogist (TMG) */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have three options:
* [[Import_from_another_genealogy_program#GEDCOM_2|GEDCOM export from TMG]]
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] program - By John Cardinal
* tmg2gramps script from Cohsoft

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-26T04:12:04Z

ErickLedger: /* The Master Genealogist (TMG) */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have three options:
* GEDCOM export from TMG
* [[Import_from_another_genealogy_program#tmgtogedcom|tmgtogedcom]] - John Cardinals program
* tmg2gramps script from Cohsoft

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-23T07:56:02Z

ErickLedger: /* Ancestrologie */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

[https://www.ancestrologie.org/ Ancestrologie] seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-23T07:53:54Z

ErickLedger: /* See also */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM] (12 Aug 2024)

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

Ancestrologie seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-23T07:52:40Z

ErickLedger: /* Addon:GEDCOM 7 */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see
* [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM]

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

Ancestrologie seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-23T07:52:26Z

ErickLedger: /* Addon:GEDCOM 7 */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM]

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

Ancestrologie seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Import from another genealogy program

2025-09-23T07:51:59Z

ErickLedger: /* Addon:GEDCOM Extensions */

{{languages|Import from another genealogy program}}
{{man tip|Tips on importing from other genealogy programs}}
There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information.

You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.

We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.

Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manual}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.

== Gramps to Gramps==

This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy & living person filters.

Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.
=== What's not included? ===

{{Template:Backup Omissions}}

== Standard GEDCOM as transfer tool==

Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100% compliant and ''standard'' GEDCOM format.
{{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}
{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}
Due to these idiosyncrasies and dialects of GEDCOM, you should always [[How_to_make_a_backup|make a backup]] before importing any GEDCOM file.

<ol>
<li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li>
<li>In Gramps, create a blank Tree database to accept the imported data.</li>
<ol style="list-style-type:lower-alpha">
<li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li>
<li>Click the {{man button|New}} button to create a new family tree</li>
<li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li>
<li>click on the {{man button|Load Family Tree}} button to open.</li></ol>
<li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li>
<li>Start the import</li>
<ol style="list-style-type:lower-alpha">
<li>Use the File Selector to locate the GEDCOM file created by your originating program</li>
<li>select the GEDCOM file</li>
<li>click the {{man button|Import}} button</li></ol>
</ol>

{{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}}

Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path.

== Spreadsheet import ==

Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.

The CSV import option currently doesn't allow import of all Gramps data.

For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.

For more details on this format see [[Gramps {{man version}} Wiki Manual - Manage Family Trees: CSV Import and Export]].

== Addon ==

===Addon:GEDCOM Extensions===
[[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions.

===Addon:GEDCOM 7 ===
In development for Gramps 6 or newer see [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781
Gedcom 7 Library - "Future basis of a new Gedcom 7 import addon"] 2025/06/04

== Import instructions for different programs ==

=== Aldfaer ===
[https://aldfaer.net Aldaer] is a Dutch genealogy application.

When exporting GEDCOM for surnames that include a Prefix, the NAME section outputs the surname prefix (SPFX) tag but not the surname (SURN) tag. This causes the NAME data between the slashes to be used for the SURN data. So the Prefix data is repeated.

GEDCOM 5.5.1 Aldaer dialect Example:
<pre>
1 NAME Peronella/van der Linden/
2 SPFX van der
2 NICK Nelly
1 SEX F
</pre>

Should follow the form:
<pre>
1 NAME William D. "Bill" /van der Berg/ Jr.
2 GIVN William D.
2 NICK Bill
2 SPFX van der
2 SURN Berg
2 NSFX Jr.
1 SEX M
</pre>

GEDCOM 5.5.1 specified order is:
<pre>
NPFX (name prefix)
GIVN (given name)
NICK (nickname)
SPFX (surname prefix)
SURN (surname)
NSFX (name suffix)
</pre>
==== See also ====
Gramps community support forum (Discourse) topics:
* [https://gramps.discourse.group/t/confuson-about-use-of-prefix-or-name-in-aldfaer-gedcom/5862 Confusion about use of prefix or name in Aldfaer GEDCOM]

Support forum:
* [https://aldfaerforum.nl/forum/oude-berichten/17-aldfaer-gedcom-en-tussenvoegsels-achternamen.html Aldfaer gedcom and suffixes surnames]: Aldfaer (09 Mar 2014)
* [https://forum.ancestris.org/index.php?topic=4109.0 importing Gedcom from the Dutch program Aldfaer]: Ancestris (4 Nov 2022)
Modern Software Experience by Tamura Jones:
* [https://www.tamurajones.net/Aldfaer4.0.xhtml Aldfaer 4.0] (4 Apr 2008)

=== Ancestrologie ===

Ancestrologie seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.

==== Programs for fixing some of the known problems ====
Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments.

; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements.

; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec.

; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:
2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111

The data (in this case 75111) may be absent or extend to CONT lines.
The non-standard elements converted to APPX notes include:

; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"
; _ANCES_ORDRE : Considered non-critical, events classification
; _ANCES_XACTE : Non-critical (certificat found = 1)
; _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit'')
; EVEN F : Invalid EVENTS_RECORDED format in a SOUR record
; EVEN I : (Same)
; LIEU : A subdivision of place, is not our place but a division
; XTYPE : These seem to be OBJE subordinates
; XIDEN : Considered non-critical, media object used for primary media (photo)
; XMODE : (file is not present at the FILE address)

In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

1 FILA Enfant légitime

becomes

1 FACT Enfant légitime
2 TYPE FILA

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.'''

'''Please also feel free to provide feedback on broken scripts or incorrect ''fixes'''''

-----

=== Ancestry.com ===

Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,

But some GEDCOM idiosyncracies remain.

These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.
==== Records not imported ====
There were around 8000 lines that were reported as "not imported". They were the following categories:
* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else.
* many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.
* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.
Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons.

The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.
==== Scan for Errors====
Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''.

There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born.

==== Source objects ====
The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".
You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.
==== Notes ====
Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find.

You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.
==== Dates ====
Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard. Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format].

There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing.

A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates"

==== Final cleanup of Ancestry's empty export records ====
A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems.

==== additional Ancestry notes ====
[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com]

[https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers]

[Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:
* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept]

See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com
-----

=== Evidentia ===
If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [http://evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM.

==== General tips ====
When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another.

==== People ====
===== Import into Evidentia as subjects =====
First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.

===== What Evidentia imports and exports =====
Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person:

; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia
; NAME Lakshmi /Wolowitz/ : Full name
; GIVN Lakshmi : Given name)
; SURN Wolowitz : Surname
; SEX F : Gender
; BIRT : Birth year

==== Events and facts ====
As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version.

===== Manually add facts into Evidentia =====
The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations.

===== Export some types of facts to Gramps =====
Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.

==== Sources and Citations ====
===== Manually add to Evidentia first =====
Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps.

There are two reasons to follow this workflow:
* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.

* Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted!

===== Match your source title and source abbreviation =====
When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs.

===== Complete publication information exported =====
Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication.

===== Citation title only used in Evidentia =====
Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them.

==== Claims and proof ====
===== Default GEDCOM export =====
When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's:

* Individual information: id, name, gender
* Claim type: facts, events, or attributes
* Source information: title, abbreviation, and full publication info (PUBL)
* Full citation (PAGE)

If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps.

===== Evidentia-specific GEDCOM export =====
Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps).

If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example:

* Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840.
The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."
* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810."

=== Family Tree Maker ===

GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].
{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog. ''extensively revised for Gramps 5.0 on 8 Aug 2018''}}
==== If you do not have access to Family Tree Maker ====
(Tested with FTW file created by Family Tree Maker 2006)
* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Create a new account (with bogus data)
* Disable any syncing features when asked
* Create new Project: File > New Project...
* File > Import GEDCOM... > Browse > Select FTW file
* File > Export GEDCOM...

==== Family Tree Maker 2005 ====

Select File -> Export File -> Entire File...
In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.
In the "Export to GEDCOM" dialog, set the following:
* Destination: FTM
* GEDCOM: Version 5.5
* Character set: ANSI (Gramps will convert to UTF-8 upon import)
* Deselect "Indent records"
* Select "Abbreviate tags"

Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off.

{{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}}

==== Known issues or custom extensions ====

# Blank lines
# Issues on date string
# PHON in INDI records
# PLAC for general data
# The source quality is coded as a NOTE rather as QUAY
# Marriage start status
# Double dates use the first date rather than the second

==== Programs for fixing some of the known problems ====

; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows.

====Experimental way====

[[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database.

[[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data.

=== Geneweb ===

Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}.

=== GenoPro ===

==== Gedcom ====

GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464].

==== GenoPro to Gramps ====

Experimental converter (.gno to .gramps) on {{bug|2757}}.

=== Heredis ===

;Modifications of GEDCOM from Heredis to import in Gramps

''With editor (like gedit or note++) find and replace '''« > »''':''

;1. Non standard tags of Heredis

'''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...

1 _FIL LEGITIMATE_CHILD > suppress all lines

1 _UST MARRIED > suppress all lines

1 RESN privacy > suppress all lines

NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)

;2. Assign value Y to following to tags

1 BIRT > 1 BIRT Y

1 DEAT > 1 DEAT Y

1 MARR > 1 MARR Y

1 MARC > 1 MARC Y

1 DIV > 1 DIV Y

1 CHR > 1 CHR Y

1 ... > 1 ... Y

;3. Sources and Repositories

1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)''

'''3 MEDI > 1 MEDI or 1 PUBL'''

_ARCH > AUTH

;4. Change levels in Associations

2 ASSO @398195I@ > 1 ASSO@398195I@

3 TYPE INDI > suppress all lines

3 RELA > 2 RELA

3 TITL > 2 TITL

3 NOTE XXX > 2 NOTE XXX If a note is associated

;5. Équivalents of disks drives when loaded Linux Gramps

FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/

FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/

;6. For people's tags located in Events instead of Attributes

Description Type

Profession > Occupation

Titre > Nobility title

No (signe) > null

YES (end of line) > null

There would be a way to assign some fields in attributes instead of events. It's a mix up.

By ''Ifs, Oct 25 2011''

====Known issues====

According to "''Ancestris''" wiki, GEDCOM generated by Heredis may :

# Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.
# Not properly manage dates (calendars)
# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.
# Not properly manage sources and repositories

There are some alternatives to GEDCOM generated by Heredis :

* Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].
* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].
* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].
* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]!

=== Legacy ===

According to "''Ancestris''" wiki, GEDCOM generated by Legacy may :

# introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.
# ignore SOURCE_REPOSITORY_CITATION.
# modify MEDI tag design, which can be used into CALN.

[https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing.

* Legacy 7 uses an invalid character encoding: ANSI
: Manually ceaning this up is discussed on the Discourse forum: [https://gramps.discourse.group/t/gedcom-character-encoding-mismatch/3551 GEDCOM character encoding mismatch]

=== MinSläkt ===

MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data].



=== MyHeritage Family Tree Builder ===

Instead of using GEDCOM you can use the Gramps addon to transfer your data to Gramps

* Download and install the free MyHeritage Family Tree Builder:
http://www.myheritage.com/family-tree-builder
* Login to your account
* Enable any syncing features when asked

Then install the gramps addon [https://gramps.discourse.group/t/myheritage-ftb-to-gramps-data-transfer/6516 MyHeritage FTB to Gramps data transfer] and follow that advice.

=== Pro-Gen ===

PRO-GEN is a Microsoft Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.

Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Gramps importer plugin was created that reads the native PRO-GEN files. The plugin is included in the standard Gramps distribution.

To import the data, Gramps needs to be able to locate the PRO-GEN directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a <code>~/pg30</code> folder. If you are running Gramps on a Windows PC and have a copy PRO-GEN on that same computer, then no export or copying to another device is necessary before starting the import.

Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that <code>~/pg30</code> folder.

In the following steps, we will assume that the PRO-GEN files are at <code>~/pg30</code>

Import the data:
* start Gramps
* From the {{man menu|Family Trees}} menu, select "{{man menu|Manage Family Trees...}}"
* use the "{{man button|New}}" button to create a new family tree database
* Give the Tree a name (like "<code>PRO-GEN imported Tree</code>") and select that new database
* click the "{{man button|Load Family Tree}}" button to open the blank tree database
* go to menu {{man menu|[[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Importing_data|Family Trees -> Import]]}}
* in the file Selection dialog, go to the <code>~/pg30/nl/data</code> directory
* select the <code>.DEF</code> file of your PRO-GEN database
* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)
* click "{{man button|Import}}"
* wait as the data processes...

To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

=== RootsMagic, all versions ===

RootsMagic is a Windows program that offers features to synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

Import of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. They will then be imported as parts separated by comma's, and the same will happen to prefixes, if they exist.

Exported GEDCOM files are quite clean, when you clear the checkmarks for

* Note formatting (bold, etc)
* Extra details (RM specific)

which are available in the bottom left of the Gedcom Export Options screen.

The export of tasks is disabled by default, and untested.

RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The information entered for those is stored in specialized attributes, which are not exported when the Extra details checkmark is cleared. And when you use templates, you may find formatted citation sentences in the standard GEDCOM fields, like TITL and PAGE. These fields may also include HTML markup for italic and bold.

Note that when you import sources from the FamilySearch tree into RootsMagic, the full formatted citation text is stored in the source title, because of the way FamilySearch works, with a flat model. In that case, the citation fields (date, page) are all empty.

RootsMagic 9 has a quirk that duplicates PAGE information into a NAME tag that should not be exported in the citation. This can cause lots of import warnings in Gramps, which can be discarded.

=== The Master Genealogist (TMG) ===

You have two options.

==== GEDCOM ====

This is the easy option, but much of your data may not transfer correctly. Try it first anyway in case it works for you.

Read this first: [http://mjh-nm.net/GED-EXPT.HTML TMG™ GEDCOM Export - Guide to Limitations and Issues ©MJH (Michael J. Hannah)][http://archiver.rootsweb.ancestry.com/th/read/TMG/2014-09/1409969819]

Then with that in mind:

# Tell TMG to export your data to GEDCOM, following the instructions that come with TMG.
#* TMG gives you many options for GEDCOM exports. What works best will depend in part on the way you organised your family tree. Choose whatever you like.
#* Write down which choices you make.
# Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].

If the results aren't too bad, but aren't quite right, try again after changing one or more of TMG's GEDCOM export options. You'll remember what you did previously because you wrote them down. Didn't you?

Keep trying and hopefully you'll hit on the combination that works best for you.

If you can't get good results, you'll have to use the tmg2gramps method instead.

===== Known issues =====

Using a GEDCOM export from TMG does not transfer the following information:

See [[Import_from_another_genealogy_program#Data_tmg2gramps_successfully_converts | Data tmg2gramps successfully converts]]

==== tmg2gramps ====

For many people, using GEDCOM will lose too much information, most notably "Witness" information.

If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort.

For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database.

You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]].

tmg2gramps was designed to, '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well.

{{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}}

===== Data tmg2gramps successfully converts =====

Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows:

*"Witness" information.

*"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field.

*Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is there and can be corrected in Gramps.

*tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

===== Known issues =====

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1:

# Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth — so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).
# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.
# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" — this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "Default family relationship" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manual}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

===== Preparing to run tmg2gramps =====

Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04.

====== Copy your TMG projects folder ======
Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here:

<code>C:\Program Files\The Master Genealogist\projects</code>

====== Rename your copied TMG projects folder ======
Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>'

====== Convert TMG filenames to lowercase ======
Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt:

<code>$ rename 'y/A-Z/a-z/' *</code>

====== Prepare MySQL ======
Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal:

<code>$ sudo apt-get install mysql-server</code>

That will either install MySQL, or if it is already installed, it won't cause any harm.

The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected:

<code>$ sudo apt-get install libdbd-xbase-perl</code>

Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt:

<code>$ mysql -u root</code>

If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead:

<code>$ mysql -u root -p</code>

You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt:

<code>mysql> show databases;</code>

That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt:

<code>mysql> create database tmg_gramps;</code>

Now, make sure that you can connect to the database with the appropriate password and privileges by typing:

<code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code>

You can now exit MySQL:

<code>mysql> exit</code>

====== Preparation for the tmg2gramps script ======
...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside:

<code>$ ls -l</code>

This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as:

<pre>
smith__.acc
smith__.pjc
smith_$.cdx
....
</pre>

...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above.

And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following:

<code>$ chmod +x tmg2gramps.pl</code>

Now, it is finally time to run tmg2gramps and convert your data.

===== Running tmg2gramps =====

When running tmg2gramps, the example below makes the following assumptions:

* Name of TMG project: '''''<code>smith</code>'''''
* Home directory: /home/'''''<code>asmith</code>'''''

Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):

$ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass

You should now be able to watch tmg2gramps running in terminal.

The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards.

When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder.

You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:

$ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps

Open Gramps, create a new family tree, and import the .gramps file you just created.

Congratulations! Your TMG data is now in Gramps.

{{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}}

==== TMG-Working-Group ====

Information only at the moment.

'''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti''

https://github.com/girimonti/TMG-Working-Group

==== Gramps Addon TMG importer ====

An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge).
* [[Addon:TMGimporter]] - Not released - Abandoned

See {{bug|7591}} for more details and tests.

==== tmgtogedcom ====

TMG to GEDCOM includes a template for exporting from TMG into Gramps. In addition to the commonly-supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that supports:

* Witnesses and role labels
* Flag values as Gramps Attributes

See {{bug|7591}} and [https://www.tmgtogedcom.com/en/template-gramps.htm John Cardinal's project ]

=== Visuged ===

According to a "''Ancestris''" wiki, GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

# Partial sources
# Repositories are lost
# BAPT, ASSO are lost
# Internal numbers are modified

=== WikiTree ===

The GEDCOM generated by the [https://www.wikitree.com/wiki/Special:DownloadGedcom Special:DownloadGedcom] WikiTree application has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.

Their database repeats the <code>NAME</code> data incorrectly parsed into a <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given incorrectly deprived of the "middle name", an occasional custom "preferred given name", a mandatory custom "middle name" field, and Surname). This conflicts with the GEDCOM standard form for the <code>GIVN</code> data. Although Gramps does have a "Call name" (exported as <code>_rufname</code>) that could correspond to the <code>_PGVN</code> (if WikiTree enforced any rules), it does not have the American-centric separate Middle Name. The <code>_PGVN</code> is more similar to the <code>NICK</code> tag. Thus, it is better to force the import to ignore the mangled <code>GIVN</code> (by re-naming it to <code>_GIVN</code>) and let it re-parse the <code>NAME</code> field correctly.

The <code>NAME</code> dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:
* [https://www.wikitree.com/g2g/1038205/wikitree-gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] May 2020

====See also====
* [https://www.wikitree.com/g2g/1475/how-to-export-a-gedcom-file-from-wikitree How to export a GEDCOM file from WikiTree] Apr 2012
* [https://www.wikitree.com/g2g/1097159/gedcom-import-improvement-to-wt-from-gramps gedcom import improvement to WikiTree from Gramps] Aug 2020
* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps: A Guide]
* [https://www.wikitree.com/wiki/Space:Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]
* [https://www.wikitree.com/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]
* [https://www.tamurajones.net/WikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] Aug 2012 by Tamura Jones
* [https://www.wikitree.com/g2g/6292/do-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]
* Experimental [https://github.com/hgboldt/WikiTree WikiTree] gramplet by Hans Boldt. Search for the Active Person from Gramps in WikiTree, and save the WikiTree profile id as an attribute. View the WikiTree profile for the current person. Generate a WikiTree style of biography for the Active Person.
* The [[Addon:Biography_Quickview|Biography]] addon quickview Person report was also created to generate a WikiTree compatible Biography entry.

Source code on [https://github.com/wikitree GitHub WikiTree project] for the <code>src/GedcomExport.php</code>

== See also ==
'''Discourse community support forum:'''
* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]
* Re-parsing non-uniform date formats: [https://gramps.discourse.group/t/making-date-input-more-flexible/2814 Making Date Input More Flexible]

* [[Other genealogy tools]]
* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for RootsMagic]
* [http://wiki-en.genealogy.net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (originally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch])
* 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the GEDCOM 7.0.2 specification was published 15 Jun 2021 and it is typical for revised specifications to not be supported until there is sufficient reason to re-develop.)
{{languages|Import from another genealogy program}}
[[Category:How do I...]]
[[Category:Developers/General]]

Mac OS X:Application package

2025-09-23T07:46:49Z

ErickLedger: /* If something seems to go wrong */

[[File:macos_200x200.png|128px|right|link=Download#Mac_OS_X]]
Installation of the ready-to-run Gramps application for [https://en.wikipedia.org/wiki/MacOS macOS] (originally Mac OS X, previously shortened as OS X). This is also known as the GTK-OSX port of Gramps for Mac. It is a single, stand-alone bundle which uses the native quartz windowing system of macOS instead of X11.

== Before installation ==

{{man tip|Apple ''macOS versions'' |*Gramps 5.0 requires Mac OS X 10.9 (Mavericks) and later.
*Gramps 5.1 requires Mac OS X 10.10 (Yosemite) and later.
*Gramps 6.0 requires macOS 11.0 (Big Sur) and later.
 
(5-year support window for the macOS dependencies)}}

;'''Back up your databases:''': If you're using Time Machine, that's already taken care of. (You do test your Time Machine backups periodically, right?) But it doesn't hurt to have a spare copy set aside before starting up a new version. If you've been using the Gtk-OSX build, version 3.2.4 or later, just copy <code>Library/Application Support/gramps/grampsdb</code>. (Right click/option click and select "Make a copy" from the menu. It will be named <code>grampsdb(2)</code>.

;'''New Version Notice:''': If you are upgrading from the pre-built Gramps Application version 3.2.3 or earlier (or a build from source version) and you want to keep your old database and settings, you'll need to create a <code>Library/Application Support/gramps</code> folder with your existing data in it. Unless you've changed the location in Preferences, the data is in a hidden folder in your home directory called "<code>.gramps</code>". Select a Finder window and select Go>Go to Folder from the menu. Type "<code>/Users/yourname/.gramps</code>" in the dialog box that opens up, and click on "Go". (Yes, substitute your userid for "yourname".) The hidden folder will appear, highlighted and open. Option-drag the whole thing to <code>Library/Application Support</code> (the one in your home folder, not the one in your boot drive's "root" directory). Slow-double-click on the new copy so that you can edit the name and delete the '.' at the beginning to unhide it.

{{man note|''Migrating to [https://en.wikipedia.org/wiki/Mac_transition_to_Apple_silicon Apple Silicon]?''|Make an [[How_to_make_a_backup|XML backup]] of your databases on your Intel Mac and copy them to your Apple Silicon Mac and restore them there after installing Gramps. There seems to be a binary object incompatibility in SQLite3 databases, even when running an Intel binary using Rosetta2.}}

== Installing Gramps ==

From the '''[[Download#macos]]''' page download the dmg. Once it's downloaded, you can open the file (just double click on it in Finder if your browser doesn't open it automatically) and drag the Gramps application wherever you like. Once installed on your computer, it opens like any other application.

'''Links with other programs:''' Double clicking an image in the media reference editor should bring up Apple Preview (or a whatever program you've set as the default to edit that kind of image) to view the image. Clicking the view button in an internet reference should bring up the URL in the default browser. Clicking the Google Maps button in the Places display should bring up the map in the browser.

Gramps doesn't use the X11 Mac package. It's useful to install [http://www.documentfoundation.org/download/ LibreOffice], [http://www.calligra-suite.org/ Calligra] (or [http://www.neooffice.org/ NeoOffice], a more mac-friendly version) to work on your reports after saving them from Gramps.

== What goes where ==

'''File structure:''' Gramps database and settings files can be found at the following places in the Mac file system (Gramps Version 3.2.5 and later):
* The Gramps database with the user's genealogical information is stored under <code>/Users/<username>/Library/Application Support/gramps/grampsdb</code>
* Setting files (ini-files) are found here: <code>/Users/<username>/Library/Application Support/gramps/gramps51</code>
* Start-up settings for Gramps (for e. g. the environment variable LANG) can be accessed through Gramps.app (generally in /Applications): Right click on "Gramps.app", select "Show Package Content" from the menu, the start-up settings are found in the file <code>Contents/MacOS/Gramps</code>.

== Advanced setup ==

If Gramps has the appropriate translation, calendar, etc. it will honor the settings in System Preferences>Language and Region provided that the combination results in a locale that exists in /usr/share/locale. It will always fall back to English if it can't figure out your Language & Region settings. Some examples: French and France, Belgium, or Canada work fine, as do German and Germany or Switzerland and Dutch and Netherlands or Belgium. German and France doesn't work, nor does Dutch and Switzerland.

If you want to run Gramps with different locale settings than you use for your system settings, you can use the "defaults" program from Terminal.app (Applications:Utilities:Terminal.app):
defaults write -app Gramps AppleLocale "de_DE"
to set Gramps to operate in German with German calendar and formatting.

To read the setting use:
defaults read -app Gramps
this gave "Can't determine domain name for application Gramps; defaults unchanged" for me; if you have problems you can use
defaults read org.gramps-project.gramps

The settings are stored in ~/Library/Preferences/org.gramps-project.gramps.plist

To remove the special settings
defaults delete -app Gramps AppleLanguages (or AppleLocale or AppleCollation).

Note that you will need to run Gramps at least once before the defaults system will recognize its existence; before that trying to use defaults will produce an error about there being no Gramps application.

[[Howto:Change the language of reports]] has more information on language features in Gramps. When reading it, remember that AppleLanguages (which corresponds to the language list on the Languages & Text system preference pane) sets the LANGUAGE environment variable and AppleLocale (Formats in the Languages & Test pane) sets the LANG variable.

=== Dictionaries ===
The spelling checker uses [https://en.wikipedia.org/wiki/MySpell MySpell] dictionaries -- the same ones that [http://www.documentfoundation.org/download/ LibreOffice] and NeoOffice use. Unfortunately, they bury them in their application bundles, so you can download them [http://archive.services.openoffice.org/pub/mirror/OpenOffice.org/contrib/dictionaries/ here]. You need to install them in /Library/Dictionaries, and you'll need to authenticate as an administrator to do so. If you have one of them installed and know how to make symbolic links from the command line, you'll find them in Contents/share/uno_packages/cache/uno_packages, scattered about in the hash-named directories. You'll need to link both the aff and dic files (e.g., en_US.aff and en_US.dic).

== Bugs ==

=== If something seems to go wrong ===

You'll find error messages in the console log, which you can view with <code>/Applications/Utilities/Console.app</code>

All of the known bugs in previous version have been corrected in Gramps {{Version_Mac}} and later. There will no doubt be new ones; report them in the usual way on [https://gramps-project.org/bugs/my_view_page.php MantisBT] ([[Using the bug tracker]] instructions). When reporting what you're sure is an macOS specific bug, please set the Platform field to "mac" (no quotes, caps, or spaces!) so that I can find it easily.

Previous Gramps version 3.2.4, bugs are described at [[Mac OS X:Build from source:gtk-osx:bugs]].

== Updates ==

Gramps stores all its internal data in <code>~/Library/Application Support</code>. So, to upgrade a Gramps application bundle to a newer version, just throw the old application in the Trash. Make a backup copy of your data, just in case, then download the new version of the application and just use it. If you don't like the new version and want the old one back, throw the new version in the Trash and fetch the old one back from the Trash. The Gramps version is shown in Finder if you use column view; otherwise right click on it and select Get Info.

[[Category:Developers/Packaging]]
[[Category:Documentation]]

Installing Gramps for macOS computers

2025-09-23T07:41:50Z

ErickLedger: /* MacPorts */ No hypen shown on "Third-party Addons" page stick to one spelling.

{{languages|Installing Gramps for macOS computers}}

{{man warn|Before upgrading your distribution|Use your '''earlier version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees to the hardy and portable [[#1|XML format1]].}}
[[File:macos_200x200.png|248px|right]]


== Application package ==

The [[Mac_OS_X:Application_package|application package]] is the recommended way of installing Gramps on macOS.

First read the [[Mac OS X:Application package|before installation]] instructions.

Tested for compatibility with Apple macOS/Mac OS X versions 10.13 ([https://en.wikipedia.org/wiki/MacOS_version_history#Version_10.13:_%22High_Sierra%22 High Sierra]) through 14 ([https://en.wikipedia.org/wiki/MacOS_version_history#Version_14:_%Sonoma%22 Sonoma]). ''Help determining your Operating System version can be found in the [https://support.apple.com/en-us/HT201260 HT201260 Apple Support article.]''

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next, drag the Gramps application to your application folder and double-click to launch it. (For Apple Mac OS X, alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.)

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. Should this fail for any reason, '''Create''' a new Family Tree and [[How_to_restore_a_backup|'''Import''' the back-up]] into this new Tree.

{{-}}

=== Adding additional Spell Checking languages on macOS ===
{{man tip|[[Mac_OS_X:Application_package#Dictionaries|Spell Checking:]]|Gramps uses a different spell checker than the one provided by Mac OS X, with different spelling dictionary requirements. We can't easily provide dictionaries for all of the supported languages in the bundle, but they're easily downloaded from [https://extensions.openoffice.org/ OpenOffice.org's website]. Download the language you want and save it, then navigate to the download in Finder. Most browsers have a downloads window that offers "Show in Finder" in its context menu. Change the file extension from <tt>oxt</tt> to <tt>zip</tt>, then from the context menu select '''Open with... Archive Utility''' to decompress it. In the decompressed folder or perhaps in a subfolder you'll find the dictionary files in pairs, <tt>foo.aff</tt> and <tt>foo.dic</tt>. Some languages have more than one pair with a README file to explain why. Select a pair and copy it to /Library/Dictionaries (you'll have to authenticate with an administrator id and password), and if 'foo' isn't already a language or locale code, make it one. For example, the French package includes several pairs with names like <tt>fr-moderne.aff</tt> and <tt>fr-moderne.dic</tt>. The spell checker doesn't recognize those names, so when you copy them to /Library/Dictionaries you must rename them to <tt>fr.aff</tt> and <tt>fr.dic</tt> or <tt>fr_FR.aff</tt> and <tt>fr_FR.dic</tt>. You can have more than one dictionary pair installed if you use several languages, but one '''must''' match the language you use for Gramps or spell checking won't be enabled at all.}}

{{-}}

== MacPorts ==

MacPorts is a package manager for Apple Mac.

* [[Mac_OS_X:Build_from_source:MacPorts|MacPorts]]

Why use the version from MacPorts? Certain plugins or addons require additional supporting software in order to operate. With MacPorts, you can install such software easily (most of the time; there could be exceptions). With the official .dmg installer, installing such additional software is more difficult or impossible.

The [[Addon:Prerequisites_Checker_Gramplet|Prequisites Checker]] can identify if any addons have been installed that require such additional software.

{{-}}

== Homebrew ==

The macOS application bundle can also be installed via the Homebrew package manager as a cask. Note that this is '''not''' a Homebrew build, it is a repackaging of the same Gramps.app provided in the above dmg. It does not depend on or use any of the Homebrew-built libraries.

[https://wikipedia.org/wiki/Homebrew_(package_manager) Homebrew] is an open-source package manager for macOS (and Linux).

See https://github.com/homebrew/

{{-}}

== Notes ==
Backup to '''Gramps XML''' format when updating. ''Although Gramps reads and writes '''GEDCOM 5.5.1''' format fluently (because it is the de facto format for genealogical data interchange), never depend on such a rudimentary format for archiving your research. GEDCOM cannot store all the intricacies found in Gramps data.'' Always backup with the more robust Gramps XML format.

[[File:Menubar-FamilyTrees-overview-FamilyTree-Loaded-example-60.png|thumb|right|450px|Menubar - {{man menu|"Family Trees > Make Backup..."}}]]

You will find a [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Backing_up_a_Family_Tree|{{Man menu|Make Backup...}}]] option in the {{Man menu|Family Trees}} menu of recent Gramps versions. Alternately, use [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|{{Man menu|Export...}}]] in the same menu but deselect the privacy and filtering options in the Exporter Assistant to avoid omission of any data.

See: [[How to make a backup]]

== See also ==
===Installing Gramps for Desktops===
Installation instructions specific to the different OSes are on the [[File:linux_32x32.png|link=Installing_Gramps_for_Linux_computers#Linux_distributions]], [[File:windows_32x32.png|link=Installing_Gramps_for_Windows_computers]],[[File:macos_200x200.png|32px|link=Installing_Gramps_for_macOS_computers]] and [[File:Bsd daemon.png|32px|link=BSD_platforms]] pages.

===GitHub Gramps for Desktops Releases===
:* [{{github_url}}/releases/v{{version}} {{version}} version]
:* [{{github_url}}/releases/ Archive of Gramps releases]
Wiki pages
* [[Previous releases of Gramps]]
* [[:Category:Versions|Versions on various platforms]]

===Installing Gramps Web for online collaboration===
[https://gramps-project.org/blog/web/ Gramps Web] is a frontend for a hosted instance of Gramps
* [https://www.grampsweb.org/Deployment/ Docker]
* [https://www.grampsweb.org/LetsEncrypt/ Let's Encrypt and Docker Compose]

[[Category:Documentation]]

Installing Gramps for macOS computers

2025-09-23T07:39:49Z

ErickLedger:

{{languages|Installing Gramps for macOS computers}}

{{man warn|Before upgrading your distribution|Use your '''earlier version of Gramps''' to [[How_to_make_a_backup#Gramps_version_3.3_and_later|backup]] your Family Trees to the hardy and portable [[#1|XML format1]].}}
[[File:macos_200x200.png|248px|right]]


== Application package ==

The [[Mac_OS_X:Application_package|application package]] is the recommended way of installing Gramps on macOS.

First read the [[Mac OS X:Application package|before installation]] instructions.

Tested for compatibility with Apple macOS/Mac OS X versions 10.13 ([https://en.wikipedia.org/wiki/MacOS_version_history#Version_10.13:_%22High_Sierra%22 High Sierra]) through 14 ([https://en.wikipedia.org/wiki/MacOS_version_history#Version_14:_%Sonoma%22 Sonoma]). ''Help determining your Operating System version can be found in the [https://support.apple.com/en-us/HT201260 HT201260 Apple Support article.]''

After download: Double-click the .dmg file to mount the disk (note: your browser may do this for you automatically). Next, drag the Gramps application to your application folder and double-click to launch it. (For Apple Mac OS X, alternatively, you can click and hold on the disk icon at the top of the window of the mounted disk, and then option-drag to the Applications folder. This will create a new folder containing all the files, including the README and NEWS.)

Normally, when you try to load your old Family Tree you can allow it to be upgraded if necessary, and it will be opened. Should this fail for any reason, '''Create''' a new Family Tree and [[How_to_restore_a_backup|'''Import''' the back-up]] into this new Tree.

{{-}}

=== Adding additional Spell Checking languages on macOS ===
{{man tip|[[Mac_OS_X:Application_package#Dictionaries|Spell Checking:]]|Gramps uses a different spell checker than the one provided by Mac OS X, with different spelling dictionary requirements. We can't easily provide dictionaries for all of the supported languages in the bundle, but they're easily downloaded from [https://extensions.openoffice.org/ OpenOffice.org's website]. Download the language you want and save it, then navigate to the download in Finder. Most browsers have a downloads window that offers "Show in Finder" in its context menu. Change the file extension from <tt>oxt</tt> to <tt>zip</tt>, then from the context menu select '''Open with... Archive Utility''' to decompress it. In the decompressed folder or perhaps in a subfolder you'll find the dictionary files in pairs, <tt>foo.aff</tt> and <tt>foo.dic</tt>. Some languages have more than one pair with a README file to explain why. Select a pair and copy it to /Library/Dictionaries (you'll have to authenticate with an administrator id and password), and if 'foo' isn't already a language or locale code, make it one. For example, the French package includes several pairs with names like <tt>fr-moderne.aff</tt> and <tt>fr-moderne.dic</tt>. The spell checker doesn't recognize those names, so when you copy them to /Library/Dictionaries you must rename them to <tt>fr.aff</tt> and <tt>fr.dic</tt> or <tt>fr_FR.aff</tt> and <tt>fr_FR.dic</tt>. You can have more than one dictionary pair installed if you use several languages, but one '''must''' match the language you use for Gramps or spell checking won't be enabled at all.}}

{{-}}

== MacPorts ==

MacPorts is a package manager for Apple Mac.

* [[Mac_OS_X:Build_from_source:MacPorts|MacPorts]]

Why use the version from MacPorts? Certain plugins or add-ons require additional supporting software in order to operate. With MacPorts, you can install such software easily (most of the time; there could be exceptions). With the official .dmg installer, installing such additional software is more difficult or impossible.

The [[Addon:Prerequisites_Checker_Gramplet|Prequisites Checker]] can identify if any add-ons have been installed that require such additional software.

{{-}}

== Homebrew ==

The macOS application bundle can also be installed via the Homebrew package manager as a cask. Note that this is '''not''' a Homebrew build, it is a repackaging of the same Gramps.app provided in the above dmg. It does not depend on or use any of the Homebrew-built libraries.

[https://wikipedia.org/wiki/Homebrew_(package_manager) Homebrew] is an open-source package manager for macOS (and Linux).

See https://github.com/homebrew/

{{-}}

== Notes ==
Backup to '''Gramps XML''' format when updating. ''Although Gramps reads and writes '''GEDCOM 5.5.1''' format fluently (because it is the de facto format for genealogical data interchange), never depend on such a rudimentary format for archiving your research. GEDCOM cannot store all the intricacies found in Gramps data.'' Always backup with the more robust Gramps XML format.

[[File:Menubar-FamilyTrees-overview-FamilyTree-Loaded-example-60.png|thumb|right|450px|Menubar - {{man menu|"Family Trees > Make Backup..."}}]]

You will find a [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Backing_up_a_Family_Tree|{{Man menu|Make Backup...}}]] option in the {{Man menu|Family Trees}} menu of recent Gramps versions. Alternately, use [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Exporting_data|{{Man menu|Export...}}]] in the same menu but deselect the privacy and filtering options in the Exporter Assistant to avoid omission of any data.

See: [[How to make a backup]]

== See also ==
===Installing Gramps for Desktops===
Installation instructions specific to the different OSes are on the [[File:linux_32x32.png|link=Installing_Gramps_for_Linux_computers#Linux_distributions]], [[File:windows_32x32.png|link=Installing_Gramps_for_Windows_computers]],[[File:macos_200x200.png|32px|link=Installing_Gramps_for_macOS_computers]] and [[File:Bsd daemon.png|32px|link=BSD_platforms]] pages.

===GitHub Gramps for Desktops Releases===
:* [{{github_url}}/releases/v{{version}} {{version}} version]
:* [{{github_url}}/releases/ Archive of Gramps releases]
Wiki pages
* [[Previous releases of Gramps]]
* [[:Category:Versions|Versions on various platforms]]

===Installing Gramps Web for online collaboration===
[https://gramps-project.org/blog/web/ Gramps Web] is a frontend for a hosted instance of Gramps
* [https://www.grampsweb.org/Deployment/ Docker]
* [https://www.grampsweb.org/LetsEncrypt/ Let's Encrypt and Docker Compose]

[[Category:Documentation]]

Website report Themes

2025-09-19T11:04:49Z

ErickLedger: Add missing letter. vale Rob!

{{man note|Only Gramps 5.0 or greater}}

Website reports - CSS StyleSheet Themes

Narrated Website Report

Please place the css file in your User directories css directory <code>\gramps\css\</code> and select it from the reports {{man label|Stylesheet:}} option found on the [[Gramps_{{Version manual}}_Wiki_Manual_-_Reports_-_part_7#HTML_Options|HTML Options]] tab.

{| {{Prettytable}}
|-
! Theme Screen Shots
! Name
! Version
! Description
! Written for Gramps
! Contact
! Download
|-
| [[Image:ThemeTest.gif]]
| ThemeTest
| 1.0
| Testing CSS new (2009) layout, for low vision viewing
| 3.1
| [https://gramps-project.org/bugs/my_view_page.php Gramps Bugtracker]
| #{{bug|3173}} - Feature Request - Closed as [https://gramps-project.org/blog/2012/07/in-memory-of-rob-g-healey/ Rob Healey(1969–2012)] passed away.
|-
|}

[[Category:Plugins]]
[[Category:Reports]]