CFTS Documentation

Onboarding Checklist

This checklist helps clients prepare for a new CFTS service, migration, or infrastructure deployment.

Not every item applies to every service. CFTS will confirm what is needed for the agreed scope.

Commercial and Account Details

  • confirm legal client name
  • confirm billing contact
  • confirm technical contact
  • confirm emergency or escalation contact if applicable
  • confirm quotation, service agreement, or order details
  • confirm preferred billing currency where applicable
  • confirm tax or purchase order requirements

Service Requirements

  • describe the workload or service being hosted
  • confirm expected users, locations, and usage pattern
  • confirm required hosting region or data location preference
  • confirm whether the service is shared, dedicated, virtualised, or custom
  • confirm expected storage, CPU, RAM, and bandwidth needs
  • confirm whether public IP addresses are required
  • confirm whether managed services are required

Access Requirements

  • identify who needs administrative access
  • confirm whether access should be IP-restricted
  • confirm MFA requirements
  • identify third-party vendors that may require access
  • agree how credentials will be exchanged securely
  • avoid sending passwords or private keys by normal e-mail

Domain and DNS

  • confirm domain ownership
  • identify current DNS provider
  • confirm who is authorised to make DNS changes
  • provide required DNS records
  • plan DNS TTL changes before migration where needed
  • confirm mail routing requirements
  • confirm whether CFTS will manage any DNS records

Data and Migration

  • identify source systems
  • estimate data volume
  • confirm acceptable migration window
  • identify any application freeze or content freeze needed
  • confirm database export requirements
  • confirm file transfer method
  • confirm rollback plan where appropriate
  • validate migrated data before go-live

Backup and Recovery

  • confirm whether backup services are included
  • define what must be backed up
  • define required retention
  • identify recovery priorities
  • confirm application consistency requirements
  • confirm whether independent client copies are required
  • plan a test restore where appropriate

Security and Compliance

  • identify whether personal data will be hosted
  • confirm whether CFTS is acting as Data Processor
  • review the Data Processing Addendum where applicable
  • identify access restrictions or audit requirements
  • identify encryption expectations
  • identify logging or retention expectations
  • disclose special regulatory or contractual obligations

Go-Live Readiness

  • confirm service is provisioned
  • confirm DNS or routing changes are ready
  • confirm monitoring expectations
  • confirm backups are configured where included
  • confirm client access works
  • confirm application health checks pass
  • confirm support contacts know how to raise issues
  • confirm any post-go-live observation period