<h3>Migrating From Front End Uses Module</h3>


<p>If you are seeing this tab is because you have the <b>Module Front End Users (FEU)</b> installed in which case you'll be able to import settings, and users' data from <b>FEU</b>.</p>
<div class="warning">
  <p><b>Note:</b> the migration from <b>FEU</b> has only been tested with <b>FEU</b> branch <b>2.x</b>, specifically <b>2.14.3.4</b>. There is no warranty that it will work with any other version of <b>FEU</b>.</p>
</div>
<p>This should be a one time operation right after <b>MAMS</b> installation! Doing this will delete all data from MAMS. There is a rollback feature that tries to go back to whatever was previously in <b>MAMS</b> in case something fails, but there is no way to ensure the success of the operation.</p>
<p>
  <b>MAMS</b> will import all users tables, including groups and properties. Additionally all module settings from <b>FEU</b>  will be imported to <b>MAMS</b>.
</p>
<div class="information">
  <p><strong>Note:</strong> <b>MAMS</b> migration <b>won't delete nor modify</b> any data from <b>FEU</b>.</p>
</div>

<p>
  After a successful data import from <b>FEU</b>, there will still be a few steps needed to take to complete the migration:
</p>
<ul>
  <li>
    <b>templates</b> won't be copied for you, you'll have to copy them yourself;
  </li>
  <li>
    after copying the <b>templates</b> you'll have to adjust them to be used with <b>MAMS</b>:
    <ul>
      <li>you'll have to search and replace occurrences of <b>FEU</b>, <b>feu</b>, <b>cge</b>, <b>FrontEndUsers</b> and <b>frontendusers</b> with there counterparts (look at <b>MAMS</b> default templates for reference);</li>
      <li><b>cge</b> and other <b>CGExtensions</b> tags or <b>Smarty</b> plugins should be replaced by their <b>CMSMSExt</b> counterparts: as an example replace all occurrences of <b>&#123;cge_csrf}</b> with <b>&#123;xt_csrf}</b>;</li>
    </ul>
  </li>
    <li>
    <b>image and other files</b> will be kept in the folders set in <b>FEU</b>, settings which should have been copied to <b>MAMS</b> by the import tool;
  </li>
</ul>

<div class="information">
  <p><strong>Note:</strong> other than the case of a migration, both modules should be able to coexist side by side without issues as long as they don't share files' folders.</p>
</div>