---
title: "Mapping custom fields during import"
url: "https://demo.myforumcat.com/q/98/mapping-custom-fields-during-import"
forum: "Demo"
question_number: 98
category: "General"
tags: ["Rate Limits"]
status: "solved"
solved: true
votes: 38
replies: 6
views: 1199
asked_at: "2026-07-26T00:10:22.846Z"
updated_at: "2026-09-18T22:18:47.851Z"
---

# Mapping custom fields during import

Asked by Marcus Lee on 2026-07-26 · 38 votes

Our old system had a priority field with no equivalent here. Can we map it into a tag during import instead of losing it?

## 6 replies

### Reply 1

meow (Owner) · 2026-07-26 · 3 votes

No field mapping in the import flow today, a priority field like that would need to become a tag manually after import.

### Reply 2 (marked as the solution)

Rebecca Stone · 2026-07-26 · 5 votes

We mapped our old priority values onto tags after the fact with a quick script against the API, worked well enough.

### Reply 3

Tom Whitfield · 2026-07-26 · 1 vote · In reply to Reply 2

Would be nice to have this built in eventually, but the tag workaround got us unblocked.

### Reply 4

Hannah Wright · 2026-07-26 · 1 vote

Same approach worked for us, scripted the tag assignment after the fact.

### Reply 5

Kai Tanaka · 2026-07-26 · 1 vote

Would still be nice to have this built into the importer directly, but the workaround is fine.

### Reply 6

Elena Marsh (Agent) · 2026-07-26 · 2 votes

Noted as a real request, added it to the import tool backlog alongside the timestamp preservation issue above.