Migrating from ClearSCADA to Geo SCADA Expert: What Changes and What Breaks

Quick Answer

Schneider Electric rebranded ClearSCADA as Geo SCADA Expert starting with version 2017. Migration involves database compatibility verification, addressing deprecated features like the legacy web client, updated licensing requirements, and testing for breaking changes in scripting APIs and driver configurations. Careful planning prevents common migration pitfalls.

Why Schneider Rebranded ClearSCADA

ClearSCADA was originally developed by Control Microsystems, which was acquired by Schneider Electric. The rebranding to Geo SCADA Expert aligns the product with Schneider's broader EcoStruxure portfolio and reflects the platform's evolution from a traditional SCADA system to a geographically distributed infrastructure management platform. The core architecture remains the same — SQL Server database, ViewX thick client, DNP3/Modbus communication drivers — but the product name, licensing model, and some features changed.

Version Compatibility

Migration paths depend on your current ClearSCADA version:

• ClearSCADA 2015 R2 and later: Direct upgrade to Geo SCADA Expert is supported. Database migration is handled by the installer.
• ClearSCADA 2013 R2 to 2015 R1: Requires intermediate upgrade to 2015 R2 before migrating to Geo SCADA Expert.
• ClearSCADA 2010 and earlier: Requires a staged migration through multiple intermediate versions. Consider a fresh installation with database export/import for these legacy versions.

Always check the Schneider Electric release notes for your specific target version, as supported upgrade paths may change between releases.

Breaking Changes to Plan For

Deprecated Features

Several ClearSCADA features were deprecated or removed in Geo SCADA Expert versions:

• Legacy web client: The original ClearSCADA web client was replaced by WebX (later renamed Virtual ViewX). If your organization uses the legacy web interface, users will need to transition to the new client.
• OPC DA server: While still supported in some versions, Schneider encourages migration to OPC UA. New integrations should use OPC UA; existing OPC DA connections should be migrated as part of the upgrade planning.
• Specific driver versions: Some older communication driver versions may not be compatible with newer Geo SCADA releases. Review the driver compatibility matrix for your specific RTU and PLC equipment.

API and Scripting Changes

The Geo SCADA scripting environment (VBScript-based) has undergone changes across major versions. Scripts that reference specific object classes, method signatures, or database schema elements may require updates. Common issues include renamed properties, changed method parameters, and altered event handler interfaces. Test all custom scripts in a staging environment before production migration.

Licensing Model

Geo SCADA Expert uses a different licensing structure than legacy ClearSCADA versions. Tag counts, client seat licenses, and communication driver licenses may be structured differently. Confirm your new license entitlements with Schneider Electric before beginning the migration to avoid discovering licensing gaps during the upgrade.

Database Migration Steps

The standard database migration process for a supported upgrade path:

• Step 1: Take a verified, tested backup of the current ClearSCADA database.
• Step 2: Document current server configuration — communication drivers, channel settings, user accounts, alarm configurations, report definitions.
• Step 3: Install Geo SCADA Expert on a test server and restore the backup to validate the migration path.
• Step 4: On the test server, verify: client connectivity, communication to a subset of field devices, historian data access, alarm functionality, report generation, and any custom scripts.
• Step 5: Plan the production migration window with documented rollback procedures. The rollback plan must include the ability to revert to the previous ClearSCADA version using the pre-migration backup.
• Step 6: Execute the production migration during a planned maintenance window. Verify all functionality before closing the maintenance window.

Testing Strategy for Migrated Configurations

A thorough post-migration test plan covers:

• ViewX client connectivity from all client workstations
• WebX/Virtual ViewX access through all supported browsers
• Communication to every remote site (poll each outstation and verify data flow)
• Alarm generation and notification (trigger a test alarm and verify the full notification chain)
• Historian recording and retrieval (verify trends show current data and historical data survived the migration)
• Report generation (run all scheduled reports and verify output)
• Custom script execution (test every custom script)
• Mirror server synchronization (if applicable)
• User authentication and role-based access

Common Pitfalls from Real Migrations

Based on experience with multiple ClearSCADA-to-Geo-SCADA migrations:

• Insufficient test time: Operators underestimate the testing required and rush production migration. Plan twice as much test time as you think you need.
• Driver incompatibility: A specific RTU model's communication driver requires a firmware update that wasn't identified during planning. Audit all field device firmware before migration.
• Custom script failures: Scripts that worked for years fail silently after migration due to changed API behavior. Test scripts with actual data, not just syntax validation.
• Rollback untested: The rollback plan was documented but never tested. During a failed migration at 2 AM, untested rollback procedures add hours to the outage.

When to Hire Expert Support

Consider engaging managed Geo SCADA support for migrations when:

• You're migrating from ClearSCADA 2013 or earlier (multi-step migration)
• Your deployment includes more than 50 remote sites
• You have extensive custom scripting
• You use OPC DA integrations that need to migrate to OPC UA
• You lack a test environment for pre-migration validation

Contact NFM Consulting for a migration assessment to identify risks, estimate effort, and plan a successful transition from ClearSCADA to Geo SCADA Expert.