Sometimes you don’t want a full staging-to-live push, with everything that implies about conflicts and overwrites — you just want specific new content (a set of pages, a product catalogue update) pulled from staging into live, leaving everything else on both sides exactly as it is.
Content-only merge from staging
Specific content pulled from staging into live, without touching anything else on either side.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Confirmation of exactly what content should be merged (specific pages, posts, products, or data types)
- Access to both the staging and live environments
- Confirmation of what should happen if the same content exists differently in both places
This or something else?
| You want specific content merged from staging to live, without a full site push | This fix covers it |
| You want everything from staging pushed to live, with conflicts resolved | Staging-to-live push with conflict resolution, the broader version |
| You don’t have a staging environment set up yet to merge from | Staging environment creation & sync |
| You want to restore live from a backup entirely, not merge specific content | Restore from backup – single site |
What we do
- Confirm precisely which content should be merged from staging
- Identify anything on live that could conflict with the specified content
- Perform a targeted, careful merge of only the specified content
- Verify the merged content displays and functions correctly on live
- Confirm nothing unrelated on live was affected by the merge
- Provide a written summary of exactly what was merged
What is included
- A targeted merge of exactly the specified content
- Verification the merge didn’t affect unrelated live content
- A written summary of what was merged
- The pre-merge backup, kept for 30 days
Not included
- A full staging-to-live push of everything, a separate, broader fix
- Creating the staging environment itself, if not already set up
- Resolving conflicts in content beyond what was specified for merging
- Ongoing, repeated merges as a standing service
Questions about this fix
How is this different from a full staging-to-live push?
A full push brings everything from staging to live, accounting for conflicts across the whole site; this is a narrower, more surgical merge of only the specific content you specify, leaving everything else untouched.
What if the content I want merged conflicts with something already on live?
We confirm with you upfront how to handle that specific case rather than making an assumption, since a content-only merge is meant to be precise and deliberate, not automatic.
Can I request multiple, separate content-only merges over time?
Yes, this can be done as a repeated, targeted process each time you have new content ready in staging, rather than needing a full push every time.
Will this affect anything else on my live site?
No, that's the specific point of this fix — only the content you specify is touched, with everything else on live left exactly as it was.
Is this cheaper or faster than a full push?
It's generally more contained in scope, since it doesn't require reconciling the entire site, though the actual complexity depends on how much content you're merging and how it interacts with what's already live.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.