{"id":92962,"date":"2026-09-09T03:19:23","date_gmt":"2026-09-09T03:19:23","guid":{"rendered":"https:\/\/gaeatech.com\/knowledge-center\/?p=92962"},"modified":"2026-09-09T03:19:24","modified_gmt":"2026-09-09T03:19:24","slug":"from-gint-to-winlog-and-gaeasynergy-a-practical-migration-plan","status":"publish","type":"post","link":"https:\/\/gaeatech.com\/knowledge-center\/from-gint-to-winlog-and-gaeasynergy-a-practical-migration-plan\/","title":{"rendered":"From gINT to WinLoG and GaeaSynergy: A Practical Migration Plan"},"content":{"rendered":"

Replacing a long-used borehole data system is not simply a file-conversion exercise. Organizations must preserve historical records, reproduce essential reports and establish a supported workflow for future projects. A controlled migration to WinLoG<\/a> and, where appropriate, GaeaSynergy<\/a> should be planned around data, outputs, users and acceptance criteria.<\/p>\n

1. Inventory the current environment<\/h2>\n

Begin by identifying databases, projects, report templates, libraries, coordinate systems, user-defined fields, attachments and integrations. Classify each item as active, historical, duplicated or no longer required. This avoids spending migration effort on information that has no continuing business value.<\/p>\n

2. Define the future workflow<\/h2>\n

WinLoG focuses on configurable borehole and well logs, structured entry, professional output and validation. GaeaSynergy can extend that workflow with centralized project databases, dashboards, GIS, documents and integrated visualization. Determine which users need log production only and which require broader project access.<\/p>\n

3. Map data deliberately<\/h2>\n

Create a mapping document for borehole headers, lithology, samples, tests, groundwater observations, well construction, coordinates and custom fields. Record transformations, units, controlled terminology and the treatment of missing or ambiguous values. Never treat an apparently successful import as proof that the meaning of the data was preserved.<\/p>\n

4. Rebuild the outputs that matter<\/h2>\n

Prioritize frequently used and contractually important log formats. Configure WinLoG templates using representative examples, including long descriptions, complex well construction, core intervals and company branding. Retire redundant variants instead of reproducing every historical layout.<\/p>\n

5. Run a representative pilot<\/h2>\n

Select projects that cover the difficult cases, not only the cleanest database. Compare record counts, depths, intervals, units, sample identifiers and printed outputs. Use WinLoG Validation and QA\/QC<\/a> to identify completeness and consistency issues that may have existed before migration.<\/p>\n

6. Approve, roll out and retain evidence<\/h2>\n

Document acceptance results, exceptions, training and responsibilities. Keep protected source archives for the required retention period, and use staged rollout so teams can receive support as they adopt the new workflow.<\/p>\n

Migration planning checklist<\/h2>\n