Mapping custom fields during import

Question

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

Rebecca Stone · Accepted Answer

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

Demo Team · Answer

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

Tom Whitfield · Answer

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

Hannah Wright · Answer

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

Kai Tanaka · Answer

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

Demo Team · Answer

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

Solution