Merging Tags and Scopes, and Remapping Fields

As an organisation grows, its labels drift: one person tags records "VIP", another "V.I.P", a third "vip-client"; two departments end up with near-identical scopes; a custom field gets replaced by a better one but the old data is stranded. Qik has three clean-up tools for this — merging tags, merging scopes and remapping profile fields — so you can consolidate without editing records one at a time.

Merging tags

Merging tags combines several tags into one. Every record tagged with any of the merged-away tags is re-tagged with the tag you keep, and the merged-away tags are deleted.

How to merge tags

1. Open the Tags list in the dashboard.
2. Tick the checkboxes beside the tags you want to combine (at least two). Tick the tag you want to keep first.
3. Open the action sidebar and choose Merge (n) tags.
4. The merge page lists the tags and tells you how many tagged items will be updated. The first tag listed is the one that will be kept.
5. Click Start Merge. When it finishes you'll see "Tags were merged successfully" and return to the Tags list.

What changes

• Every record carrying a merged-away tag — profiles, events, articles, workflow cards and any other content — now carries the kept tag instead. A record that already had both ends up with the kept tag once.
• The merged-away tags are deleted.
• Smart lists, filters and automations that referred to a merged-away tag by name or selection will no longer match it. Update them to use the kept tag.
• If re-tagging fails for any type of record, no tags are deleted, so you can simply run the merge again.

Tag merges run straight away rather than as a background job, so for a tag used on a very large number of records, wait for the confirmation before navigating away.

Merging scopes

Merging scopes combines several scopes into one target scope. Everything that lives in, or refers to, the merged-away scopes moves to the target, and the merged-away scopes are deleted once they're empty. See Scopes and Groups for background on scopes.

How to merge scopes

1. Open the Scopes list and switch to the list view if you're looking at the tree.
2. Tick the scopes you want to combine (at least two).
3. Open the action sidebar and choose Merge (n) scopes.
4. On the merge page, choose the scope to keep. Qik pre-selects the scope that currently holds the most content; click Set as target on another scope to change it. The page confirms which scopes will be merged into the target.
5. Click Start Merge.

If none of the merged-away scopes contain anything, the merge finishes immediately ("Scope merge complete"). Otherwise it runs as a background job — you can follow its progress in the batch progress panel and carry on working.

What moves to the target scope

• Content — every record stored in a merged-away scope (profiles, events, forms, files and so on) is moved into the target scope.
• Child scopes — scopes nested under a merged-away scope are re-parented under the target.
• Access — roles, access passes, smart lists, actions and applications that granted permissions over a merged-away scope now grant them over the target.
• Positions and members — positions defined on the merged-away scopes are added to the target, and the people holding them move across. If someone already holds the same position in the target, they keep it once.
• Custom field values — values from the merged-away scopes' custom fields are copied onto the target. Where both scopes have a value for the same field, the merged-away scope's value can replace the target's, so review the target's details afterwards.

Once every record has been moved, the merged-away scopes are deleted. If any record failed to move, the merged-away scopes are left in place so nothing is orphaned — run the merge again to finish.

Limits

• You can't merge a scope with one of its own parents or children. Remove one of them from the selection.
• All scopes must belong to your organisation and be visible to you.

Remapping profile fields

Remap Profile Fields copies data from one profile custom field into another, across your profiles, in one background job. Use it when you've replaced a field (for example a free-text "Department" with a new dropdown) or need to consolidate two fields that hold the same information.

How to remap fields

1. From the dashboard, open Remap Profile Fields (listed under Utilities on the system dashboard).
2. For each mapping, choose the Source Field and the Destination Field. If the old field has already been removed from the profile content type, switch the source to Custom path and type its path, for example data.oldFieldKey.
3. Under If Destination Has Data, choose Skip (don't overwrite) to protect values people already have in the destination, or Overwrite to replace them.
4. Click Add Mapping to remap several fields in the same run. Each destination may only be used once.
5. Click Run Remap and confirm.

Progress is shown as "x / y profiles processed". You can navigate away — the job continues in the background. When it finishes you'll see Remap complete.

What to know

• Source data is copied, not moved. The source field keeps its values; remove the old field from the content type yourself once you're happy.
• Profiles with nothing in the source field are left untouched.
• Only custom fields (those stored under data.) can be chosen.
• Values are copied as they are. Make sure the destination field type can hold the source values — for example, copying free text into a dropdown only works if the text matches the dropdown's options.
• The remap runs with your permissions: fields you can't view aren't copied, and you need permission to edit the profiles being updated.
• When the job finishes, check that the processed count matches the number of profiles you expected to be updated.

Permissions

Admins can always perform all three.

Tips

• Before merging tags or scopes, search your smart lists, filters, workflows and automations for the names you're about to retire — anything selecting them directly will need updating.
• Rename the tag or scope you're keeping to its final name before merging, so everyone sees the right label straight away.
• Try a remap on a field with a handful of values first and spot-check a few profiles before running a large remap with Overwrite.

FAQs