If the plan is to replace 11 with 15, I'd avoid the port change as that could cause further problems down the road. Is there any requirement to share the v15 db before you're ready to roll it out? You could just keep it on your desktop if not. Alternatively, if others need to access the solution to review what you've done, then it might be easier to pick up hosting for a month or two, depending on how long you'll be in development.
Where is the new server going to be physically? You mentioned at least three remote areas from where others may connect (home and other office (implying more than one)). Another option is to have your server colocated at a data center. This would also resolve the need to adjust and then have to troubleshoot port issues later.
Ah, yes! Excellent solutions! Thanks for helping me get my head out of itself!
We’re actually looking at an off-site server solution/colocation, so that might be the easiest way around it.
Thanks so much!
Glad that helped. Have a great day!
You may want to mark the response as helpful for others in a similar situation.
FYI, you don't have to worry about sharing ports with FMS 11 and FMS 15 because you can't install both on the same machine. The install will error out. techt's suggestion of off-site server hosting is good and maybe you might look at FileMaker's Cloud solution in the Amazon Marketplace. You'll want to do a trial run converting your databases from *.fp7 (FM 11 format) to *.fmp12 (format used by FM 15). Most things will transfer perfectly fine, but always good to test when you're jumping so many versions. Keep in mind FM 11 used an old proprietary standard of layouts which is now called Classic and no longer supported. Those Classic layouts will convert, but you'll want to make them into one of the new themes which are in CSS and much faster too. Reworking layouts into themes will greatly improve the user interface and performance, but it sure takes a lot of work too.