Top Tip: Use Alternate Id when migrating data

MemNet provides a number of data import routines that can be used to migrate your data, see here for details.

These separate imports require you to link various import files to members that have already been created, for example, adding additional people, adding subscriptions to a member or using the member update to add custom fields to a member. With each of these, you can link the import to the member using either a member code or alternate id type and value pair. If you are importing members with a member code, then you can use that, but what if MemNet has been configured to create member codes when the members were imported? How do you link the later imports?

Use Alternate Ids.

The alternate ID value does not have to have any meaning on the membership, you just have to be able to include the same value in all of the imports you will be using. The value can be as simple as a sequence number created in your "source" data.

You will need to create an alternate ID type to use, but this and the alternate id's can be deleted once the data migration is complete.

See What is Member Alternate ID’s?