Mailchimp not importing signup date data

@snoogs 

Yeah Klaviyo is a bit specific when uploading lists with dates.. so you will have to format it in one of the acceptable formats and then upload as date property in klaviyo (not a list that is usually basic for new properties when uploading)

Here is article explaining what are the acceptable date formats https://help.klaviyo.com/hc/en-us/articles/115005253428

The main issue is for me at least most of the times i have dates with dots for example 03.23.2024 but klaviyo doesn’t accepts it with dots so it has to be for example 03-23-2024 or 03/23/2024

Hmm, Mailchimp seems to already export in an acceptable Klaviyo format.   Perhaps I’m cataloging it in the wrong place, the only Klaviyo category that made sense to me is $consent_timestamp.   Is that the wrong place to put it? Do I need to create a new Klaviyo category?   It’d just be nice to maintain when they subscribed as I transition to Klaviyo.   Thank you @Bobi N.!

@snoogs 

I don’t know how Klaviyo looks at consent timestamp at the end but I think that is property more for legal purposes than for use in email marketing.. in klaviyo you are adding profiles now so because of that the day when you add them is the date when they will be considered as created profiles in Klaviyo. But if you want to use that date for segmentation or something similar in the future, if consent timestamp is not available option for choosing you can add those date in a new property and use that one for segmentation..

Hey @snoogs, jumping in here to clarify: I hear you only want to import one segment from Mailchimp which wasn’t possible with the integration, but did you try importing all your subscriber data this way? Klaviyo should maintain the proper subscription status and data accordingly. 

I’m wondering if just doing it all via the integration will solve your problem rather than trying to cherry pick which contacts you do and don’t import. 

I think the cleanest way is to avoid importing it as a normal “new list” if you want the original signup data to stay accurate. A CSV import will often make the contacts look like they joined today unless the consent date field is mapped correctly.

I would first export only that Mailchimp segment, then make sure the CSV has a clear email column and a separate signup/consent date column. During the Klaviyo import, map that date field as a custom property or consent timestamp if available. Klaviyo also says CSV imports can include consent type and consent timestamp columns, so the mapping step is important.

Also, before importing, make sure the date format is accepted by Klaviyo. If Google Sheets changes the format, Klaviyo may not read it properly. Klaviyo has guidance for formatting dates in CSV files, so I would clean the date column first and test with a small sample before importing all 1,100 contacts.

For websites where signup timing matters, like a SASSA status check information site, keeping the original opt-in date is important because it shows when users actually joined and helps keep email records clean. So I would not rush the full import until the date mapping is tested properly