Will original ownership, authorship and created dates be preserved when the instances are merged?
Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users exist in the instance you keep. Where one of them cannot be set natively on the migrated record, it is kept as embedded metadata on that record.
Will consolidating our Affinity instances 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 the instance you are consolidating into will send messages about the migrated data: we import with notifications switched off wherever Affinity allows it, and pause any automation that could send them or give it a condition that skips migrated 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 Affinity can't take in through an API?
In many cases, yes. Where something can't be written through an API, we recreate it through Affinity'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 Affinity since our last migration?
Yes. We find the exact point in Affinity 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 if the instance we're consolidating into requires fields our other Affinity instance doesn't fill?
We check the instance you are consolidating into for required fields the incoming 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 that instance lets the 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.
Can I choose how pipeline stages and statuses from our other Affinity instance map into the one we keep?
Yes. You tell us where each stage, status and field should land in the instance you keep, including moving records into a different pipeline or stage name than the one they have today. We build that mapping into the migration scripts, show it to you in a sample migration, and adjust it before the full run if anything needs to change.
Can you map data from our other Affinity instance into the custom fields we already use, so our workflows and automations keep working?
Yes. We map the incoming data straight into the fields you already have in the instance you keep, rather than creating duplicate fields or tags alongside them. Your workflows and automations keep reading the same fields they rely on today, and you review the mapping in a sample migration before the full run.
How will we tell migrated records apart from the ones already in our Affinity instance?
We can mark every migrated record in the instance you are consolidating into, for example with a custom checkbox field that names the instance it came from, so your team can tell migrated data apart from records created there. We agree the marker with you during scoping so it fits how your team uses that instance.
We use a lot of custom fields in both Affinity instances. Can you map them across?
Yes. Each migration is a custom script written for your project, so custom fields in the instance being merged in are mapped to the fields in the instance you are consolidating into. Where the same field has a different type in each instance, such as text in one and a number in the other, the script converts it. We agree the mapping with you and prove it on a sample migration before the full run.
Can you migrate sales sequences, email templates and automation flows from our other Affinity instance?
Partly. Email templates are generally the simpler part to move, while sequences, flows and automations are recreated in the instance you keep rather than copied. Where Affinity's API lets us create them, we set them up programmatically; where it doesn't, they are built through its interface, by us with a login or by your team, and we confirm which items fall where during scoping.
Will the emails and files stored on contacts in our other Affinity instance migrate, including for inactive accounts?
Yes. Emails and files stored on those contacts can be part of the migration, including those on inactive accounts, and you choose which records and how much history come across. Files come across as actual files, attached to the matching records in the instance you keep. Where an email's original user has no account in the instance you keep, we can bring it across as a note on the contact instead.
Do you migrate bulk marketing emails as well as one-to-one emails when we merge Affinity instances?
It depends on which you need, and we confirm that before anything is pulled. Some CRMs keep bulk marketing emails, such as broadcasts, separately from one-to-one emails with contacts, so we agree with you which types are in scope and share a sample of them to review. One-to-one emails linked to your contacts and companies come across with those records, and bulk marketing emails can be included too.
Can you migrate the history of deal stage changes from our other Affinity instance, not just each deal's current stage?
Yes, where Affinity records stage changes and can hold them on migrated deals. Deal-stage history is scoped like any other data: we check what the instance you retire keeps for each deal's stage transitions, agree with you how that history is represented in the instance you keep, and you review it in the sample migration before the full run.
Can you migrate emails that are private to individual users of our other Affinity instance, not just the emails linked to contacts and deals?
Yes, where Affinity's API gives us access to them. On some CRMs, the API returns only emails linked to a record plus the private emails of the user whose account is connected, so each colleague whose private emails you want included connects their own account. Private emails that aren't linked to any contact or deal have nothing to attach to in the instance you keep, so we agree with you where they go, for example on a dedicated contact for each user, with the email content kept searchable.
Can you migrate products and customers' purchase history from our other Affinity instance, not just contacts?
Yes, where Affinity'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 the API can read and write before anything runs.
Do you migrate notes, tasks, activities and files from our other Affinity instance, or only contacts and deals?
Yes, all of them can come across, not just contacts and deals. Notes, tasks, activities such as events and emails, and files can be included alongside contacts, companies and deals, each linked to the record it belongs to, with owners kept where those users exist in the instance you keep. Tasks are migrated with the contacts they are linked to.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
