We import custom field data from a file you supply — matched to the correct posts and field keys — at scale. This imports exactly the data you provide; we don’t decide what the field values should be or design the underlying field structure they’re importing into.
Custom field bulk import from supplied file
Custom field data you supply, imported at scale into the correct existing fields.
- 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
- A file (spreadsheet or CSV) with the field data, matched to post identifiers
- Confirmation of the existing field structure the data should map into
- Confirmation of how to handle rows that don’t clearly match an existing post or field
This or something else?
| You have custom field data ready to import in bulk, matched to existing posts and fields | This fix covers it |
| You need the underlying field structure created first, not just data imported into it | Worth confirming — field group creation is a separate, prerequisite step if that doesn’t already exist |
| You want product descriptions specifically imported, not custom field data generally | Product description bulk update from supplied CSV, in the Content & Updates bucket |
| Your field data seems to have been lost, not something you’re importing fresh | Custom field data loss recovery, a different, diagnostic situation |
What we do
- Review your supplied file for formatting and post-matching accuracy
- Flag any rows that don’t clearly match an existing post or field
- Import the data into the correct fields for each matched post
- Verify a representative sample displays correctly on the live site
- Check that field types (repeaters, relationships) import correctly where applicable
- Provide a written summary of what was imported and what, if anything, was flagged
What is included
- Your supplied field data imported at scale into the correct fields
- Mismatched or ambiguous rows flagged before import
- Verification of a representative sample
- A written summary of the import
Not included
- Creating the underlying field group structure, if it doesn’t already exist — a separate, prerequisite fix
- Deciding what the field values should actually be — that’s your data to provide
- Fixing an underlying field configuration issue discovered during import
- Ongoing imports as you prepare additional data over time
Questions about this fix
What if my file references a field that doesn't exist yet?
We'd flag this specifically, since importing into a non-existent field isn't possible — creating the underlying field structure first is a separate, prerequisite step if that's genuinely needed.
Can this import repeater or relationship field data, not just simple text fields?
Yes, though these more complex field types need careful formatting in your supplied file to import correctly — we'd confirm the right format for your specific field types before starting.
Will this overwrite field data that's already set on some posts?
Only according to your stated preference — we'd confirm upfront whether the import should overwrite existing values or only fill in genuinely missing ones.
How do you match rows in my file to the correct posts?
Typically by a unique identifier (a post ID, SKU, or similar) that you include in your file — we'd confirm the matching method that fits your specific data before starting the import.
How large a file can this handle?
This scales well to a large number of rows — a bigger file just takes proportionally more careful verification of the matching and import.
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.