--- title: How Wix Saved 650 Developer-Days in One Quarter by... description: Wix built an internal Code Migration Platform to automate cross-team code migrations at scale — 50 migrations per year touching 6,000 repositories. The... canonical: https://daily.dev/posts/how-wix-saved-650-developer-days-in-one-quarter-by-automating-code-migrations-iwvhghcod twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How Wix Saved 650 Developer-Days in One Quarter by Automating Code Migrations | daily.dev og:description: Wix built an internal Code Migration Platform to automate cross-team code migrations at scale — 50 migrations per year touching 6,000 repositories. The... og:url: https://daily.dev/posts/how-wix-saved-650-developer-days-in-one-quarter-by-automating-code-migrations-iwvhghcod og:image: https://api.daily.dev/og/posts/iwVhghCoD.png og:image:alt: How Wix Saved 650 Developer-Days in One Quarter by Automating Code Migrations og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How Wix Saved 650 Developer-Days in One Quarter by Automating Code Migrations **[Wix Engineering](https://daily.dev/sources/wix_eng)** · 8 min read · 1 upvotes · 0 comments ## Summary Wix built an internal Code Migration Platform to automate cross-team code migrations at scale — 50 migrations per year touching 6,000 repositories. The platform uses a three-layer architecture: a migration dashboard for target discovery, an execution layer running AI code agents on Buildkite to open repos and create PRs automatically, and a database layer for tracking. A Prompt Bank stores versioned migration logic that improves over time based on manual adjustments made by service owners. Key merge-rate improvements came from clear ownership, rich PR context, and automerge for safe changes. Results: 650 developer-days saved in one quarter, with 88% of PRs merged without manual changes. Future plans include conversational migration via MCP and automatic build failure fixes. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can large organizations automate code migrations across thousands of repositories? One approach uses a three-layer platform: a dashboard where a migration owner identifies target repositories and paths, an execution layer where a code agent opens each repo, applies the change, and creates a pull request via Buildkite, and a tracking database that pulls PR statuses continuously from GitHub Actions. Prompts are version-controlled and refined based on manual edits service owners make after merging, so the same refined prompt automatically fixes newly discovered targets. _daily.dev surfaces engineering write-ups on scaling migrations for teams weighing automation investments._ ### What results has Wix reported from automating code migrations with AI agents? Wix reported saving 650 developer-days in a single quarter after deploying its Code Migration Platform, with 88% of generated pull requests merged without any manual changes and 60% of migrations fully merged within two weeks of PR creation. Roughly 25% of developer time across the organization had previously been spent on migrations across around 50 initiatives and 6,000 repositories touched annually. _track real-world automation outcomes like this on daily.dev when evaluating AI agents for engineering workflows._ ### Should I use an LLM-based agent or a deterministic script for automating code migrations? Use scripts for deterministic changes and reserve LLM-based code agents for cases requiring contextual judgment, since applying an agent to changes that don't need one adds complexity without added value. Wix Engineering's migration platform uses both approaches depending on the migration type, choosing the simplest tool that reliably produces a correct pull request. _developers deciding between scripts and AI agents for migrations can follow these trade-offs on daily.dev._ ## Similar posts on daily.dev - [From Co-Pilot to Full Automation: How Wix Is Embedding AI Agents Across an Engineering Org at Scale](https://daily.dev/posts/from-co-pilot-to-full-automation-how-wix-is-embedding-ai-agents-across-an-engineering-org-at-scale-3yjzklvp7) · Wix Engineering · 0 upvotes · 0 comments - [Building AI-Powered Migration Tools: Compressing 4 Sprints Into 3 Days](https://daily.dev/posts/building-ai-powered-migration-tools-compressing-4-sprints-into-3-days-vlj1z2ucz) · Salesforce Engineering · 2 upvotes · 0 comments - [The AI-native SDLC is paying off: 19% more PRs and 2–3 hours saved per developer per week](https://daily.dev/posts/the-ai-native-sdlc-is-paying-off-19-more-prs-and-2-3-hours-saved-per-developer-per-week-hii0tkbve) · Atlassian · 0 upvotes · 0 comments - [What 986 million code pushes say about the developer workflow in 2025](https://daily.dev/posts/what-986-million-code-pushes-say-about-the-developer-workflow-in-2025-4bpyjwlpr) · GitHub Blog · 4 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#automation](https://daily.dev/tags/automation), [#productivity](https://daily.dev/tags/productivity), [#platform-engineering](https://daily.dev/tags/platform-engineering) [View this post on daily.dev](https://daily.dev/posts/how-wix-saved-650-developer-days-in-one-quarter-by-automating-code-migrations-iwvhghcod) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How Wix Saved 650 Developer-Days in One Quarter by Automating Code Migrations","url":"https://daily.dev/posts/how-wix-saved-650-developer-days-in-one-quarter-by-automating-code-migrations-iwvhghcod","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-wix-saved-650-developer-days-in-one-quarter-by-automating-code-migrations-iwvhghcod"},"datePublished":"2026-07-22T14:19:53.756Z","dateModified":"2026-09-13T19:41:28.466Z","description":"Wix built an internal Code Migration Platform to automate cross-team code migrations at scale — 50 migrations per year touching 6,000 repositories. The...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3935d74b2fbeb7f9f777e290c1d10cd4?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3935d74b2fbeb7f9f777e290c1d10cd4?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Wix Engineering","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Wix Engineering","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/5a14a3f3d2a14128bcb9a084fb2ebadf","url":"https://daily.dev/sources/wix_eng"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-wix-saved-650-developer-days-in-one-quarter-by-automating-code-migrations-iwvhghcod","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,automation,productivity,platform-engineering","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Wix Engineering","item":"https://daily.dev/sources/wix_eng"},{"@type":"ListItem","position":3,"name":"How Wix Saved 650 Developer-Days in One Quarter by Automating Code Migrations"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/how-wix-saved-650-developer-days-in-one-quarter-by-automating-code-migrations-iwvhghcod#faq","mainEntity":[{"@type":"Question","name":"How can large organizations automate code migrations across thousands of repositories?","acceptedAnswer":{"@type":"Answer","text":"One approach uses a three-layer platform: a dashboard where a migration owner identifies target repositories and paths, an execution layer where a code agent opens each repo, applies the change, and creates a pull request via Buildkite, and a tracking database that pulls PR statuses continuously from GitHub Actions. Prompts are version-controlled and refined based on manual edits service owners make after merging, so the same refined prompt automatically fixes newly discovered targets. daily.dev surfaces engineering write-ups on scaling migrations for teams weighing automation investments."}},{"@type":"Question","name":"What results has Wix reported from automating code migrations with AI agents?","acceptedAnswer":{"@type":"Answer","text":"Wix reported saving 650 developer-days in a single quarter after deploying its Code Migration Platform, with 88% of generated pull requests merged without any manual changes and 60% of migrations fully merged within two weeks of PR creation. Roughly 25% of developer time across the organization had previously been spent on migrations across around 50 initiatives and 6,000 repositories touched annually. track real-world automation outcomes like this on daily.dev when evaluating AI agents for engineering workflows."}},{"@type":"Question","name":"Should I use an LLM-based agent or a deterministic script for automating code migrations?","acceptedAnswer":{"@type":"Answer","text":"Use scripts for deterministic changes and reserve LLM-based code agents for cases requiring contextual judgment, since applying an agent to changes that don't need one adds complexity without added value. Wix Engineering's migration platform uses both approaches depending on the migration type, choosing the simplest tool that reliably produces a correct pull request. developers deciding between scripts and AI agents for migrations can follow these trade-offs on daily.dev."}}]} ```