What JSON property moving is
Relocate values and remove their original properties
Property moving reads an exact source path, writes the same JSON value to a safe destination, and removes the original property. Records stay ordered and conflicts are blocked before output is created.
Schema evolution
Relocate fields as a data model changes
Move customerId to account.id or reorganize flat properties into intentional nested groups. The resulting sample data can represent a new schema without a custom script.
API migration
Prepare payloads for a new integration contract
Relocate identifiers, statuses, or contact details when a new API version expects different paths. Missing sources are skipped and counted; existing destinations are never overwritten.
Payload restructuring
Group related values without automatic transformations
Move exact properties into nested destinations before testing, documentation, or import. UtilityDock performs only the mappings you define and never guesses at restructuring.
Examples
Move exact source paths to intentional destinations
| Source property | Destination property | Use |
|---|---|---|
id | legacyId | Adopt a replacement field name |
profile.email | contact.primaryEmail | Restructure an API payload |
status | metadata.state | Group related metadata |
Modification utilities
Continue with related UtilityDock JSON workflows
FAQ
Questions about moving JSON properties
Does UtilityDock upload or store my JSON?
No. Your files never leave your computer. Validation, field discovery, property moving, conflict detection, preview, copying, and download creation all happen locally inside your browser.
What JSON shape can I use?
Version 1 accepts a non-empty array of JSON objects at the document root.
Can I move more than one property?
Yes. Enter a destination for each detected source property you want to move, then apply all mappings together.
Can a destination use a nested path?
Yes. Dot paths can create nested objects, and indexed array paths can target compatible existing or newly created array containers.
What happens when a destination already exists?
UtilityDock blocks the operation and identifies the affected array item. Existing destination values are never overwritten.
What happens when a source property is missing?
That mapping is skipped for the affected record. The summary reports how many missing source values were skipped.
How is moving different from copying?
Moving writes the value to its safe destination and removes the original property. JSON Property Copier keeps the original property.
Can moves be conditional?
No. Version 1 uses exact source and destination paths. It does not support expressions, conditions, regular expressions, automatic restructuring, or APIs.