About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Cutover timing chooses when the business can tolerate controlled risk while DNS, identity and application layers switch to hosting. Australian organisations weigh Friday night against Saturday morning, watch state-based public holidays, and align with who is actually on call — internal staff, managed hosting support, and application vendors in other time zones.
Material difference from published coverage: Business freeze windows and change blackouts before a migration cutover owns freeze and blackout policy — what changes are forbidden before cutover. Planning identity, DNS and application cutovers for hosted services sequences technical dependencies. Cutover runbook: replication lag, DNS TTL, validation gates and rollback owns runbook mechanics. Estimating initial data sync time before you promise a weekend cutover sizes replication duration. Hypercare: first 72 hours after a hosted migration covers post-go-live staffing. This article is the Australian timezone and support-coverage calendar overlay for choosing weekend versus weeknight — not freeze rules, sequencing steps or hypercare task lists.
Why it matters
A technically sound runbook still fails when payroll must still run on a public holiday, or when retail stores trade Sunday morning. Weeknight windows save calendar days but exhaust staff; weekend windows buy rollback time but compete with family and award or agreement overtime rules (not assumed here).
Hosting customers also inherit provider support hours. If cutover assumes 24×7 provider hands when the contract lists business-hours escalation, hypercare becomes a voicemail exercise.
How it works
Overlay three calendars before naming a window:
- Trading calendar — peak sales, month-end, EOFY, stocktake, clinical roster peaks.
- Australian public holidays by state and territory — staff may be interstate; Easter varies by year. Fair Work's public holidays guidance states that holidays differ by state or territory — check each jurisdiction's calendar for the cutover year; do not assume one national list covers every site.
- Support coverage — your IT, hosting provider, ISV, identity team, telco for WAN changes.
Questions to put to your provider (editorial): confirmed support hours during the proposed window; escalation path and response targets after hours; named contact reachable on the night (not a generic queue).
Window table (editorial opinion, not prescriptive scheduling):
| Window type | Typical AU fit (editorial) | Watch-outs |
|---|---|---|
| Thursday 22:00 Sydney – Friday 02:00 Sydney | B2B with quiet Friday morning | Fatigue; for each planned date, calculate the local time in each vendor zone (offsets change with Australian and US daylight saving) |
| Friday 22:00–Sat 06:00 | Offices closed Saturday | Check payroll and banking cutoffs for your organisation |
| Saturday 06:00–14:00 | Some offices closed; retail trading varies | Staff availability; award costs — many retailers trade Saturday |
| Sunday night | Preface Monday go-live | Monday is unforgiving if rollback slips |
Weeknight suits small databases and reversible DNS when Monday traffic is moderate and testers can work next day. Weekend suits longer replication catch-up, printer recabling, or branch visits.
Document business constraints in plain language — for example "no new invoices after 20:00 Friday" as a transaction freeze start, not a substitute for maximum downtime. Record separately: cutover start and end, latest acceptable restore time, and when the rollback decision was made or deferred.
What to choose and why
Choose weekend when physical office tasks, multi-site DNS TTL overlap, or dress-rehearsal fixes need daylight on Saturday without Monday revenue pressure.
Choose weeknight when automation is mature, rollback is practiced, user count is small, and support contracts include overnight response.
Choose avoid EOFY and major holiday stacks unless regulators mandate — editorial view: error cost can be asymmetric after a bad window.
Communicate Australian time zones explicitly in runbooks shared with offshore vendors. State the time zone and UTC offset for each location on the actual cutover date; daylight-saving rules and offsets vary.
Read next
Related articles you may want next.
- HostingBusiness freeze windows and change blackouts before a migration cutoverHow long to freeze configuration and data changes before cutover, who may approve an exception, and what the freeze is meant to protect — distinct from replication lag and DNS mechanics.Read article
- HostingHypercare in the first 72 hours after a hosted migrationWhat to monitor, how long to keep elevated support and war-room habits, and when to declare normal operations after cutover.Read article
- HostingEstimating initial data sync time before you promise a weekend cutoverHow to turn measured throughput, data size and change rate into an honest first-sync duration for migration planning — not egress billing or restore-drill throughput alone.Read article
Risks and limits
False quiet. Retail e-commerce may peak Sunday evening while offices are idle.
DNS caching. Mobile and ISP resolver behaviour affects cutover; timing interacts with Port forward works from the internet but not inside: NAT hairpin or split DNS — specific cache durations vary by network; do not assume a fixed global TTL.
Penalty and fatigue. Repeated weeknights without rotation cause procedural mistakes.
Not freeze policy. Deliberate code and data freezes are covered in Business freeze windows and change blackouts before a migration cutover.
Related: How it works.
Sources
- Fair Work — Public holidays — holidays differ by state and territory.
- Editorial: business change-window practice for Australian organisations; state calendars consulted annually.
- Linked NetLeverage articles above — freeze policy, sequencing, runbook, sync estimate, hypercare.
Learning notes
- Cutover timing is a trading and support decision, not only technical duration.
- Overlay AU state holidays and vendor time zones on one calendar.
- Weekends buy daylight for office tasks; weeknights save calendar days.
- Separate freeze starts from measured downtime and rollback decision times.
- Provider after-hours coverage must match the chosen window.
This article was originally published on .