Will original ownership, authorship and created dates be preserved?
Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users are set up in UGRU CRM. Where UGRU CRM cannot store one of them natively, it is kept as embedded metadata on the migrated record.
If the new system can't natively support an old record type, what are my options?
We handle it case by case. While mapping your data, we identify every record type without a direct counterpart in UGRU CRM, review sample records from it and propose how it can be represented, based on what UGRU CRM supports: map it to the closest native object, create a custom field or object, fold it into the parent record as text or a note, attach it as a file, or keep it in a read-only archive. You choose the approach, we write the migration scripts to place the data there, so it comes across in the form you choose instead of being left behind, and you see how it looks in a sample migration before we run the full set.
If the same contact appears more than once in Clarify, or several contacts share an email address or telephone number, will the migration create duplicates or merge them?
You decide, and we don't merge records on a guess about which one is correct. Your records come across as they exist in Clarify, so duplicates that are already there can come across too, and if you want them merged, give us the matching rule you want and we apply it as a follow-up pass. The exception is a CRM that checks for duplicates through its API: it returns the existing contact instead of creating a new one, so records sharing an email address or telephone number would otherwise collapse into one contact. Where that applies, we tell you how many records are affected and let you choose. If you want a separate contact for each source record and UGRU CRM has a setting that allows duplicate contacts, your team switches it on while we migrate them, and we tell you when it is safe to switch it off again.
Will the migration set off automations or send emails or notifications to customers, our team or anyone else?
No. Before the sample or full migration starts, we confirm with you that nothing in UGRU CRM will send messages about the migrated data: we import with notifications switched off wherever UGRU CRM allows it, and either pause any automation that could send them for the migration window or give it a condition, such as a suppression tag, that skips migrated records, which lets your live automations keep running for new records. We only proceed once you have confirmed it. If you want anyone told about the move, that message is sent separately, once the migrated data has been checked.
Can you migrate data that UGRU CRM can't take in through an API?
In many cases, yes. Where something can't be written through an API, we recreate it through UGRU CRM's user interface where the interface allows it, and where that work is repetitive we script and automate it. We tell you up front which items are handled this way, because recreating them through the interface can add time to the schedule.
Can you migrate only the data added to Clarify since our last migration?
Yes. We find the exact point in Clarify where the earlier migration ended and move only the records added after it. Records that were already migrated are not brought across a second time.
What happens if UGRU CRM requires fields our Clarify data doesn't have?
We check the destination for required fields your source data cannot fill and bring each one to you before those records are migrated. Together we agree how each one is handled, such as a mapping from an existing field, a default value, or, where UGRU CRM lets that field be made optional, setting it to not required for the migration so you can make it required again once the migration is complete. The migration then runs with that rule applied, so no records are rejected or left behind.
Will contacts that are already in UGRU CRM get duplicated?
They don't need to be. We can check each contact against the contacts already in UGRU CRM before creating it, so a contact the matching rule identifies as already there is matched to the incoming record instead of being created a second time. We agree the matching rule with you before the migration runs.
We use a lot of custom fields in Clarify. Can you map them to UGRU CRM?
Where UGRU CRM has a place for them, yes. Each migration is a custom script written for your project, so your custom fields and structure are mapped to UGRU CRM's model rather than forced through an import template. Where field types differ, such as a value stored as text in Clarify that UGRU CRM needs as a number, the script converts it. We agree the mapping with you and prove it on a sample migration before the full run.
How will my records carry over if UGRU CRM organizes leads, contacts and accounts differently from Clarify?
We map your records to the way UGRU CRM structures them, so each type of record lands where UGRU CRM expects it instead of being copied field for field. Before we build anything, we send you a migration checklist showing what moves and where each item lands, for you to review. Most data moves through the platforms' APIs; where an API cannot write something, we fall back to CSV import or manual entry.
Can you migrate the email history on our mail server, such as Microsoft Exchange, along with our Clarify records?
Yes, on a best-effort basis where Clarify has no clean way to export it. For team members who are still with you, UGRU CRM may be able to sync their mail itself once each person's email account is connected; for people who have left, we bring their messages in as notes on the right records, retrieving them from Clarify or your Exchange server, so the history stays intact and attributable.
Can you migrate our Clarify products and customers' purchase history to UGRU CRM, not just contacts?
Yes, where Clarify's API makes them available. Products and purchase records are scoped like any other data: the migration checklist covers products alongside contacts, notes and tags, and we confirm what each platform's API can read and write before anything runs. Where UGRU CRM has no native home for purchase history, we agree another form with you, such as a custom field or a note on the contact.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
