Terms of Service

Ditchplugins, Inc. ("Ditchplugins", "we", "us") is a Delaware corporation that makes Ditchplugins Migrate, a product that copies a publicly available website onto Astro. These terms govern your use of ditchplugins.com and of the product. By creating an account or buying credits, you agree to them.

If you are agreeing on behalf of a company, you confirm you have the authority to bind it.

Migrate reads your existing, publicly available website and rebuilds it in Astro: same design, same content, your technical SEO (metadata, canonicals, hreflang, structured data, internal links) preserved, and a redirect for every page you leave behind. It works only from what is live; it never asks for your CMS credentials.

It is built for marketing and content sites. E-commerce, and sites with logins, registration, user accounts, membership areas, or a complex backend are out of scope — the free analysis tells you before you buy anything.

Integrations (forms, chat, analytics) are rewired, not copied: the migrated site calls the same services your current site does. Where an integration depends on a custom backend, we don't guarantee it, and the analysis says so.

The analysis and the homepage preview are free and need no card. The preview exists so you can judge the result before paying — it is served from our servers and is not a deliverable. Until you buy credits and migrate the page, the preview and its code remain our property, and you may not copy, publish, or reuse it. If you decide not to proceed, no charge, no hard feelings — and no rights to the preview.

You buy credits in packs, at the prices shown on the site when you buy. A migration spends credits per page, by the page's measured complexity, plus a flat amount for integrations; the exact total is shown before you confirm, and credits are only used once you pick pages and start. Credits never expire and there is no subscription. Prices exclude applicable taxes.

Because the free preview lets you judge the result before committing, a migration cannot be cancelled for a refund once it has started, and credits already spent are not refunded. The exceptions are on us: if a page fails our match gate, its credits come back to your balance, and if we fail to deliver a migration at all, we refund the credits it used.

When a migration passes the proof, you connect your GitHub account through GitHub OAuth and, with your permission, we create a private repository under your account and push the migrated site to it. From that moment the code is yours: we assign to you all rights in the code generated for your migration, to host, change, and control as you like. Your own content and assets were always yours.

We keep no copy of the repository. We do keep the proof reports and the record of what was migrated, so a re-run can charge you only for the pages that changed. You can deploy in one click to Cloudflare or to any host; pointing your domain at the new site is the one step we do not do for you, and your current site stays untouched until you do.

We may list your site as one migrated with Ditchplugins Migrate (a link, before/after metrics). If you would rather we didn't, tell us and we won't.

Open-source components (Astro itself, libraries) remain under their own licenses.

Migrate is self-serve, and no support is bundled with a credit pack. What every migration does include: the proof, with every check open for you to inspect; a "Send to my developer" button on each technical step, with exact instructions; and a real person at hello@ditchplugins.com who answers.

A product warranty for self-serve migrations is still being decided; until it is published here, the warranties in section 09 are what applies.

You need an account to use the product. Keep your sign-in details to yourself, and tell us if you think someone else has used your account; you are responsible for what is done under it. We may suspend or close an account used to migrate sites you have no rights to, or that involve unlawful content.

You confirm that you own or have the rights to the website, content, and assets you ask us to migrate, and that nothing in them is unlawful or infringes anyone else's rights. You are responsible for reviewing the proof before connecting GitHub, and for your site's content, legal compliance, and operation once it is in your repository.

Each of us stands behind what we bring to the migration. If a third party brings a claim against one of us because of the other's contribution, that other covers the reasonable legal costs and any damages: you cover us for claims that the content or assets you asked us to migrate infringe someone's rights or break the law, and we cover you for claims that the code we generated infringes someone else's intellectual property. Neither of us is on the hook for a claim caused by the other's own changes to the site after delivery.

We promise to run the product with reasonable skill and care, and every page we deliver has passed the checks described on the site. Beyond that, the site and the product are provided "as is": we do not guarantee specific search rankings, Core Web Vitals scores, traffic, or business results — the web changes, and much of it is outside our control. Certain website setups (heavy embeds, third-party scripts, large media) may stand in the way of perfect Core Web Vitals scores on the migrated site too.

To the fullest extent the law allows, our total liability for anything arising out of a migration is capped at the amount you paid for the credits it used, and neither of us is liable to the other for indirect or consequential losses (lost profits, lost data, lost business). Nothing in these terms excludes liability that cannot legally be excluded.

You can close your account at any time; unused credits are lost when you do, so spend them first. Either of us can end our relationship by written notice if the other materially breaches these terms and does not fix it within 14 days. We may decline or discontinue a migration that turns out to involve unlawful content or misrepresented rights; credits for pages not migrated come back to your balance.

These terms are governed by the laws of the State of Delaware, USA, without regard to its conflict-of-law rules. Any dispute that we cannot resolve between us will be brought exclusively in the state or federal courts located in Delaware, and both of us consent to their jurisdiction. But please — email us first. Almost everything can be sorted out with a conversation.

If we change these terms, we'll update the date at the top. Changes do not apply retroactively to a migration already in progress — the terms in force when you started it are the ones that govern it. For significant changes affecting an account, we'll email you directly.