Skip to content
Wayline Access StudioIndependent route planning

Field note · migration

Import only after the field map makes sense.

Current SecureCRT releases include a Text Import Wizard. The hard part is not producing rows—it is deciding which fields are authoritative and how operators will review the result.

Import itinerary

  1. Normalize hostname, protocol, port, username, folder, emulation and description fields.
  2. Choose an unambiguous session-name rule and decide how duplicates are handled.
  3. Test a small cross-section of session types and compare expected settings.
  4. Review navigation, ownership and exceptions with operators before broader rollout.

Acceptance table

CheckEvidence
CompletenessRequired fields present for every pilot row
IdentityNames and folders match the approved blueprint
SafetyNo secrets embedded in source data
RecoveryOriginal configuration remains recoverable