GenoPro Home
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 

GenoPro Support Forum


Home » GenoPro Help and Technical Support » Sales and Licensing Questions » Do GenoPro Licenses Affect Long-Term Project Portability?


Do GenoPro Licenses Affect Long-Term Project Portability?

Click to view RSS...
Author
genome
Posted Friday, January 30, 2026 - Post #47543
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 8 hours ago
Posts: 3,476, Visits: 27,020
Hi Jadon, I have not encountered similar licensing scenarios and I am not a member of the GenoPro Team but I do know that .gno files are simply zipped xml files. Unzip one and you will see a file Data.xml and it does not contain any embedded licencing flags or feature dependencies and so they are totally portable between different licence scenarios.

AFAIK a GenoPro licence simply allows you to save .gno files contains more than 25 objects. 

For any further clarification you could try emailing the author at GenoPro Support  ( supoort <at> genopro <dot> com )  

'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
jadongreen
Posted Wednesday, January 28, 2026 - Post #47538
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Forum Members

Last Login: Yesterday @ 10:00 PM
Posts: 1, Visits: 6
Hello,
My name is Jadon. I’ve been using GenoPro for some time in projects that involve large, multi-generation datasets with extensive notes, custom symbols, and cross-referenced relationships. GenoPro appealed to me because it scales much better than most genealogy tools once a project goes beyond a simple family tree.
I’m currently evaluating licensing options for a scenario that isn’t entirely straightforward and would appreciate some clarification.
If a project is created and actively maintained under an academic or site license, but later needs to be transferred to individuals who only hold standard personal licenses, how is license compliance handled at the file level? Specifically:
Are there any embedded license flags or feature dependencies in a .gno file that would prevent advanced structures, reports, or symbols from being edited under a personal license?
Does GenoPro enforce licensing only at the application level, or are there long-term restrictions tied to how and under which license a project was originally authored?
In a mixed-license environment (site + personal), is there a recommended workflow to avoid future licensing conflicts when ownership of a project changes?
I’m trying to plan ahead to ensure long-term portability of complex GenoPro projects without running into unexpected licensing limitations down the road.
Thanks for any insight from those who’ve dealt with similar setups or from the GenoPro team.
Geometry Dash

Tags:

Edited: Wednesday, January 28, 2026 by jadongreen


Similar Topics

Click to view RSS...
Expand / Collapse

Reading This Topic

Expand / Collapse


Powered By InstantForum.NET 2010-3-x © 2026
Execution: 0.000. 3 queries. Compression Enabled.