Extracted data

The Extracted data view shows you exactly what Graftport pulled from the source platform. One row per source object, keyed by the source’s stable ID.

Where to find it

From any run item, click Source rows. The list is paginated and filterable:

• Source ID — exact match. Useful when you have a known SKU or customer email.
• Resource type — narrow to products / customers / orders / …
• Updated since — show only rows extracted since a date.

Each row shows:

• The source ID (e.g. Magento entity_id, Shopify GID).
• The full payload as the source returned it, JSON.
• The extract timestamp.
• A link to the staged record derived from this row, if one exists yet.

What it’s good for

• “Did we pull this row?” — answer in one search.
• “What did the source actually contain on March 10?” — the extract timestamp + the historical payload tell you.
• “Why did this transform output X?” — paste the raw payload into the mapping editor’s sample input and re-evaluate.

What’s stored

The full API response object for that source row, untouched. Graftport doesn’t strip or normalize before storing — that’s the transform’s job. The extracted data is the ground truth, and every downstream artifact can be re-derived from it.

Retention

Extracted data persists for the lifetime of the migration. Even after a successful load, it sticks around — that’s what makes re-transforming cheap, and what auditors need to see.

There’s no automatic pruning today. Tenants that need PII purge can contact the Graftport team to arrange one.