Zendesk legacy custom objects are gone. Here is the way out.

If you read one sentence and close the tab, read this one: Zendesk never shipped an automated migration for legacy custom objects. The developer documentation describes a CSV export tool in Admin Center and a manual path you walk yourself. Anyone who told you the tool handled it had not opened the page.

What happened, and when

Two dates matter. From January 15, 2026, no new legacy custom objects could be created. On July 27, 2026, they were removed. The gap between those dates was the migration window.

That window has now closed, which changes the question from how do I prepare to what do I do now.

The part almost nobody mentions

Zendesk's own removal announcement includes a request form for a one-time six-month extension. Customers who filed it can hold legacy objects until roughly January 2027.

So if you are reading this and your instance still works, you are not imagining it. Either someone on your team filed for the extension, or you are not as far into the problem as you feared. Check before you panic, and check before you pay anyone to fix it.

Why this catches teams out

Legacy objects rarely live alone. They get referenced by ticket fields, triggers, automations, macros, views and Explore reports built by admins who left two reorganisations ago. Nobody inventories that web until something stops resolving.

In plain terms: the data is the easy part. Knowing what reads the data is the hard part.

Inventory before you export

• Ticket forms and fields that show object values to agents or customers.
• Triggers and automations whose conditions test an object attribute.
• Views and macros that filter or template from object data.
• Explore reports and dashboards built on those attributes, including scheduled deliveries somebody in finance quietly relies on.
• Anything outside Zendesk calling the API for those records.

Then the move itself

Export to CSV from Admin Center. The tool batches at 20,000 rows per file. Rebuild the object structure using the current custom objects, load the records through the API or the data importer, then repoint every reference you inventoried. Finally, compare counts against your export rather than trusting a success message.

If your project touches legacy objects, treat it as its own workstream with its own sequence. It is not a line item inside a data move, and pricing it as one is how migrations turn into arguments.

Verified against

• Zendesk announcement, removal of legacy custom objects, including the six-month extension request form.
• Zendesk developer docs, migrating legacy custom objects: no automated process.
• Zendesk developer docs, exporting legacy custom objects tool.

Checked against Zendesk's own documentation on August 6, 2026.