Magento Stack Exchange is a question and answer site for users of the Magento e-Commerce platform. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have my production and development sites. They have had different history of installing/uninstalling extensions therefore under core_config_data the config_id does not match unfortunately.

I am wanting to copy over a bunch of settings from the dev site to production however it seems like I'll be skipping a 50 or so ID numbers when I export and import. Does this matter? I am thinking it should be fine as long as there are no overlaps.

share|improve this question
up vote 3 down vote accepted

It should be fine. Config values are always triggered by path.

If I'm not mistaken config_id is only there for a primary key.

share|improve this answer

The config_id is not important unless you have some custom code that uses it. (I hope you don't).

The important columns in the core_config_data table are path (most important), scope, scope_id.

share|improve this answer
For once in my live I was quicker then you. – Tim Bezhashvyly Apr 4 '14 at 13:16
@Tim. yeah...I'm starting to lose it. I'm getting old but so is everybody else and I guess it's not a good excuse. – Marius Apr 4 '14 at 13:17
you would not believe me but I recently discovered that I'm getting old also. – Tim Bezhashvyly Apr 4 '14 at 13:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.