The Melbourne Marketing Brief / #002 / NEWS
Twilio Functions Classic migration window opens
Published by Ajay Dabhi · · AI-assisted reporting
Scheduled platform change · Account migration not independently verified
Twilio’s scheduled window for automatically moving active Functions Classic workloads to its newer Functions platform opens on 14 September 2026. The window runs through 26 October, according to the company’s deprecation announcement.
The schedule was announced on 13 August. The milestone today is the start of the migration window, rather than a newly announced product launch. Twilio says customers do not need to initiate the move.
The company’s cutoff for creating new Classic functions and assets was 13 September. Existing workloads can continue running, and existing code can still be edited and deployed during the transition. The planned transfer includes URLs, function and asset names, environment variables and deployed code.
This report checks the published schedule. It does not confirm that any particular Australian customer account has already migrated, or that a specific phone integration has passed testing.
Announced 13 August 2026. Source checked 14 September 2026.
ANALYSIS / BUSINESS CONTEXT
What this means for an Australian service business
For an owner, the useful first question is whether the business has a custom dependency at all. A phone-system provider or developer can inspect the configuration. Hearing that a business uses Twilio, an AI receptionist or Growthcenter does not by itself establish that Functions Classic is involved.
A custom function may sit between an incoming enquiry and the next action: routing a call, handling a webhook, creating a CRM record or triggering an SMS. Those are examples of possible implementations, not functions observed in a client account for this report.
A platform migration and an end-to-end customer test answer different questions. Even when code transfers automatically, the owner still needs to know whether the complete journey reaches the right person and records the enquiry correctly. An ordinary test call through the business’s actual routing rules is more useful than assuming a successful deployment proves the whole journey works.
Practical checks
- Ask the maintainer to identify any Functions Classic dependencies before commissioning migration work.
- Keep a secure copy of current code and record webhook URLs and environment-variable names. Keep secret values out of shared checklists.
- Test an inbound call, missed call, transfer, after-hours route and human fallback. If your system supports them, also check appointment capture and SMS confirmation.
- Record the expected result and who will investigate a failure. Use authorised test details so a test does not become a real customer booking or marketing enrolment.
These checks are recommendations, not additional requirements announced by the platform. The appropriate work depends on your actual configuration.
Publisher and editorial information
Ajay Dabhi publishes this report and also sells marketing and automation services. The commercial invitation above is separate from the sourced reporting. No client account test or direct interview is claimed in this report.
Research and writing use AI assistance. Original documents are linked so readers can check the facts. Read our ownership, sourcing and corrections policy or report a correction to Ajay.
More marketing and AI news →