Hi Ibrahim,
sure – I think it’s quite simple to understand, there is only one major question, will this lead to “email log-manipulatin”? Those kind of logs could anyway be manipulated via database, so I don’t think that is an issue but something to be aware of.
The goal: do not loose data when migrating between live and staging websites
Migration / why: Not every change on a website is done live, some larger changes require e.g. a week or longer. The developer works on the changes on the dev/staging, when completed pushes the changes to the live system (migration). This will overwrite everything on the live website, including the email logs. Those email logs become in very very handy quite often when troubleshooting. It would be good to be able to rely on them. I cannot rely on them when there is a gap where email logs are missing
Process / how: simply allow to export to a format that can be imported again (e.g. CSV, JSON, XML). In real life it works like this: I migrate live to dev. I implement changes in dev over some time. When I am ready to migrate back from dev to live, I take an export of the email log of live. I run the migration to update the entire live site (this will overwrite the email logs, and all email logs in between this entire process get lost), after successfull migration to live, I simply import the email logs again
Better / advanced: instead of manual export/import, cloud integration would be the next level
I hope that clarifies things and is enough feedback and information about this idea.
Thanks
best regards
Markus