Reassign Zingg ID For Identity Resolution

Upgrade your model, migrate infrastructure, or change your schema. Every downstream system still references the same Zingg ID it always did.

New Run. Same IDs Your Systems Already Trust.

Zingg maps clusters from your new model back to your original cluster assignments by primary key overlap, reassigning the original Zingg ID wherever a match exists.

A new ID is only generated when no match is found in the original clusters.

--phase reassignZinggId
--conf newConfig.json
--originalZinggId prodConfig.json

record_pk	new cluster	Zingg ID
S3301	tmp-902a	zg-14f0 (original)
S3302	tmp-902a	zg-14f0 (original)
S3305	tmp-955c	zg-88b7 (new)

Built for the Moments Migrations Usually Break

Model upgrades

Add nicknames, better blocking, or improved classifiers without losing IDs

Infrastructure migration

Move from Spark to Snowflake, or vice versa, and keep the same IDs

Schema evolution

Add, remove, or retype fields and still preserve matched IDs

Data migration

Move from Databricks to Fabric, or consolidate data sources, without losing continuity

Platform upgrades

Upgrade Spark versions, Snowflake features, or other platform components and keep IDs stable through the process

docs.zingg.ai: Reassign Zingg ID guide

Reassign Zingg ID For Identity Resolution

Join Slack