Illustration of a project migration scenario, AI-generated

Define the scope of authorization for data and access

Confirm permission to use project documents, historical data, device protocols, and interfaces. Prioritize export files or authorized interfaces provided by the original platform, and do not obtain data through unauthorized means.

More Than Historical Curves Are Migrated

Project hierarchy, measurement items and points, initial values, coordinates, units, instrument scale factors, device ownership, warning thresholds, and reporting conventions all need to be checked. Attachments, response records, and historical rules may need to be organized separately.

Start with a small sample, then scale up

Select representative monitoring items and a segment of historical data, and compare quantities, timestamps, cumulative values, rates of change, and missing data. After validation, import the data in batches while retaining the original files and mapping records.

Schedule the switch after parallel validation

Eligible devices can first run parallel validation of the new platform to verify reporting stability, alert notifications, and report results. The switching window, rollback path, and responsibilities must be clearly defined; devices that cannot run in parallel should have a separate integration testing plan.

The migration experience can start with a set of measurement points. Complete the validation first, then decide whether to switch over fully.
← Back to Knowledge & Insights