Developer & data · focused workspace

JSON Field Migration Runner

Rebuild JSON records with a declarative field map, nested destination paths, defaults and an audit of missing source values.

Migration auditEditable projectsLocal processing

Source → inspect → export

Preparing the worked example…

Your source & settings

Settings & options
Open your media file

Files stay in your browser. Try the built-in sample first.

Source text is limited to 1.5 million characters per editor; imported text files are limited to 1.5 MB.

Inspect your result

PREVIEW & EXPORT

Know what changed

Dot paths address object fields only; literal dots in keys cannot be addressed. Output is rebuilt from mapping rules. Overlapping destination paths are rejected.

    Choose another output above or open Export files.

    Explore the example

    Rebuild JSON records with a declarative field map, nested destination paths, defaults and an audit of missing source values.

    What you can inspect

    • Migration audit — Row, Source, Action.

    Keep the result you need

    Use the output selector to inspect each generated file, then download it. Save a project to keep source inputs and settings together. Result files and editable projects serve different purposes.

    Processing & file support

    Source text is limited to 1.5 million characters per editor; imported text files are limited to 1.5 MB.

    Your working session

    Processing runs locally in a worker with a 30-second cancellation limit. Undo and redo keep up to 20 edits in this tab. Project files include imported assets and are limited to 40 MiB. There is no automatic saving.

    Public pages include advertising and optional analytics under our privacy policy. Review the method and any flagged output before sharing files.

    Using JSON Field Migration Runner

    Rebuild JSON records with a declarative field map, nested destination paths, defaults and an audit of missing source values.

    1. Start with the worked example in record array and mapping rules, then paste your own source or open a text file.
    2. Review your input structure and make any needed edits in the source editors.
    3. Choose “Process source”. Inspect the migration audit before using the result.
    4. Download the selected output, inspect other files in Export files and save a project if you want to reopen the same inputs.

    Example

    Try the built-in example, inspect migration audit and compare the result after changing one option.

    Questions & answers

    What does JSON Field Migration Runner do?

    Rebuild JSON records with a declarative field map, nested destination paths, defaults and an audit of missing source values.

    What are the important limitations?

    Dot paths address object fields only; literal dots in keys cannot be addressed. Output is rebuilt from mapping rules. Overlapping destination paths are rejected.

    Can I save and reopen my work?

    Yes. Save a project JSON file containing your inputs, settings and any imported assets. Projects are limited to 40 MiB. Undo/redo stores up to 20 edits in this session and is not saved in the project. There is no automatic saving.

    How do imports and output previews work?

    Source text is limited to 1.5 million characters per editor; imported text files are limited to 1.5 MB. Text previews show up to 150,000 characters; downloads include the complete output. Tables show 50 rows per page; CSV files include all rows.

    Help improve this tool

    Report a problem or suggest an improvement

    Describe the issue without pasting private tool input. Feedback goes to our admin inbox.

    Find another tool · Read practical guides