● Deploy anywhereGet API key

Home / Add-ons / Migration Service

Migration service — move providers without breaking production

A compatibility review, a shadow-traffic run and a quality diff before cutover, so you change the base URL with evidence instead of hope.

$250

one-time · two or more scheduled sessions · no renewal

Delivered by a Plugsky engineer. Scope, price and refund terms are confirmed in writing before anything is booked.

Who it is for

Teams moving from another provider and unwilling to discover the differences in production.

The problem it removes

What you get

How to use it

1. Scope call

We list what your code sends today and what must keep working.

2. Shadow run

Mirrored traffic for a fixed window; you get the diff, not an opinion.

3. Cutover

You switch with a rollback step written down.

What the compatibility review checks

Two providers can both claim an OpenAI-compatible endpoint and still differ in nine places that break code. The review lists each one against your actual request shape rather than against the provider's documentation, because documentation describes what the API accepts, not what your code sends.

Compatibility surface reviewed before any traffic moves.
SurfaceWhat usually differsWhat the review records
Chat completionsMessage roles accepted, system-message handlingWhether every message your code sends is accepted unchanged
StreamingChunk shape, keep-alive behaviour, termination signalWhere your parser would need a branch
Tool callsArgument encoding, parallel calls, finish reasonsThe exact shape of a tool response on each side
JSON modeSchema enforcement, malformed-output behaviourWhether invalid JSON is retried or returned
Token countingTokenizer differences change prompt costMeasured token delta on your own samples
Error codesStatus codes for the same failureA mapping so retry logic stops guessing
Rate-limit headersNames, units, reset semanticsThe header your client should read
EmbeddingsDimensions and normalisationWhether an existing index must be rebuilt
Context limitsMaximum input and outputWhich prompts must be shortened before cutover

How shadow traffic works without production access

Shadow traffic does not require credentials. You export a sample of representative requests — 200 to 2,000, redacted — and we replay them against the new endpoint with the same parameters. The two response sets are then compared offline. Your production system is never involved, and no customer data leaves your environment unless you choose to send it.

The sample matters more than the size. A thousand requests from one customer proves one customer's workload works. Two hundred requests spread across your input classes — short and long, structured and free-form, tool-using and plain — finds the differences that matter. We ask for the spread, not the volume.

Replay is run at a fixed temperature where the parameter is supported, because comparing outputs sampled at random measures noise. Where determinism is not available, each case is run three times and the comparison uses the distribution rather than a single pair.

What the shadow run needs from you

Three things, none of them credentials. A request export in JSONL with one request object per line, a note on which fields are sensitive so they can be redacted before they leave your environment, and a list of the input classes you consider important. The export is usually produced by a logging middleware you already have; if you do not log requests today, the review includes a short patch that turns logging on for a sample window and off again afterwards.

Redaction happens on your side. Names, account numbers and free text can all be replaced with fixed tokens without changing the shape of the request, and shape is what the compatibility review measures. If a redacted request behaves differently from the original, that is itself a finding about how much the model depends on the content.

What the quality diff report contains

Reading the diff without overreacting

Not every difference is a defect. The report separates three kinds, and only the third should stop a cutover.

How the report classifies a disagreement.
KindExampleVerdict
CosmeticDifferent whitespace, a reordered JSON key, a different opening phraseIgnore if your parser is stable
StructuralTool arguments as a string instead of an object; a missing finish reasonPatch the parser before cutover
SemanticA refusal where the old model answered; a truncated answer; a wrong extractionDo not cut over for that input class

Most failed migrations are structural differences discovered in production because the evaluation only compared prose. The report exists to move that discovery into a spreadsheet.

The rollback plan

Rollback is written before cutover, not after something goes wrong. It has five steps and a named owner for each.

When migration is not worth it

If your usage sits comfortably inside your current plan, the saving from a cheaper per-token price is usually smaller than the engineering time the migration consumes. The same is true if your application depends on a feature the new provider implements differently — a migration that requires rewriting your tool-call layer is a project, not a switch.

The review will say this plainly when the numbers point that way. A $250 report that recommends staying is a successful engagement; the alternative is discovering the same thing after two weeks of engineering.

Timeline

Typical schedule for a single-application migration.
DayActivityOutput
1Scope call and request exportWritten scope, sample received
2–3Compatibility reviewSurface-by-surface findings
4–6Shadow replay and comparisonRaw comparison data
7–8Report writingQuality diff, rollback plan
9–14Your cutover windowPost-cutover notes for one week

What we do not do

Questions

What does it cost?

$250 one-time. The shadow run is included.

How long does it take?

One to two weeks depending on how many models and features you use.

Do you need production access?

No. We need representative requests, not credentials.

What if quality is worse?

The diff shows where. You can stop before cutover; the report is still yours.

Does it include code changes?

We provide the patch guidance; your team applies it.

Sources

Guided Onboarding

Two live sessions with a Plugsky engineer: keys, first integration, an evaluation set and a cost baseline. Delivered in one week.

$150/one-time · Read more →

Compliance Audit

A scoped technical assessment: what applies to you, what is missing, and the order to fix it. A report and an evidence appendix, not legal advice.

$500/one-time · Read more →

Start with an intake form

One intake form, then two sessions in the same week. Paid once through Stripe; nothing renews.

Book the engagementCompare add-ons