u/Big-Reporter7078

I want to share what I been building and why, not to promote but because this community helped me a lot and I think the story is useful.

I work with a lot of B2B SaaS companies and kept seeing same thing. they use Zendesk for 3-4 years, build up all this support history, custom objects, field data. then one day they want to leave Zendesk (because price doubled), or they want to use the data to train an AI, or they want to put it in their warehouse to do proper analytics.

and then they realize: they can't get their data out cleanly.

Zendesk native export is flat CSV. no custom objects. no ticket events. no relational structure. attachments are completely separate. if you have custom objects (which every serious Zendesk customer does) you are basically stuck.

so engineers write scripts. takes a week. hits rate limits. breaks. gets fixed. breaks again. I did this 3 times for different companies and each time it was the same painful week.

I build Evicta (evicta.dev) to solve this. one-click extraction, handles the API complexity, uses Claude to map custom fields to whatever schema you want, outputs clean archive. $500 flat, no subscription.

what I learned building this:

the hardest part was not the technical side. it was convincing myself that "boring infrastructure problem" is actually a real business. no viral potential. no beautiful UI. not going to be on TechCrunch. but it solves a real, expensive problem for a specific type of customer and that is enough.

I am still early — looking for the first few customers who tried to do this manually and can tell me what I got wrong. if you want to try it there is free tier, 100 records no credit card, just to see how it works. if you work with Zendesk data I would genuinely love to hear your experience.

I want to share what I been building and why, not to promote but because this community helped me a lot and I think the story is useful.

I work with a lot of B2B SaaS companies and kept seeing same thing. they use Zendesk for 3-4 years, build up all this support history, custom objects, field data. then one day they want to leave Zendesk (because price doubled), or they want to use the data to train an AI, or they want to put it in their warehouse to do proper analytics.

and then they realize: they can't get their data out cleanly.

Zendesk native export is flat CSV. no custom objects. no ticket events. no relational structure. attachments are completely separate. if you have custom objects (which every serious Zendesk customer does) you are basically stuck.

so engineers write scripts. takes a week. hits rate limits. breaks. gets fixed. breaks again. I did this 3 times for different companies and each time it was the same painful week.

I build Evicta (evicta.dev) to solve this. one-click extraction, handles the API complexity, uses Claude to map custom fields to whatever schema you want, outputs clean archive. $500 flat, no subscription.

what I learned building this:

the hardest part was not the technical side. it was convincing myself that "boring infrastructure problem" is actually a real business. no viral potential. no beautiful UI. not going to be on TechCrunch. but it solves a real, expensive problem for a specific type of customer and that is enough.

I am still early — looking for the first few customers who tried to do this manually and can tell me what I got wrong. if you want to try it there is free tier, 100 records no credit card, just to see how it works. if you work with Zendesk data I would genuinely love to hear your experience.

I want to share what I been building and why, not to promote but because this community helped me a lot and I think the story is useful.

I work with a lot of B2B SaaS companies and kept seeing same thing. they use Zendesk for 3-4 years, build up all this support history, custom objects, field data. then one day they want to leave Zendesk (because price doubled), or they want to use the data to train an AI, or they want to put it in their warehouse to do proper analytics.

and then they realize: they can't get their data out cleanly.

Zendesk native export is flat CSV. no custom objects. no ticket events. no relational structure. attachments are completely separate. if you have custom objects (which every serious Zendesk customer does) you are basically stuck.

so engineers write scripts. takes a week. hits rate limits. breaks. gets fixed. breaks again. I did this 3 times for different companies and each time it was the same painful week.

I build Evicta (evicta.dev) to solve this. one-click extraction, handles the API complexity, uses Claude to map custom fields to whatever schema you want, outputs clean archive. $500 flat, no subscription.

what I learned building this:

the hardest part was not the technical side. it was convincing myself that "boring infrastructure problem" is actually a real business. no viral potential. no beautiful UI. not going to be on TechCrunch. but it solves a real, expensive problem for a specific type of customer and that is enough.

I am still early — looking for the first few customers who tried to do this manually and can tell me what I got wrong. if you want to try it there is free tier, 100 records no credit card, just to see how it works. if you work with Zendesk data I would genuinely love to hear your experience.

wanted to share my validation process because I think I did it in a decent way and maybe useful for others here.

the idea: one-click tool that extracts all Zendesk data (including custom objects) and maps it to a clean schema using AI. target customer is CTO who is canceling Zendesk, or ML engineer who needs ticket history for training data.

how I validated:

before I wrote any code I posted on r/Zendesk asking how people handle relational data exports for AI training. not mentioning any product, just asking the question. got real responses from real people describing exactly the pain I thought existed. that was enough for me to start building.

then I mapped out 3 types of buyers: companies leaving Zendesk (one-time export), AI teams that need training data, RevOps teams doing warehouse backfill. all three have same problem, different urgency.

why $500 flat:

I hate subscriptions for tools I use once. and this is almost always a one-time thing — you leave Zendesk, you get your data, done. $500 is below "need approval" budget for most CTOs. no ongoing cost, no surprise bills.

also there is free tier — 100 records, no credit card. so you can see exactly what the output looks like before deciding if it's worth paying. I think that's important for a tool like this where the output format matters a lot.

current status:

just launched, evicta.dev, looking for first paying customers and honest feedback. if you have Zendesk and ever tried to export your data you know the pain. would love to hear if the pricing makes sense or if I'm wrong about the one-time model.

https://reddit.com/link/1sxstop/video/uvuwaxj5gvxg1/player

so I kept running into the same problem. companies using Zendesk for years and when they want to either switch tool, use their data for AI training, or just put it in a warehouse — they realize the native export is basically useless. flat CSVs, no custom objects, no ticket events, attachments completely separate.

I write this script like 3 times for different projects and every time it was same pain — rate limits, pagination, custom object joins that break, field mapping that is different for every account.

so I just build Evicta (evicta.dev). you connect your Zendesk, define what schema you want the data in, it pulls everything — tickets, events, custom objects, users, orgs — and gives you a clean downloadable archive. uses Claude to map your custom fields to whatever structure you need.

pricing is $500 one time, no subscription. I choose this because the use case is usually one-off — you leave Zendesk, you train your AI, you do your backfill. not something you need every month.

there is also free tier — 100 records, no credit card needed. just connect your Zendesk and see what actually comes out. good way to check if the schema looks right for your use case before paying anything.

still early, would love brutal feedback especially from people who tried to do this manually before. what would make you actually use something like this?

https://reddit.com/link/1sxl7mi/video/vu6qor09otxg1/player